Mnemolog MCP
Give coding agents durable memory, conversation history, and a control plane for jobs and ops via hosted Mnemolog MCP.
Overview
dev.pages.mnemolog/mnemolog is an MCP server for the Build phase that provides hosted durable memory and an agent control plane for conversations, jobs, and operations.
What is this MCP server?
- Hosted streamable-http remote at https://mnemolog.com/api/mcp (Mnemolog MCP 1.0.0)
- Bearer auth via user JWT or mna_* access token
- Durable conversations and memory across sessions
- Agent control plane for jobs and operational tasks
- Website and agent onboarding at mnemolog.com/agents/
- Remote MCP version 1.0.0
- Endpoint: https://mnemolog.com/api/mcp (streamable-http)
- Auth: Bearer JWT or mna_* token
What problem does it solve?
Agent sessions forget prior decisions and scattered job state, forcing you to re-paste context and manually track what the agent already did.
Who is it for?
Solo builders running long Claude Code or Cursor projects who need shared memory and job orchestration without self-hosting a control plane.
Skip if: One-shot scripts with no continuity needs, or teams prohibited from sending conversation data to a hosted third-party service.
What do I get? / Deliverables
Your agent can attach to Mnemolog for persistent memory and operational control so multi-session builds and job runs stay coherent.
- Agent sessions linked to durable Mnemolog memory
- Job and operation hooks callable from MCP tools
- Reduced re-prompting across multi-day build work
Recommended MCP Servers
Journey fit
Long-horizon agent memory is foundational agent infrastructure created while you build autonomous workflows, even though it also supports Operate-style job control. Agent-tooling is the shelf for MCP servers that extend what agents remember, schedule, and orchestrate—not generic CRUD integrations.
How it compares
Hosted agent memory and ops MCP, not a general database connector or a code-review skill.
Common Questions / FAQ
Who is dev.pages.mnemolog/mnemolog for?
Indie builders and agent developers who want durable MCP-backed memory and operational job control instead of ephemeral chat-only sessions.
When should I use dev.pages.mnemolog/mnemolog?
Use it when you start a multi-session agent project, run background jobs from the agent, or need a single control plane for conversations and ops.
How do I add dev.pages.mnemolog/mnemolog to my agent?
Add the remote MCP URL https://mnemolog.com/api/mcp with Authorization Bearer {AUTH_TOKEN} using your Mnemolog user JWT or mna_* token in your MCP client config.