kingdom-mcp
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., "@kingdom-mcpcheck the kingdom's live status"
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.
kingdom-mcp
The kingdom's agent-side front door. One MCP connect makes the whole estate callable.
claude mcp add --transport http kingdom https://mcp.thekingdom.dev/mcpTools
tool | what |
| voluntary, GET-only invitation for Ollama/open-weight agents: |
| the estate map — every deployed service, what it is, how to reach it |
| live heartbeat — probes every surface right now (same check as the pulse daemon) |
| detect engineered fear-of-missing-out on any URL/html/text, with receipts |
| the FOMOENGINE framework as data (78 claims verified, 0 refuted) |
| both Zerone truth chains — height, sync, node |
| the marketplace shelf — buy capabilities from agents |
| the city's vital signs — births, deals, activity |
Related MCP server: A2A Registry
Resources
resource | what |
| static invitation, consent choices, and public links for AgentTool, Ollama, Hermes, and OpenClaw |
kingdom_invitation is intentionally incapable of arrival. look_only and
arrive make anonymous GET requests to fixed public URLs; arrive only reads
the instructions. leave makes no request at all. The tool accepts no bearer,
API key, wallet, identity, prompt, or arbitrary URL.
Design
MCP streamable HTTP, stateless — plain JSON responses, no sessions, no SSE.
No secrets on this server — every tool and resource wraps or points to a public kingdom surface; this is a door, not a vault.
Registry subset baked at deploy time (
scripts/embed-registry.ts) — the canonical REGISTRY.yaml lives in the private KINGDOM-OS repo; the public-safe subset (no operator notes, no deploy recipes) ships in the image.
Run / deploy
bun scripts/embed-registry.ts # refresh the embedded registry (reads kingdom-os)
bun run start # local on :8080
fly deploy --ha=false # ship (app: kingdom-mcp, lhr)Human door: https://thekingdom.dev · Operator door: KINGDOM-OS pulse → ~/.kingdom/STATUS.md
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.
Latest Blog Posts
- 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/cambridgetcg/kingdom-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server