mcpField
S
suma-memory

suma-memory

Remote
github.com/sumanaddankiMemory & Knowledge0Updated 28w ago
Repository

About suma-memory

SUMA Memory MCP provides MCP clients such as Claude Code and Cursor with a persistent project knowledge graph across sessions. It stores decisions, bug causes, and rules, retrieves relevant context, and supports shared organizational memory across agents.

Key features

  1. 01Store project knowledge in a weighted graph
  2. 02Retrieve context with natural-language queries
  3. 03Search and learn in one operation
  4. 04Correct information and remove noisy nodes
  5. 05Share memory across agents in an organization

Use cases

  1. 01Recover architectural decisions and their rationale in a new session
  2. 02Find prior bug causes and fixes
  3. 03Share project knowledge among development, architecture, and QA agents

MCP support

It is a hosted MCP server accessed through a remote URL and Bearer API key, with no local server to run. It exposes tools for health checks, knowledge ingestion, search, combined retrieval and learning, and corrections.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://sumapro.quadframe.work/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://sumapro.quadframe.work/mcpAuth required
Packages
npmsuma-mcp-proxy1.4.0

Tools

Details

From the project README

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

ToolWhat it does
suma_pingHealth check — verify connection and API key
suma_ingestAdd knowledge to the graph (architecture decisions, bug fixes, rules)
suma_searchRetrieve relevant context by natural language query
suma_talkSearch + learn in one call — retrieves context and updates graph
suma_correctFix wrong information — supersedes original, queues replacement
suma_cleanRemove noise nodes that pollute search results

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 on the same Cloud Run instance cannot access each other's data — enforced by SQL, not application logic.

Immutable audit trail: suma_correct and suma_clean never delete data. Nodes are superseded and invisible to the API while preserved in storage for compliance.


Key Metrics (Live Production — April 2026)

MetricValue
Compression ratio94.7% — 801 nodes replace 15.2M tokens
Cost saved per org$14.47 across 538 queries
K-WIL fidelity96.3% — 26/27 facts recoverable from 5-node graph
Automated tests118 (102 Playwright E2E + 16 pytest)

Pricing

PlanQueries/monthPrice
Starter20,000Free
Developer100,000$4.99/mo
Team500,000$29/mo
EnterpriseUnlimitedContact

Get your key: sumapro.quadframe.work


© 2025–2026 Suman Addanke / A2 Vibe Creators LLC
US Patent applications pending — 6 filed (2025–2026). Unauthorized commercial use prohibited.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.