Agent Memory
Give Claude Code or Cursor a remote MCP layer so coding agents can store and recall session memory across chats without building your own memory API.
Overview
io.github.lazymac2x/agent-memory is a MCP server for the Build phase that exposes a Cloudflare Workers–hosted remote endpoint so coding agents can persist and retrieve memory over streamable-http.
What is this MCP server?
- Hosted Cloudflare Workers MCP server at api.lazy-mac.com with streamable-http transport
- Remote-only MCP registration—no local stdio binary required in the repo
- Pairs with agent and SaaS shapes that need cross-session recall for solo builders
- Open-source API implementation on GitHub (lazymac2x/agent-memory-api)
- Server schema version 1.0.0 aligned with Model Context Protocol 2025-09-29 metadata
- MCP server version 1.0.0
- 1 streamable-http remote URL documented
- Hosted on Cloudflare Workers (lazy-mac.com)
What problem does it solve?
Agent chats forget prior decisions unless you bolt on a custom memory store and MCP wiring yourself.
Who is it for?
Indie builders prototyping AI copilots or internal agents who want a hosted memory MCP endpoint with minimal local setup.
Skip if: Teams that require on-prem memory, full data residency control, or richly documented tool schemas in this README alone.
What do I get? / Deliverables
After you register the remote MCP URL, your agent can call memory tools through standard MCP instead of ad-hoc prompts or copy-pasted notes.
- Registered remote MCP server pointing at the agent-memory endpoint
- Agent-callable memory tools over MCP once the client connects
- Reference to version 1.0.0 server metadata for catalog and compliance checks
Recommended MCP Servers
Journey fit
Persistent agent memory is wired during product build when you connect agent tooling to external services, even though recalled context helps later operate and grow phases. integrations is the canonical shelf because this server is an HTTP MCP bridge (streamable-http) that plugs memory into the agent stack rather than shipping UI or backend app code directly.
How it compares
Remote MCP memory service, not an in-repo agent skill or local SQLite scratchpad.
Common Questions / FAQ
Who is io.github.lazymac2x/agent-memory for?
Solo and small-team builders using MCP-enabled coding agents who need cross-session memory without building a Workers API from scratch.
When should I use io.github.lazymac2x/agent-memory?
Use it during Build when you are wiring agent integrations and want a remote memory bridge before you invest in a self-hosted store.
How do I add io.github.lazymac2x/agent-memory to my agent?
Add the streamable-http remote https://api.lazy-mac.com/agent-memory/mcp in your client’s MCP config, then restart the agent and verify tools load per the agent-memory-api repo.