meridiaanWorks with every MCP client
meridiaan exposes a standard MCP endpoint. Configure it once in your tool of choice and your agent has project context automatically.
Built on MCP, so it connects the same way everywhere
meridiaan runs as a standard MCP server. Model Context Protocol is an open standard for feeding project context to AI agents: every client that speaks it connects through the same endpoint, with a few lines of config and no plugin to install.
We've verified the full round trip against production with Claude Code, GitHub Copilot and OpenAI Codex. Cursor, VS Code, Claude Desktop and every other MCP client connect through the same endpoint.
Open standard
MCP is an open protocol for connecting agents to external context. Every tool that adopts it can reach meridiaan out of the box, with no custom plugin or adapter to install.
One endpoint per project
Each project exposes its own MCP endpoint, protected by a dedicated Bearer token. Configure it once in your client and the agent sees every active topic as a native tool.
No lock-in
The same knowledge base can be queried at the same time from different tools and by different people on the team. Changing editor never touches your knowledge base.
One endpoint that speaks both eras of MCP
The protocol has been through several revisions, and the July 2026 spec changed how a client opens the connection. meridiaan negotiates the revision at handshake: tools still on the earlier revisions and tools on the current one both connect to the same endpoint. In the spec's own vocabulary, it is a dual-era server, so a new client and an older one work side by side with no migration on your part.
Transport is Streamable HTTP: a single stateless endpoint, with a streamed response only when a call needs one. No always-open socket to keep alive, so it sits behind the same proxies and load balancers as the rest of your stack.
Whatever the client, you are handing it the same two things: the endpoint URL and a Bearer token. Most tools take them as a small JSON entry shaped like this.
// a typical MCP client config
{
"mcpServers": {
"my-project": {
"type": "http",
"url": "https://mcp.meridiaan.io/mcp/<project-id>",
"headers": {
"Authorization": "Bearer <api-key>"
}
}
}
}
The file it lives in, the exact root key and whether it is per-project or global differ from tool to tool. We mapped all of them. Once you sign up, the Connection page hands you the block already filled in for your project.
One endpoint. Any agent.
Create a project, copy the endpoint, and paste it into your tool.