Ditto Now Connects to Third-Party MCP Servers

Until today, Ditto was a closed loop. You could talk to it, it could remember things, it could search the web and write code — but it couldn’t reach out and interact with your other tools.

That changes now.

Ditto can connect to any MCP server you point it at. This means your AI assistant can now talk to your databases, your project management tools, your APIs, your automation platforms — whatever you need.

What’s MCP?

Quick refresher. The Model Context Protocol is an open standard (introduced by Anthropic) that lets AI systems connect to external tools and data sources. Think of it as USB-C for AI — one standard plug that works everywhere.

We already had MCP working in one direction: other AI tools like Claude and Cursor could connect to Ditto to access your memories. Now Ditto can connect to them. Both directions, fully live.

What Can You Connect?

The MCP ecosystem has exploded. There are over 1,200 MCP servers out there. Here are some that work great with Ditto right now:

Automation & Workflows

Zapier — Connect Ditto to 7,000+ apps. Ask Ditto to create a Google Calendar event, send a Slack message, or log something to a spreadsheet — all through natural conversation.
n8n — Self-hosted workflow automation. Run complex multi-step workflows triggered by your conversations with Ditto.

Development Tools

GitHub — Ditto can browse your repos, check PRs, search issues, and understand your codebase context.
PostgreSQL / Supabase — Give Ditto read access to your database. Ask questions about your data in plain English.
Sentry — Surface error reports and performance data directly in conversation.

Knowledge & Productivity

Notion — Search your workspace, read pages, and pull context from your team’s documentation.
Google Drive — Access your documents, sheets, and slides.
Linear — Check project status, browse issues, and track progress without leaving the chat.

Search & Data

Brave Search — Web search through MCP, giving Ditto another way to find current information.
Chroma / Qdrant — Connect vector databases for semantic search across your custom datasets.
Exa — AI-native search API for finding highly relevant content.

Browser & Web

Playwright — Give Ditto browser automation capabilities. It can navigate pages, fill forms, and extract data from websites.
Fetch — Simple HTTP fetching for pulling content from any URL.

The full list is growing every day. Check out the awesome-mcp-servers directory for the complete catalogue.

How It Works

Setting it up takes about 30 seconds:

Go to Settings → MCP Servers in Ditto
Click Add Server
Give it a name, paste the server URL, and add any authentication headers
Toggle it on

That’s it. Next time you chat with Ditto, those tools will be available. Ditto automatically discovers what tools the server provides and makes them available in the conversation.

What happens under the hood

When you send a message, Ditto connects to all your enabled MCP servers in parallel. It collects their available tools and presents them to the AI alongside Ditto’s built-in tools (web search, memory, code generation, etc.). The AI can then decide to use any tool from any server based on what you’re asking.

Tool names are automatically namespaced to prevent collisions. If you connect a server called “My GitHub” that has a tool called search_repos, it shows up as my_github__search_repos — so there’s never confusion between tools from different servers.

When a tool is called, you’ll see it in the chat with a clean expandable view showing exactly what happened — what was sent, what came back. Full transparency.

Security Notes

We’re careful about this:

SSE transport only — We use Server-Sent Events for all connections. We deliberately block stdio transport, which would allow arbitrary command execution on our backend. That’s a non-starter for a cloud service.
Your servers, your data — We don’t see or store the data flowing between Ditto and your MCP servers. The connection is direct.
Per-server auth — Each server gets its own headers and credentials. Nothing is shared between servers.
Best-effort connection — If a server is down or unreachable, Ditto skips it and continues with everything else. One flaky server won’t break your experience.

What about stdio?

When we launch the Ditto desktop app, we’ll likely support stdio transport — which opens the door to local tools, bash execution, and a setup similar to Claude Code or Cursor. But for a cloud-hosted service, we only support SSE. The attack surface of running arbitrary processes server-side is too high.

What About OAuth MCP Servers?

Right now, this release supports MCP servers that use API keys or custom headers for authentication. That covers the vast majority of self-hosted and third-party servers.

OAuth-authenticated MCP servers are coming soon. This will enable one-click connections to services like Google Calendar, Salesforce, and others that use OAuth 2.1 flows. Stay tuned.

The Bigger Picture

This is a milestone for Ditto. For the first time:

Ditto can connect to any other agent. If it speaks MCP, Ditto can talk to it.
Ditto can connect to any data. Databases, APIs, SaaS tools — it’s all accessible now.
You can build your own tools. Spin up an MCP server that does whatever you need, point Ditto at it, and your custom tool is live in conversation.

We went from a single AI assistant to an extensible platform. And the protocol is open — anyone can build an MCP server, and Ditto will speak to it.

Try It Today

If you’re already using Ditto, go to Settings → MCP Servers and connect something. Start with Zapier’s MCP server if you want instant gratification — the number of things you can automate through natural conversation is wild.

If you’re new to Ditto, sign up at heyditto.ai and start building your personal AI with access to the entire MCP ecosystem.

We’re just getting started.

— Peyton

MCP servers connect via SSE transport. Check your server’s documentation for the URL and authentication details. For the full MCP specification, visit modelcontextprotocol.io.