Claude Code that remembers your project.
Keep the why behind your code. Connect Claude Code to Ditto so it can retrieve saved project context and carry useful decisions into the next session.
What can you ask Claude Code with Ditto?
Use saved context before the work, and leave useful context after it. These example prompts use the memory tools exposed through MCP.
- Recover the reason behind a code change
-
“Search Ditto for why we switched auth libraries. Bring back the decision before changing token validation.”
The earlier decision needs to be saved in the memory you authorize.
Set up memory retrieval - Keep a solved bug from becoming the next mystery
-
“Save this bug’s cause, the fix we chose and the regression test in Ditto for our next session.”
Give Claude Code permission to create memories through Ditto’s MCP server.
Review memory permissions - Hand the next agent a useful starting point
-
“Save a handoff in Ditto: what changed, the checks we ran and the next unresolved task.”
Connect the next client separately and authorize access to the same memory.
Choose another supported client
Put the connection to work.
Choose a team workflow to see what to ask, what context it needs, and what you can take away.
Connect once. Put the context to work.
You’ll need Claude Code and a Ditto account. This connects to your authorized memory through MCP; it doesn’t replace your project instructions.
Add the Ditto MCP server
Run this in the project where you use Claude Code.
claude mcp add --transport http ditto https://api.heyditto.ai/mcpSign in to Ditto
Open Claude Code, run
/mcp, choose Ditto and complete the browser OAuth flow.Start with a useful decision
Ask Claude Code to save a project decision in Ditto. In a later session, ask it to retrieve that decision before it starts work.
Before you connect.
How do I connect Claude Code to Ditto?
Add Ditto as an HTTP MCP server with the command above. In Claude Code, run /mcp, select Ditto and complete the browser sign-in. The MCP setup guide also covers API-key authentication.
Does this replace Claude Code’s own memory?
No. Ditto provides an additional memory layer through MCP. Use it for context you want to retrieve across sessions or make available to other connected tools, alongside your project instructions and Claude Code’s own features.
Does connecting automatically save every conversation?
Connecting exposes Ditto’s memory tools; it does not mean every prompt is automatically stored. Ask your agent to retrieve relevant context and save useful decisions. Behavior depends on the client and instructions you configure.
Can I use the same memory in another tool?
Other supported MCP clients can connect to Ditto. The memory they can access depends on the account and permissions you authorize. Each client needs its own setup.
What can a connected app access?
Access depends on its authorization. Ditto distinguishes app memory from main memory and supports granular permissions for memory operations. Review the requested access when connecting, and use the App Permissions guide for details.
Change the tool.
Keep the context.
Bring other supported clients into the same memory workflow.