MCP-Native by Design
Memex AI exposes its entire surface as an MCP (Model Context Protocol) server. Any AI agent, regardless of vendor, framework, or runtime, connects to Memex AI and interacts with the strategy/decision/work/blueprint graph through standard tool calls.This is a deliberate architectural choice. Memex AI is not another AI coding tool. It’s the shared context layer that all AI tools read from and write to.
Why MCP
MCP is becoming the standard protocol for AI tool integration.Any AI coding agent
Claude Code, Cursor, GitHub Copilot, custom agents, all connect and access the full strategy/decision/work/blueprint graph.
Multi-vendor, no lock-in
Multiple agents from different vendors share the same context. Swap tools without losing your graph.
Custom agents fit in
Research, testing, deployment, product management. All integrate through the same protocol.
Server is source of truth
Not a file in a repository that might be stale. One place, always current.
Core Tool Surface
The full MCP surface, grouped by concern.Strategy (top-level container)
Strategy (top-level container)
Strategy drafting (collaborative design)
Strategy drafting (collaborative design)
Decisions (within a strategy)
Decisions (within a strategy)
Work Items (within a strategy)
Work Items (within a strategy)
Blueprints (cross-cutting knowledge layer)
Blueprints (cross-cutting knowledge layer)
Decision extraction (passive capture + review)
Decision extraction (passive capture + review)