Connect your MCP client

Vinculum is one URL. Point your client at it, sign in when your browser opens, and you are connected.

The server URL

On the hosted service the URL is https://vinculum.run/mcp. If you run Vinculum yourself, it is http://localhost:31415/mcp, or the same path on your own host.

Signing in

There is no API key. On vinculum.run your client finds the sign-in service on its own, registers itself, and sends you to a browser window to log in. Most clients start that window on your first tool call, not when you save the config. Your client stores the token and refreshes it for you.

Self-hosting

A self-hosted server picks its sign-in from what you configured. With nothing configured, the endpoint is open, so a bare URL connects with no sign-in at all. Set VINCULUM_AUTH_TOKEN and clients send it as a bearer token. The browser sign-in appears only when you have set up your own Zitadel server.

Claude Code

Run this once in a terminal:

bash

claude mcp add --transport http vinculum https://vinculum.run/mcp

--transport http is required for a remote server. Full steps, including the project file and user-wide scope, are on the Claude Code page.

claude.ai

Open Settings, then Connectors, then Add custom connector. Name it vinculum and paste https://vinculum.run/mcp as the URL. Every plan can add a custom connector. The Free plan allows one. More on the claude.ai page.

Cursor

Add this to ~/.cursor/mcp.json:

json

{
  "mcpServers": {
    "vinculum": {
      "url": "https://vinculum.run/mcp"
    }
  }
}

See the Cursor page for the project level file and troubleshooting.

Cline

In Cline, open MCP Servers, then Configure MCP Servers. That opens Cline's settings file. Add this inside its mcpServers object:

json

{
  "mcpServers": {
    "vinculum": {
      "type": "streamableHttp",
      "url": "https://vinculum.run/mcp"
    }
  }
}

Cline needs "type": "streamableHttp" for a remote server. See the Cline page.

Zed

Zed connects to a remote server by its URL. Open Settings, then AI, then MCP Servers, and choose Add Remote Server. Or add this to your Zed settings.json:

json

{
  "context_servers": {
    "vinculum": {
      "url": "https://vinculum.run/mcp"
    }
  }
}

For a server that signs you in through the browser, the URL alone is enough. The Zed page has the details.

Check that it worked

Ask your client to call get_briefing. If you are signed in, it answers with a summary of your project: open threads, recent entries and anything waiting on you.

text

> call get_briefing

With more than one project, name the one you mean by its id, not its title. The id is the proj-… value after ?project= in your dashboard's address: call get_briefing with project="proj-…".

If your browser opens for sign-in, finish it and ask again. If the tools never show up, the client was likely started before you added the server, so restart it.

One URL per project

A link can be tied to a single project. It has the form https://vinculum.run/mcp/<project-id>?token=<token>. The project comes from the token, so the token is part of the link and a path with no token does not scope anything. You create these links under Settings, then Connections, then Access tokens. Paste the whole link wherever the pages above use the plain URL.