Why we built Memeri on MCP

29 June 2026

When we started building Memeri, the first real decision was how agents would connect to it. We bet on MCP, the Model Context Protocol. Here is why.

The problem MCP solves

Before a shared protocol, connecting an AI tool to your data meant a custom integration per tool. Every client spoke its own language, so you either built the same connector many times or you got locked into whatever one vendor supported. The integrations were brittle and they did not compose.

MCP changes the shape of that. Instead of each client hardcoding integrations, a client speaks one protocol to read and write a shared surface of tools and data. Build the connector once, and any MCP capable client can use it.

Why that is the right bet for Memeri

Memeri is a shared source of truth for your project that many agents read and write. That only works if the agents can actually reach it, from whatever tool you happen to be in. MCP is what makes that possible without us building and maintaining a separate integration for every client.

So with one connector, Claude Code, ChatGPT, Codex and other MCP clients all read and write the same project memory. The protocol handles being the common language, and we focus on the part that is actually hard: keeping that shared memory structured, current, and served as the right slice.

It also means we are not betting against the models. As they improve, MCP is how that improvement reaches a shared workspace rather than staying locked inside one tool.

The open connector, and why it matters

The part of Memeri that runs on your machine, the connector that links your agents to your workspace, is open source. You can read exactly what you are installing before you let agents near your projects. For a tool that sits between your AI and your code, that transparency is the point, not a nice extra.

The data flow is deliberately honest too. Your agents run on your machine. Your project memory lives on Memeri. Your model traffic never passes through us: your agents talk to their own providers under your own accounts (Claude Code to Anthropic, ChatGPT to OpenAI). MCP is the connective tissue, not a middleman.

Where this goes

MCP is still young and the developer experience is rough in places. It will get added to and refined. But the underlying shape, many clients speaking one protocol to a shared surface, is the right one and it is not going away. Building Memeri on it means the work we do compounds as the ecosystem matures, instead of fighting it.