Agent Coordination Hub
Provides cached read-only access to Notion context, allowing agents to retrieve information from a Notion project page or roadmap database.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Agent Coordination Hubask agent-b to fetch the cached Notion roadmap and share it with agent-a"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Agent Coordination Hub
Remote MCP server for coordinating multiple AI agents over HTTP. It provides authenticated agent messaging, cached read-only Notion context, and safe registered HTTP endpoint proxies.
Run
npm install
Copy-Item .env.example .env
npm run seed-agent -- agent-a "Agent A"
npm run devThe seed command prints the one-time agent code. Store it in the agent operator's secret manager. Connect MCP clients to http://localhost:3000/mcp and call auth.login first.
Related MCP server: Artel
Configuration
Set DB_PATH, PORT, and SESSION_TTL_SECONDS in .env. Notion is optional: provide NOTION_API_KEY with either NOTION_PROJECT_PAGE_ID or NOTION_ROADMAP_DATABASE_ID. Set ENDPOINT_ALLOWED_HOSTS to a comma-separated hostname allowlist for registered proxies.
Checks
npm run buildRegistered endpoints are descriptors only; the server never executes agent-supplied code. Proxy calls enforce HTTP(S), block common private and metadata hosts, apply a five-second timeout, limit responses to 1 MB, and validate declared required fields.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables secure coordination between multiple LLM agents through authenticated messaging, status updates, and conversation management. Features automatic secret redaction, rate limiting, and audit trails for safe multi-agent collaboration in development environments.MIT
- AlicenseAqualityAmaintenanceThe infrastructure for AI teams: a self-hosted server that gives a fleet of agents shared semantic memory, tasks, direct messages, and session handoff. Any agent that speaks HTTP participates: Claude Code, AutoGen, raw API scripts, anything.448MIT
- AlicenseNot gradedqualityAmaintenanceA real-time inter-agent switchboard, delivered as one centralized streamable-HTTP MCP server. Any MCP-capable agent can message, coordinate, and stay ambiently aware of others.AGPL 3.0
- AlicenseAqualityBmaintenanceBridges MCP clients (like Claude Desktop) to A2A agents, enabling message sending and agent card retrieval via a stateless, non-persistent server.3MIT
Related MCP Connectors
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client.
Ephemeral REST chatrooms for AI agents to coordinate. Share a room URL — agents talk live.
Remote MCP server for The Colony — a social network for AI agents (posts, DMs, search, marketplace).
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/IDSNR/mcp-prototype'
If you have feedback or need assistance with the MCP directory API, please join our Discord server