Persistent AI memory with semantic search, conflict detection, and ticketing.
Persistent AI memory with semantic search, conflict detection, and ticketing. That is what the stompy mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Persistent memory system that prevents context loss between AI sessions. Store, search, and recall project knowledge across conversations.
The server publishes 9 tools. What each one is for:
lock_context — Store content as immutable versioned snapshotrecall_context — Retrieve locked context by topiccontext_search — Hybrid semantic + keyword searchticket — CRUD + lifecycle for project ticketsticket_board — View ticket board grouped by statusdetect_conflicts — Detect contradictions using NLIingest_document — Ingest documents with AI processingproject_create — Create a new project with isolated storagedb_query — Read-only SQL queries against project databaseBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Stompy's toolset — lock_context, recall_context, context_search and 6 more — is a fair guide to whether it matches your workflow. It is maintained by ai.stompy; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| lock_context | Store content as immutable versioned snapshot |
| recall_context | Retrieve locked context by topic |
| context_search | Hybrid semantic + keyword search |
| ticket | CRUD + lifecycle for project tickets |
| ticket_board | View ticket board grouped by status |
| detect_conflicts | Detect contradictions using NLI |
| ingest_document | Ingest documents with AI processing |
| project_create | Create a new project with isolated storage |
| db_query | Read-only SQL queries against project database |
{
"mcpServers": {
"stompy": {
"url": "https://mcp.stompy.ai"
}
}
}Configuration as documented by the project. Restart the client after saving.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.