An AI agent host that drives LLMs with tool access across the Extropian ecosystem.
Dependency Graph
Extropian MCP is the agent host of the Extropian ecosystem: an AI agent that drives LLM providers (Ollama / OpenCode) and acts on the ecosystem by calling whichever repos are registered as tools — spatial-ui, geometry, assets, physics, optimization, and others. It also manages conversational state (Q&A turns, history budgeting) with hooks so an embedding host can load that state into widgets, plus optional voice support via hooks.
Registered repos each ship a prompts/ folder whose files teach the AI how to use that repo's tools — extropian-mcp loads them at runtime, with no embedded prompts. Tool definitions are MCP-shaped (name, description, input JSON Schema), so a future MCP-server adapter over the registry maps one-to-one onto tools/list / tools/call.
"MCP" names the product category, not protocol conformance: extropian-mcp is the agent-runtime library that an Extropian host embeds; it does not (yet) speak the MCP JSON-RPC protocol. Server and client adapters are planned. The current version (v0.3) was rebuilt as the generic agent host after the visual-document-specific machinery moved to extropian-spatial-ui, and ships with a passing test suite.
Core capabilities
Drives LLM providers (Ollama / OpenCode) with JSON-mediated tool calls
Tool registry over registered Extropian repos, loaded from each repo's prompts/ folder
Conversational state management — Q&A turns, history budgeting, reproducible snapshots
Hooks so an embedding host can load conversation state into spatial-ui widgets
MCP-shaped tool definitions ready for future tools/list and tools/call server adapters
Technical foundation
Built on extropian-core shared types as the schema authority
Per-repo prompts-folder convention: each registered repo teaches the AI how to use its tools
Provider abstraction for local (Ollama) and code-agent (OpenCode) LLM backends
Source Available (PolyForm Shield)Binary Distribution (Proprietary)Internal Use (Proprietary)
Licensing is negotiated around the software, deployment model, scope, and ownership requirements of each project — whether Extropian MCP is used as-is, customized for your workflows, or embedded in a larger system you are building. I prefer perpetual licenses per major version: one fee licenses the version you chose for as long as you use it, with maintenance updates included within that major version.
Source Available (PolyForm Shield): view and build from the source under terms that prevent offering it as a competing product or service — no license fees or royalties.
Binary Distribution (Proprietary): one-time license to use and distribute the software in binary form, including inside products you sell.
Internal Use (Proprietary): one-time license for ongoing internal use of the software as delivered — no distribution, no recurring fees.
