SUMA Memory MCP

Stop re-explaining your project to Claude every time you start a new chat.

Your repos now have permanent memory. SUMA gives any MCP-compatible AI client (Claude Code, Cursor, Devin) a persistent knowledge graph that remembers architectural decisions, bug root causes, and project rules — across sessions, across machines, across your entire team.

Install (30 seconds)

Get an API key at sumapro.quadframe.work — free tier available.

Add to your .mcp.json:

{
  "mcpServers": {
    "suma-memory": {
      "url": "https://sumapro.quadframe.work/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_your_key_here"
      }
    }
  }
}

That's it. No local server. No Docker. No npm install. SUMA runs on Cloud Run — stateless, auto-scaled, always available.

Onboard Your Project (2 minutes)

After installing, run this once per repo to seed your permanent context:

suma_ingest(text="Project: [name]. Framework: [Next.js / Flask / etc].
Auth lives in: [path/to/auth.py]. Database: [PostgreSQL / SQLite / etc].
Rules never to break: [e.g. never store plaintext keys, all routes require org_id filter].
Deployment target: [Cloud Run / Vercel / etc].")

From this point forward, every new session inherits this context. You never explain it again.

How It Works

SUMA stores knowledge in a weighted graph. Every node has a gravity score across four dimensions:

• Recency — newer facts surface first
• Density — well-connected facts outrank isolated ones
• Semantic similarity — vector distance to your query
• Emotional weight — high-signal facts are reinforced over time

When you call suma_search, the K-WIL gravity algorithm traverses the graph and returns the highest-relevance context — not a flat list of chunks, not a raw embedding match, but the facts that actually matter for what you're doing right now.

Core Tools

Three Use Cases

1. Persistent Architecture Memory

# After finalizing a decision:
suma_ingest(text="We chose REST over GraphQL. Root cause: GraphQL N+1 queries
            caused 3x latency on /search. Architect ruling Apr 10 2026.")

# Next session, cold start — full context in one call:
suma_search(query="why did we switch to REST?")
# → Returns ruling with full context. No re-explaining.

2. Bug Root Cause Archive

# After fixing a hard bug:
suma_ingest(text="Cloud Run WebSocket bug: asyncio.run() in daemon thread killed
            by Cloud Run recycling. Fix: use asyncio.get_event_loop() instead.
            Never use asyncio.run() in long-lived Cloud Run services.")

# Six months later, same error:
suma_search(query="asyncio cloud run daemon thread crash")
# → Root cause retrieved instantly. Hours saved.

3. Multi-Agent Knowledge Fusion

Architect, developer, and QA agents each write to SUMA using their own sessions. Their knowledge merges into one shared org graph. When QA asks "what did the architect decide about auth?", it retrieves the architect's ruling — zero explicit handoff required.

Enterprise Safety

Anti-flood protection: Each source machine is rate-limited to 5 ingests per 60 seconds. Runaway agent loops are broken gracefully — the 6th request returns {"status": "throttled"} without crashing or corrupting the graph.

Multi-tenant isolation: Every node is scoped to org_id at the database layer. Two organizations

... View full README on GitHub