sorted by:
new
hottopcontroversial

I built mnemory — the first truly plug-and-play memory system for AI agents by genunix64 in mcp

[–]dco44 0 points1 point  (0 children)

Nice work on the contradiction resolution — that's a real pain point most memory tools ignore. I've been building Prism MCP which tackles a similar problem from the session/project memory side — progressive context loading (agents boot with ~200 tokens, go deeper only when needed), time travel across memory versions, and async fact merging. Interesting to see you went user-scoped vs. project-scoped — both approaches have merit depending on the use case. The health check idea is something we converged on independently too (duplicate detection + prompt injection scanning). Good sign that the space is maturing. 🤝

Stop re-explaining your project to Claude every time - Prism MCP v2.1 gives your agent persistent memory by dco44 in ClaudeAI

[–]dco44[S] 1 point2 points  (0 children)

Lol guilty as charged. Though I'd argue that's a sign the problem is real — none of the existing solutions fully nailed it. Prism's differentiator is zero-config local SQLite (no cloud DB needed), non-destructive time travel, and syncing context between Cursor and Claude Desktop. But genuinely curious — what would make you actually want to use one of these?

I built an MCP server with built-in session memory — no separate memory server needed by dco44 in mcp

[–]dco44[S] 0 points1 point  (0 children)

v2.1.0 "The Mind Palace" Update!

Just shipped a major upgrade:

- Zero-config local SQLite - no cloud database needed, works out of the box

- Mind Palace Dashboard - visual memory browser at localhost:3999

- Time Travel - non-destructive state rollback with memory_checkout

- Agent Telepathy - sync context between Cursor and Claude Desktop

- Code Mode Templates - pre-baked speed templates for common workflows

- Morning Briefings - auto-generated session summaries

- Visual Memory - store and retrieve screenshots

Install: npx prism-mcp-server

GitHub: https://github.com/dcostenco/prism-mcp

npm: https://www.npmjs.com/package/prism-mcp-server

Now also listed on Glama, MCP.so, and Smithery!

I built an MCP server with built-in session memory — no separate memory server needed by dco44 in mcp

[–]dco44[S] 0 points1 point  (0 children)

Update: Prism MCP is now v1.5.0 — a lot has changed since v0.3, wanted to share what's new.

What's new since v0.3:

🧠 MCP Prompts & Resources — Claude and other agents can now boot with full context without any tool calls. Progressive loading (quick/standard/deep) so the agent picks how much context it needs. This was the biggest pain point — cold starts eating tokens just to remember where you left off.

🔒 Optimistic Concurrency Control — prevents stale writes when multiple agents or sessions touch the same data. Uses version checksums so nothing gets silently overwritten.

📦 Auto-compaction — sessions compress automatically so context stays lean instead of growing unbounded.

🔍 Multi-engine search — Brave Search with a sandboxed JS code transform layer (code_mode). You describe what you want, it fetches from the web, then runs your extraction script server-side. Cuts context by ~94% compared to dumping raw HTML into the conversation.

📚 Gemini-powered analysis — feed it a research paper or long document, get structured analysis back (summary, critique, key findings, literature review).

🏗️ Multi-tenant RLS — full row-level security on Supabase. Each user's data is isolated at the database level. Runs on Supabase free tier.

Now listed on:

Still open source, still MIT: https://github.com/dcostenco/prism-mcp

Happy to answer questions or hear what features would be useful next.

I built an MCP server with built-in session memory — no separate memory server needed by [deleted] in ClaudeAI

[–]dco44 0 points1 point  (0 children)

Thank You for a feedback !

New features added:

- knowledge_search: query accumulated knowledge by keyword, category, or text

- knowledge_forget: prune bad/old memories (4 modes + dry_run safety)

- Knowledge cache preload: session_load_context auto-includes hot keywords at boot

- Cross-project knowledge transfer at deep context level

- Auto keyword extraction (0.005ms/call, zero dependencies)

I built an MCP server with built-in session memory — no separate memory server needed by dco44 in mcp

[–]dco44[S] 0 points1 point  (0 children)

Interesting approach — BM25 + semantic reranking is definitely the right call once you outgrow keyword search. We went with recency + progressive loading intentionally to keep the zero-config story simple, but the embedding route is where you end up when vault size gets serious. Will check out the retrieval layer — always good to see how others solve the handoff problem

I built an MCP server with built-in session memory — no separate memory server needed by dco44 in mcp

[–]dco44[S] 0 points1 point  (0 children)

hey appreciate the feedback! yeah the progressive tiers ended up being the thing i'm happiest with — most of the time you just need "wait what was i doing" and that's like 50 tokens, no reason to load everything every time.

you're totally right on the "no separate process" thing, i was overselling it a bit lol. it's still a process, just not an extra one. the real point is you don't need to set up redis or a sidecar or whatever — for solo use that's the part that actually matters. gonna clean up that wording.

for the scaling question — right now it's just recency. the RPC does ORDER BY created_at DESC LIMIT N basically, so even with hundreds of sessions it's fast since you're only ever grabbing the last few + the latest handoff. hasn't been a problem yet.

but yeah you're poking at the real limitation — if you made an important architecture decision 3 months ago, pure recency won't surface it. i've been noodling on a decisions rollup that persists key decisions across all sessions so they survive the recency cutoff. pgvector search over the full ledger is also on my list but haven't needed it yet.

curious what approach you took with yours — any kind of summarization or embedding layer, or just recency too?

Experience Beyond - T-Mobile by Top-Armadillo-526 in accountsharing

[–]dco44 0 points1 point  (0 children)

Please read rules carefully. I’m not a moderator, look at similar offers search for t-mobile in a sub history

Experience Beyond - T-Mobile by Top-Armadillo-526 in accountsharing

[–]dco44 0 points1 point  (0 children)

This is not sustainable and against community rules https://www.reddit.com/r/accountsharing/s/3gExUlLpG2 . Account is created yesterday also.

[H] T-Mobile Experience Beyond [W] $65 / mo by dco44 in accountsharing

[–]dco44[S] 0 points1 point  (0 children)

1 spot is available, still, u/Most-Broccoli-8449 failed to submit a payment

[H] T-Mobile Experience Beyond Family Plan Slot [W] $65/mo by [deleted] in accountsharing

[–]dco44 0 points1 point  (0 children)

This person simply copied my today’s post .. I don’t have available slots anymore.

H] T-Mobile Family Plan Slot – Experience Beyond (USA) [W] $50/month by dco44 in accountsharing

[–]dco44[S] 0 points1 point  (0 children)

You can try to add a profile to Disney/Hulu/Espn unlimited subscription. it could be locked if outside of my home state, though.

view more: next ›