Stompy Pro

Memory for machines
that work with machines

Same Stompy. Same $4.99. Just... more acronyms.

Not a different product—just more ways to use the one you already have.

Choose your use case

Your N8N has the memory of a— actually, it has no memory. That's the problem.

N8N's Window Buffer gives you 20 messages. Stompy gives you... more than that. Quite a lot more, actually.

Stompy thinking

Cross-Device Memory

Work anywhere. Context follows.

Start a thought on your phone. Expand it on your laptop. Build it in Claude Code. Stompy keeps the thread.

MobileStompy locks it

Quick thought on the train

"This auth flow should use refresh tokens..."

DesktopStompy recalls + updates

Back at your desk

"Expanding on that auth idea from earlier..."

Claude CodeStompy ready

Time to build

Full context available. No re-explaining.

Stompy waving hello

Your context is never lost.

Switch devices. Close apps. Come back days later. Stompy remembers where you were—and what you were thinking.

Workflows

Your N8N workflow runs at 3am. It remembers 3pm.

Your customer support automation runs every night. It processes tickets, extracts patterns, makes decisions. By morning, it's forgotten everything. Tomorrow night? Same tickets. Same patterns. Same "insights" discovered for the fifteenth time.

With Stompy, your workflow locks what it learns:

workflows-example.ts
// N8N workflow - end of nightly run
await stompy.lock_context({
topic: "support-patterns-dec-2024",
content: `Recurring issues this week:
- Auth timeout: 34 tickets (spike from EU region)
- Payment retry loop: 12 tickets (Stripe webhook delay)
- Mobile app crash: 8 tickets (iOS 17.2 specific)`,
tags: "support,patterns,automation"
});
// Next night's run
const patterns = await stompy.recall_context("support-patterns-dec-2024");
// → Knows about the EU auth issue. Doesn't re-discover it.

Your automation builds institutional knowledge. Every run makes the next one smarter.

Stompy taking notes
Agents

Your WhatsApp agent forgot your name. Again.

You've built messaging agents on WhatsApp, Telegram, and Discord through platforms like OpenClaw. They're brilliant conversationalists—for exactly one session. Sessions reset daily. Or on idle timeout. Your family assistant that knew everyone's dietary restrictions and the ongoing Easter planning? Blank. The project bot tracking three sprints of context? Gone. Multi-agent routing makes it worse. When the generalist hands off to a specialist, the specialist starts cold. All that context? Not passed along.

With Stompy, your messaging agents remember every conversation:

agents-example.ts
// Agent saves user context after each conversation
await stompy.lock_context({
topic: "user_mum_whatsapp_context",
content: `Margaret: vegetarian, birthday March 15th
Currently planning Easter for 12 people
Nephew Jake is gluten-free
Shortlisted: The Garden Room, Villa Rosa`,
priority: "important",
tags: "family,whatsapp,preferences"
});
// Next morning — session resets, agent wakes up
const context = await stompy.recall_context(
"user_mum_whatsapp_context"
);
// → "Morning! Did you check if The Garden Room
// can do gluten-free for Jake?"
// NOT: "Hello! I'm your assistant. How can I help?"

Your messaging agents remember every conversation. Every user. Every preference. Session resets become invisible.

Stompy coordinating agents
Teams

Sarah left for vacation. Her Claude didn't.

Sarah spent three days getting Claude up to speed on the auth refactor. The edge cases. The reasons behind the weird naming. The "don't touch this" comments that aren't in the code. Then she left for two weeks. You inherited the PR. "Hey Claude, why did Sarah use this pattern?" "I don't have context on Sarah's previous decisions..."

With Stompy, context survives the handoff:

teams-example.ts
// Sarah, before vacation
await stompy.lock_context({
topic: "auth-refactor-context",
content: `Auth Refactor Notes (Dec 2024)
Why the weird token naming:
- accessToken vs access_token: Legacy API compatibility
- refreshToken stored in httpOnly cookie, NEVER localStorage
The "don't touch" parts:
- session-validator.ts lines 45-67: Race condition fix
- Looks wrong but handles concurrent refresh correctly
Edge cases discovered:
- Safari private mode: cookies don't persist
- Corporate proxies: may strip custom headers`,
priority: "important",
tags: "auth,refactor,handoff"
});
// You, picking up the PR
const context = await stompy.recall_context("auth-refactor-context");
// → "Oh, THAT'S why it's like that."

Knowledge transfers without meetings. Onboarding happens in the codebase, not in Slack.

Stompy preserving team knowledge

Delta Evaluation

Not all context is created equal

Stompy classifies everything. Automatically. While you weren't looking.

NEW

Novel information

Stored immediately.

Finally, something interesting.

UPDATE

Refinement of existing knowledge

Merged.

Oh, this again. But slightly different. Fine.

REDUNDANT

Already know this

Acknowledged, not stored.

Yes. You mentioned. Stompy remembers.

CONFLICT

Contradicts existing knowledge

Flagged.

Wait. That's not what you said before. We should probably talk about this.

Your agents don't drown in duplicate context. Your workflows don't re-explain themselves. Your team doesn't lose decisions in the void.

MCP Integration

Connect via MCP

One config. Instant memory. Works with anything that speaks MCP.

Claude Desktop

MCP Client

Stompy MCP

Local Server

Stompy Cloud

Memory API

claude_desktop_config.json
{
"mcpServers": {
"stompy": {
"command": "npx",
"args": ["-y", "@anthropic/stompy-mcp"],
"env": {
"STOMPY_API_KEY": "your-api-key"
}
}
}
}
Claude Desktop
N8N
Any MCP Client

Your AI finally has somewhere to put things.

Beta: Free for Early Users

Simple, Transparent Pricing

Choose the plan that fits your usage. All plans include core Stompy features.

MonthlyAnnualSave 33%

Free

For casual users & evaluation

$0.00/mo

Usage Limits

  • 10 hrs/month active time
  • 512MB storage
  • Unlimited projects
  • Semantic search
  • Document ingestion
  • Community support
Most Popular

Pro

For regular users & hobbyists

$4.99/mo

Billed annually ($60/year)

Usage Limits

  • 75 hrs/month (~2.5 hrs/day)
  • 10GB storage
  • Everything in Free
  • Priority support
  • Advanced analytics
  • API access

Power

For heavy users & developers

$19.99/mo

Billed annually ($240/year)

Usage Limits

  • 300 hrs/month (~10 hrs/day)
  • 50GB storage
  • Everything in Pro
  • Extended usage hours
  • Bulk operations
  • Priority queue

Enterprise

For teams & organizations

Custom

Usage Limits

  • Unlimited active time
  • Dedicated compute
  • Everything in Power
  • Team collaboration
  • SSO & SAML
  • Dedicated support
Contact Us

All plans include

PostgreSQL databaseS3 document storageVoyageAI embeddingsOpenRouter Vision

We'll email you when it's ready. We won't email you about anything else.

Your workflows remember now.

Your agents share context. Your team keeps decisions.

"Finally. Someone who appreciates a good schema."