Features

Works with 50+ MCP clients.

Claude, Codex, Cursor, Copilot or a local model: if it speaks MCP, it speaks Meridiaan. One address, one click in the browser, no secrets lying around.

Secured with OAuth 2.1.

Meridiaan authorizes clients with OAuth 2.1 and PKCE, the current standard for secure authorization and the one the MCP specification adopts. Paste the Workspace address, confirm in the browser, and the client gets a token that expires, renews itself and can be revoked from the app.

A token for the clients that don’t support OAuth yet
A ready configuration for every client, in the app
One-click install where the client allows it: Cursor, VS Code, LM Studio

As defined in the Authorization section of the MCP specification.

Natively Dual-Era MCP.

The 2026-07-28 revision of the MCP specification changed how a client opens the connection, splitting clients into two eras. Meridiaan serves both from the same address: it negotiates the revision at handshake, so clients still on the earlier revisions and clients on the current one work side by side, with nothing to migrate.

Up to 2025-11-25Clients still on the earlier revisions 2026-07-28Clients on the current revision

Transport is Streamable HTTP: one stateless endpoint, with a streamed response only when a call needs one.

Any Agent, any provider.

The same knowledge, from whichever client each person prefers.

Claude Code in one terminal, a model running on your own machine in another: the same Workspace at the same time, and Signals tells each one what the other is doing.

Beyond the chat.

SDKs and frameworks

The official MCP SDKs cover TypeScript, Python, Java, C# and more, and any framework with an MCP client connects too: LangChain, LangGraph or CrewAI, for example.

Agents as a bridge

Knowledge sitting in another tool? Your Agent reads it from another knowledge base, a tracker or a document, and writes it into Meridiaan.

.cursor/mcp.json

{
  "mcpServers": {
    "your_project": {
      "url": "https://mcp.meridiaan.io/mcp/<workspace-id>",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

For clients without OAuth.

Some clients can’t sign in with OAuth yet. For them, every member has a personal token, and the app hands over the block already written for their client: the address, the token and where to paste it.

The file, the root key and the scope change from tool to tool: we mapped all of them.

One address. Any Agent.

Create a Workspace, copy its address and paste it into your client.

Create an account Getting started guide