SoluCortex MCP
[PyPI]
[CI]
[Python]
[License: MIT]
Official Model Context Protocol server for
SoluCortex — living technical memory for AI agents.
Connect any MCP-compatible agent (Claude Code, Claude Desktop, Cursor, Codex, Cline, …) to
your SoluCortex project so it can recall the decisions, conventions, risks and architecture
that matter before it works, and remember what it learns when it's done.
Website: solucortex.ai ·
Setup guide: solucortex.ai/docs/mcp ·
Tools reference: solucortex.ai/docs/mcp-tools ·
PyPI: solucortex-mcp ·
MCP Registry: io.github.soluai-spa/solucortex-mcp
[SoluCortex MCP demo: recall approved context at task start, remember learnings at close]
Tools
Governance by design: agents propose, humans govern. Agents can never change a
memory's status, rewrite its metadata, or delete it — edits go back to pending and
deletions only happen from the SoluCortex panel.
Requirements
- A SoluCortex account and a project API key (prefix
scx_) — get it from your
SoluCortex dashboard.
- One of:
uv (recommended), Python ≥ 3.10, or Docker.
Configuration
stdio mode (default, local)
The server is configured entirely through environment variables:
HTTP mode (remote, multi-tenant)
Run with MCP_TRANSPORT=http (or --http) to serve Streamable HTTP on $PORT
(default 8080) — the mode behind https://mcp.solucortex.ai. Credentials travel with
each request and the environment is ignored:
GET /health (and /healthz locally; Cloud Run's frontend intercepts /healthz) responds without auth. The MCP endpoint is
/mcp, runs stateless, and shares nothing between requests/tenants.
Never commit your API key. Keep it in your MCP client config's env block or a local .env
(see .env.example).
Install
Remote (recommended — nothing to install)
The hosted server at https://mcp.solucortex.ai/mcp speaks Streamable HTTP; your key
travels with each request:
Or in any client with remote MCP support:
Claude Code (local, stdio)
Claude Desktop / Cursor / Cline (JSON config)
Add to the client's MCP config (claude_desktop_config.json, Cursor mcp.json, etc.):
From a local clone
Docker
Prebuilt image on GHCR:
Or build it yourself:
The server speaks MCP over stdio, so clients launch it as a subprocess (-i keeps stdin open).
Instructions for your agent (AGENTS.md)
Once connected, give your agent the methodology too: copy
templates/AGENTS.md into the root of your repo (it works as
AGENTS.md or CLAUDE.md). The MCP handshake already carries these instructions — the
file lets you version them alongside your code, extend them with your own conventions,
and optionally enable the commented Claude Code hook recipe for guaranteed recall.
Development
Notes
- Memory
type vocabulary: the canonical set is architecture, decision, risk, convention, bug_history, tech_debt, sensitive_module, learning, external_integration. Some backends
accept an older set (technical_decision, historical_bug, current_state, task_closure).
The server passes type through and surfaces HTTP 422 so you can retry with the other set.
- Never store real secrets in a memory. Record location, type, severity and action taken instead.
License
MIT — see LICENSE.