Memnode
Give Claude Code or Cursor a durable memory layer with traceable edits instead of stuffing everything into the context window.
Overview
Memnode is an MCP server for the Build phase that provides persistent, inspectable agent memory with lineage and correction over a hosted endpoint.
What is this MCP server?
- Hosted streamable-HTTP MCP at https://api.memnode.dev/mcp (no local server required for remote use)
- Persistent memory with lineage so you can see how facts evolved
- Correction workflow so agents can fix wrong memories instead of blindly appending
- Inspectable store—audit what the agent remembered before you trust it in production
- Version 0.1.0 MCP server in the official catalog schema
- Catalog version 0.1.0
- Remote transport: streamable-http at https://api.memnode.dev/mcp
- Capabilities called out in catalog: persistent memory, lineage, correction, inspectability
What problem does it solve?
Coding agents forget prior decisions between sessions and cannot explain or fix what they “remembered,” so solo builders repeat context and lose trust.
Who is it for?
Indie builders running long-horizon agent workflows who need accountable, editable memory beyond the current chat.
Skip if: Teams that only need one-off codegen with no cross-session state, or anyone unwilling to curate what gets stored in agent memory.
What do I get? / Deliverables
After you register the Memnode MCP endpoint, agents read and update durable memories with visible history and explicit corrections instead of fragile chat-only recall.
- Registered hosted Memnode MCP connection in your agent client
- Persistent memory records agents can read, inspect, and correct across sessions
Recommended MCP Servers
Journey fit
Agent memory is part of the product you ship—tooling that makes the assistant reliable across sessions sits in Build. Memnode is MCP infrastructure for agents (store, inspect, correct memories), which maps directly to agent-tooling on the shelf.
How it compares
Hosted memory MCP for agents—not a vector DB skill or a generic note-taking integration.
Common Questions / FAQ
Who is dev.memnode/memnode for?
Solo and indie builders shipping agent-assisted products who want durable, auditable memory in Claude Code, Cursor, or other MCP clients.
When should I use dev.memnode/memnode?
Use it during Build when your agent must retain project facts, preferences, and corrections across many sessions without bloating every prompt.
How do I add dev.memnode/memnode to my agent?
Add the remote MCP server URL https://api.memnode.dev/mcp (streamable-http) in your client’s MCP settings, then invoke memory tools from your agent session.