

An AI memory system that actually remembers your projects, preferences, and that thing you explained three weeks ago.
Monday morning
You open Claude. Fresh context window. Blank slate.
You start typing:
"So, I'm building an API for a task management system called TaskFlow. It uses Hono on Cloudflare Workers, with Neon PostgreSQL, and we're doing OAuth via Scalekit. The auth flow is..."
You've explained this fourteen times this month.
Claude nods politely. Processes your words. Pretends this is all new information.
It isn't.
Every new conversation, you're back to zero.
That architectural decision from two weeks ago? Gone.
The API naming convention you settled on? Forgotten.
Your preference for tabs over spaces? (We don't judge.)
You spend the first ten minutes of every session rebuilding context that should already exist.
Claude is brilliant. But Claude has the long-term memory of a caffeinated goldfish.
What if it actually remembered?
Meet Stompy. An elephant. (We're not being subtle about the metaphor.)
Stompy is an AI memory system — an MCP server that gives Claude persistent, searchable, organized knowledge that survives the reset.
Actual memory. Structured. Versioned. Yours.
The Tool: lock_context
You decide what's worth remembering. API specs, architecture decisions, rules that must never be broken.
> lock_context(
topic="taskflow-api-architecture",
content="TaskFlow uses Hono on Cloudflare Workers...",
priority="important",
tags="api,architecture,taskflow"
)
✓ Locked as v1.0 (important priority)Stompy stores it as an immutable versioned snapshot. Change something later? That's a new version. The original stays intact.
Under the hood


The Tool: context_search
Two months later, you need that architecture decision. You don't remember what you called it.
> context_search("taskflow database setup")
Found 3 contexts (semantic match):
• taskflow-api-architecture (94% match)
• database-connection-pool (87% match)
• neon-postgres-setup (82% match)Stompy searches semantically. Even though you stored it as "api-architecture," searching for "database setup" finds it — because the content mentions PostgreSQL.
Under the hood
The Tool: project_switch
You're not just working on TaskFlow. There's that article publishing system. The Stompy brand work. That side project you swear you'll finish.
> project_switch("articles")
✓ Switched to articles
✓ Loaded 8 contexts from last session
✓ Ready to continue where you left offEach project gets isolated memory. TaskFlow's API conventions don't leak into your personal blog.
Under the hood


The Tool: ingest_document
That architecture diagram you made? The PDF spec from the client? The screenshot of the whiteboard session?
> ingest_document("system-architecture.png", tags="architecture,diagram")
✓ AI analyzed image content
✓ Generated description: "System architecture showing three
microservices connected via message queue..."
✓ Created multimodal embeddings
✓ Stored in S3, indexed for searchStompy doesn't just store files — it understands them.
Under the hood
The Tool: detect_conflicts
You stored "API responses must use camelCase" last month.
Today you stored "All JSON fields should be snake_case."
Stompy notices.
> detect_conflicts(scope="recent")
⚠️ Conflict detected:
Context A: "api-response-format" says camelCase
Context B: "json-standards" says snake_case
Confidence: 94% contradiction
Use resolve_conflict() to choose which to keepUnder the hood


The Tool: recall_context
You know exactly what you need. Just ask for it by name.
> recall_context("auth-decisions")
📌 auth-decisions v2.1
"JWT with refresh tokens. 15min access, 7d refresh.
MUST use httpOnly cookies. NEVER expose in localStorage."No digging through old chats. No re-making decisions you already made. It's all there.
Memory isn't just storage. It's active knowledge management.
Change your mind? That's fine. Stompy keeps the history. Roll back if needed. See how your understanding evolved.
always_check — Critical rules. important — Core knowledge. reference — Background info.
What's getting accessed? What's going stale? Where are the gaps? Stompy tracks usage patterns.
Too long to re-read? Local LLM generates concise summaries on demand. Get the gist without the scroll.
The Agent
Maya's N8N workflow runs every night, processing support tickets:
// N8N workflow calls Stompy MCP:
{
"tool": "recall_context",
"args": { "topic": "support-response-templates" }
}
// Returns templated responses for the agentStompy speaks MCP — the universal protocol. Claude Desktop. Claude Code. N8N. Cline. Any MCP client.

Stompy is an MCP server. Any MCP-compatible client gets persistent memory.
One plan. Everything included. No surprises.
when we launch. No enterprise pricing tiers. No "contact sales."
We'll email you when it's ready. We won't email you about anything else.

Neither will you.
"No memories yet. Which is fine. Totally fine. Stompy's just here. Waiting."