-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Logan Besecker edited this page Oct 1, 2026
·
2 revisions
MCP Harbor is a searchable registry of Model Context Protocol servers — about 37,000 of them — with an install guide for every client, per-tool pages, a changelog for each listing, and an MCP endpoint of its own so agents can search it directly.
This wiki explains how it works: where the data comes from, what each kind of page is, how to connect an agent, the REST API, and how the site is run.
| If you want to… | Read |
|---|---|
| Find and install an MCP server | Using MCP Harbor |
| Let your agent search the registry itself | Connecting an Agent |
| Get your server listed | Publishing a Server |
| Query the registry from code | REST API |
| Know how listings stay current | How Data Is Collected |
| Understand a listing's changelog | Changelogs |
| Run, deploy or configure it | Operations |
| Work on the code | Development |
- Search: browse every MCP server by name, description, tag or tool name.
-
For agents:
https://ai.mcpharbor.dev/mcp— Streamable HTTP, no account, no key. - For LLMs: llms.txt describes the site and the endpoint.
- What changed: the registry-wide changelog.
-
Official listing:
io.github.lbesecker195/mcp-registry-search-directoryin the official MCP Registry. - Routing many servers through one endpoint: MCP Gateway.
Source: lbesecker195/MCP_Registry, Apache 2.0.
MCP Harbor · MCP server changelog · Apache 2.0
Using it
How it works
Running it