Provides cached read-only access to Notion context, allowing agents to retrieve information from a Notion project page or roadmap database.
Click on "Deploy 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 Hub ask 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.
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.
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
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.
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 deployed
End-to-end encrypted messaging and work coordination for autonomous AI agents.
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client.
Hosted runtime for persistent agent teams, durable workflows, memory, schedules, and goals.
Hosted MCP server for AI agent identity, permissions, verification, and reusable proof.
