For public MCP server listings, start with the official MCP Registry. For connectors offered inside Claude, check Claude’s in-app connector directory. Those are different discovery routes: a server appearing in the registry is not proof that it is available in Claude’s directory, compatible with your particular Claude client, safe for your use, or currently maintained.
Use the list as a starting point, then verify each candidate against its maintainer’s current documentation before connecting it. There is no authoritative current count of all Claude-compatible MCP servers.
Where to find MCP servers for Claude
| Discovery route | Best for | What to keep in mind |
|---|---|---|
| Official MCP Registry | Searching public MCP server listings and their metadata. | It is a public catalog, not an endorsement or a guarantee that every entry works with every Claude client. |
| Claude app connector directory | Finding connectors offered inside the Claude app, especially if you prefer an in-app discovery route. | Its scope is distinct from the registry; the available evidence does not establish that every registry entry appears there. |
| MCP maintainers’ reference repository | Learning from a small collection of reference implementations and SDK examples. | It is intentionally a limited educational collection, not a complete server directory. |
| Third-party directories and curated lists | Browsing by category or finding grouped suggestions. | Listings and counts can be self-reported or change over time. Verify the project at its maintainer’s own page or repository. |
Official MCP Registry
The Model Context Protocol maintainers announced the Registry as an open catalog and API for discovering publicly available MCP servers on September 8, 2025. They described it as a “single source of truth for MCP servers.” That describes its role as the official public catalog; it does not mean a listing guarantees quality, safety, or compatibility with a specific client. Registry entries can change, so inspect the current version and listing information rather than relying on a saved list.
Claude’s in-app connector directory
The Claude connector directory is a separate route for discovering integrations offered inside Claude. It can be the simpler first stop if you want an app-level connector rather than evaluating a server from a public catalog. Do not assume that a connector directory and the MCP Registry contain the same items: they have different scopes, and no complete overlap is established.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11#1 Best Overall
Reference implementations
The MCP maintainers’ reference repository is useful for understanding examples and SDK usage, not for finding every available server. Examples surfaced there include Everything, Fetch, Filesystem, Git, Memory, Sequential Thinking, and Time. Treat these as reference projects, not as a current recommendation list: check the repository and each project’s own documentation for current maintenance and suitability.
Third-party indexes
Directories such as claudemcp.org and ClaudeMap, along with curated guides, can make it easier to browse by service or task. Their convenience does not make them a compatibility or security authority. For example, Claude MCP has displayed a self-reported figure of 36,544 servers and says it updates daily; that third-party figure was not independently verified and is not a count of all currently working Claude-compatible servers. Counts may include different kinds of entries, versions, or compatibility claims.
Rank #2
What kinds of servers appear in lists?
Listings illustrate the range of tasks MCP integrations may cover. Examples surfaced in directory results include file operations, Git, persistent memory, Slack, PostgreSQL, browser automation, and web search. These categories are useful search terms, not endorsements or confirmation that a particular listing remains maintained or works with your current Claude setup.
Historical launch examples also need context. Anthropic’s 2024 MCP announcement named Google Drive, Slack, GitHub, Git, Postgres, and Puppeteer among prebuilt servers shared to help developers get started. That is evidence of what was named at launch, not proof that every named implementation is still current, supported in the same way, or available through the same Claude connection method today.
To narrow a large list, start with the job you need done. A file-oriented server and a database server may both be valid MCP projects, but they answer different needs. For each candidate, write down the specific data or action you require, then confirm the server offers it and that its access scope is acceptable.
How to choose and verify a candidate server
- Match it to the task. Identify the exact tool or data source you need. Read the server’s own tool descriptions and confirm they cover the task rather than assuming from its name or category.
- Check compatibility for your Claude client. Read the current setup documentation for the server and the Claude client you intend to use. Confirm the supported connection method and any client-specific requirements; a generic MCP listing alone does not establish compatibility.
- Inspect who maintains it. Find the maintainer’s project page or source repository. Look for recent maintenance signals, a current release or version, and documentation that matches the version you would install. A listing’s presence does not establish that the project is actively maintained.
- Review access and actions. Determine what information the server can read, what actions its tools can perform, and which accounts or resources it will be able to reach. Give it only the access needed for the intended task, and do not treat directory inclusion as a safety endorsement.
- Understand setup and credentials. Before connecting, identify prerequisites, authentication steps, permissions, and required configuration from the maintainer’s current instructions. If those are unclear, stop and resolve them before granting access.
- Recheck immediately before installation or recommendation. Listings, versions, and compatibility can change. Check both the live official listing and the maintainer’s own documentation close to the time you plan to use the server.
Why a directory entry is not a security review
A catalog helps with discovery; it cannot tell you whether a particular server is appropriate for your data, credentials, or workflow. The MCP Registry announcement says maintainers can denylist entries and remove them from public access, so listing status itself may change. Before installing, assess the server’s maintainer, data access, possible tool actions, and setup requirements. If you cannot establish what it can access or do, do not connect it to sensitive accounts or information.
Is there a complete list of Claude-compatible MCP servers?
No authoritative, current total of all Claude-compatible MCP servers is established. A registry, an app connector directory, a reference repository, and third-party indexes do not necessarily count the same things. One may show public entries, another connectors offered within an app, and another projects or versions gathered by its own process. Compatibility can also depend on the specific Claude client and connection method.
For that reason, a large number on a directory page should not be presented as the number of working servers for Claude. Treat counts as source-specific and time-sensitive, and confirm individual candidates instead of relying on a headline total.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsScreenshotNeo for website screenshot tasks
If your MCP use case is capturing website screenshots or PDFs, ScreenshotNeo is a focused alternative to try first rather than a general-purpose server directory. It is a website screenshot API and MCP server from Yorker Media, with tools named take_screenshot, get_page_info, and capture_pdf for AI agents including Claude and Cursor. It is intended for that capture workflow, not as a replacement for file, database, or messaging integrations. See ScreenshotNeo and its documentation for current setup details.
For an API capture, one GET request can return an image or PDF. This cURL example saves a WebP screenshot of Stripe:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpUse your API key in place of YOUR_API_KEY. The API also accepts PNG, JPEG, or WebP output and can return a PDF. ScreenshotNeo removes supported cookie or consent banners, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Its billing rules exclude bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits; response headers report the page verdict and whether the request was billed.
Other available capture options include full-page captures with lazy images loaded, capturing an element by CSS selector, dark mode, device presets or a custom viewport, retina scale, PDF page settings, custom CSS or JavaScript, clicking or hiding elements, wait conditions, blocking ads or selected requests, custom headers, cookies, user agent and authorization, timezone and geolocation, transparent backgrounds, resizing, caching, signed image links, asynchronous jobs with signed webhooks, bulk captures, a usage API, and an OpenAPI specification. Parameter names used by other screenshot APIs also work, which can ease a migration. Pricing is $0 for 1,000 screenshots a month with no card, then $5 for 3,000 on Starter, $15 for 15,000 on Growth, $39 for 60,000 on Pro, $99 for 250,000 on Scale, and $249 for 1,000,000 on Business; annual billing gives two months free. Every feature is on every plan. Sign up for 1,000 free screenshots a month with no card.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
What to do when a listing is unclear
- If a listing does not name the Claude client or connection method, do not infer that it works with your intended setup; locate current maintainer documentation first.
- If a directory page and project repository show different versions or maintenance information, prefer the maintainer’s current documentation and verify the version you would actually use.
- If a third-party page gives a large server count, record it only as that page’s own count and date. Do not turn it into an estimate of all compatible servers.
- If setup instructions do not make permissions or data access understandable, do not connect the server to accounts or data you cannot afford to expose.
- If a once-listed entry is missing from a current registry, check its maintainer’s project page before assuming it is available through the public catalog; registry visibility can change.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
