MCP Hub
Every tool your agents can use, in one catalog
Add each server once, with one credential. Meandr builds its catalog, your team switches on what's allowed, and every workspace attaches from there.
How it works
How the MCP Hub works
Servers belong to your team, not to a workspace.
-
01 Shared servers
Add each MCP server once, for the whole team
A server is one record for the whole team. Remote servers over Streamable HTTP, stdio MCP servers and hosted servers all live in the same list. Any workspace can use a server without a copy of the server or its credential.
- One credential per server, shared by every workspace that uses it; revoke it once in the server's settings
- Meandr tries the connection and the sign-in the moment you add a server
- You can also turn on a health check for any server and set its interval and timeout
- Sign-in is set when you add a server; later edits cover health checks, rate limits and custom headers
×Add MCP serverRegister an MCP server. Tool calls route through it with your policies enforced on the way.
Endpointhttps://learn.microsoft.com/api/mcpEdit URLNameMicrosoftAuthentication ?NoneCustom trust roots ?Custom headers ?Health monitoring ?Per-server rate-limit override ?BackAdd server -
02 Tool discovery
Meandr reads each server's tools and prompts, and re-reads them when they change
Meandr reads a server's tools, resource templates and prompts from the server itself. Meandr re-reads that catalog every hour, and about five minutes after the server reports that its tools or prompts changed.
- Resync reads the server again on demand
- A read that fails puts a failed badge on the server, and the catalog you had stays as it was
- Files and data a server shares are never copied: Meandr fetches each one live when an agent asks
- The catalog names the MCP revision the server speaks
Server catalogDiscover what
Notionexposes — tools, resource templates, and prompts.RegionsNotion MCP 1.2.0MCP 2026-07-28latestFRA · 2 prompts iIAD · 2 prompts iToolsResource templatesPrompts- Make this a Notion page
make-this-a-notion-page{ }› - Make this a Notion database
make-this-a-notion-database{ }›
ResyncLast updated 37mCloseSaved -
03 Tool curation
Your team switches on the tools workspaces may import
Every tool, prompt and resource template gets a team switch, and no workspace can import one that is switched off.
- Tools keep the names their server gave them
- Two tools with one name in a workspace are caught at save, and you pick an alias for one
- Read-only and destructive tags the server declares show up when a workspace imports its tools
- Policies then decide which imported tools each agent sees
Server catalogDiscover what
Notionexposes — tools, resource templates, and prompts.RegionsNotion MCP 1.2.0MCP 2026-07-28latestFRA · 57 tools iIAD · 56 tools iToolsResource templatesPrompts- Create a page comment
notion-create-comment{ }› - Create pages in Markdown
notion-create-pages{ }› - Duplicate Notion page
notion-duplicate-page{ }› - Fetch Notion entitiesread-onlyidempotent
notion-fetch{ }› - Get page commentsread-onlyidempotent
notion-get-comments{ }›
Questions about the MCP Hub
Does the catalog hold my data?
Is the MCP Hub the same as the Docker MCP catalog or the Official MCP registry?
Keep every MCP server your team uses in one catalog
Each server keeps one record and one credential, however many workspaces use it.
Try for freeQuestions? Email us