Agenten stärken
Die eigene URL des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
https://sumapro.quadframe.work/mcpDie Claude-Schaltfläche oben öffnet Claude mit ausgefülltem Namen und ausgefüllter URL. Sie bestätigen dort noch.
claude mcp add --transport http io.github.sumanaddanki-suma-memory https://sumapro.quadframe.work/mcpRun in a terminal.
{ "mcpServers": { "io.github.sumanaddanki-suma-memory": { "command": "npx", "args": [ "-y", "mcp-remote", "https://sumapro.quadframe.work/mcp" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
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.
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
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.
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.
SUMA stores knowledge in a weighted graph. Every node has a gravity score across four dimensions:
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.
# 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.
# 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.
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.
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.
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.
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
{ "mcpServers": { "io.github.sumanaddanki-suma-memory": { "url": "https://sumapro.quadframe.work/mcp", "headers": {} } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Der Herausgeber nennt diese Umgebungsvariablen: SUMA_API_KEY.
Suma Memory wird über HTTP erreicht.
Zuletzt geprüft: 2026-11-10. Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.