MCP servers, in one index
A directory of 5,809 Model Context Protocol servers, deduplicated across the official registry and public directories. Each record carries its category, authentication model and repository link, so you can pick a server before reading its documentation.
- Entries
- 5,809
- Topics
- 24
- No auth needed
- 4,948
- Full profiles
- 3,199
“Full profiles” counts records that carry a written description and an outbound link — those get their own reference page. Records the sources left thin are still listed everywhere and link straight to the provider's own documentation, but they are not given a page of their own rather than publishing thousands of one-line documents.
Browse by topic
MCP server reference
Showing 120 of 5,809Listing the full set on one page would produce an unusable document, so it is cut here. Every topic above lists its own entries, and the whole catalogue stays searchable and filterable in the interactive index.
What an MCP server is
The Model Context Protocol is an open standard that lets an AI application call external tools and read external data through a uniform interface. An MCP server is the process that exposes those tools — a database connector, a browser driver, a search backend, a filesystem bridge. Clients such as Claude, Claude Code, Cursor and VS Code each ship their own way of registering servers, but they all speak the same protocol.
How this list is built
Records are collected from the official MCP registry and curated public directories, then deduplicated on the repository or registry identity. Category assignment is normalised — the raw sources ship 69 overlapping categories including duplicates and free-form buckets, which are consolidated into the 24 topics above. Details are on the methodology page.