Theory Cloud · TheoryMCP

Work with theorymcp.ai namespaces and agent MCPs.

TheoryMCP is the routed MCP surface behind theorymcp.ai. Connect a host to a namespace, query its published knowledge, talk to agent MCPs that keep scoped memory across sessions, materialize an agent into your workspace — and, when you are granted scope, author one back. The route is the identity. The namespace is the source of truth. Every step below comes with a copyable prompt and a plain explanation of how it works.

Get started How it works Prompt library View on GitHub

Three things you do with a namespace

Read its knowledge, talk to its agents, or pull an agent into your own workspace. Pick where you are.

The mental model
Use a namespace CORE
read-only knowledge surface

Connect to a namespace route and query its published knowledge bases — no memory, no materialization, the lowest-friction surface.

Query published knowledge
Use an agent MCP MCP
persistent · scoped memory

Talk to a named agent endpoint that keeps subject-scoped memory across sessions and survives a change of model — stateful by design.

See how memory works
Integrate & author AUTH
materialize ↔ publish

Materialize a published agent into your workspace, verify it against served checksums, keep it in sync — and, when granted scope, author one back.

Integrate an agent

One identity. Three hosts.

The MCP server id is theorymcp in every host. The route is the only knob — swap in your namespace.

codex mcp login https://theorymcp.ai/theorycloud/mcp # native MCP OAuth 

# .codex/config.toml — codex performs MCP OAuth natively.
[mcp_servers.theorymcp]
url            = "https://theorymcp.ai/theorycloud/mcp"
oauth_resource = "https://theorymcp.ai/theorycloud/mcp"
scopes         = ["mcp:tools", "ai.kb.query"]

Full walkthrough on the Connect a host page. Antigravity needs the mcp-remote bridge.

Theory Cloud — constrained by design, deterministic by default
Theory Cloud constrains the design space with frameworks; theorymcp.ai adds a layer of persistent, authenticated identity on top. The route resolves who you are and what you may do — server-side.
Hosts
3
codex · Claude Code · Antigravity
The route
is the identity
tenant, scope, entitlement — all server-resolved
Source of truth
the namespace
local files are a materialization
License
open
this repo is the worked example

Quick starts

The shortest path from a route to a result — ranked by how often new consumers reach for them.

All guides
Connect a host

Wire codex, Claude Code, or Antigravity to a namespace route and authenticate.
Ground before acting

Always call describe_interface first — never assume a namespace's tools.
Query knowledge

search_docs then get_unit — previews first, authoritative detail second.
Agent memory

Append-only, subject-scoped continuity that survives a change of model.
Materialize an agent

Plan, fetch the pack to disk, verify every checksum, write the marker.
The prompt library

Copy-paste prompts for every step — connect, ground, install, author.