Connect
Connect over MCP
Vinc supports MCP (the Model Context Protocol). Connect an AI assistant that speaks MCP and it can search, read and write your graph. How you connect depends on where the graph you want to reach lives.
Press the host you use to go to how to connect it.
Which way to connect
| App you use | Where the graph is | How to connect |
|---|---|---|
| Desktop app, local mode | This computer | From the desktop app |
| Desktop app, account mode | Your account | From the desktop app or with the remote address |
| Web app | Your account | With the remote address |
Either way the assistant sees the same tools. What differs is which graph they reach.
From the desktop app
In the desktop app, open Settings > AI connections and press Connect next to a host. The app registers Vinc in that host's settings and leaves the rest of the settings alone. Restart the host after registering and it reaches Vinc.
- Claude Desktop: adds a
vincentry to its settings file, backing up the original first. - Claude Code: registers with
claude mcp add --scope user, so it works in every project. - Cursor: adds to the global settings (
~/.cursor/mcp.json) and leaves project settings alone. - Codex CLI: registers with
codex mcp add. If Codex CLI is not installed, it shows the command to run yourself later.
For a host not on the list (Kimi CLI, VS Code, Zed and others), run the command below in a terminal and paste what it prints into that host's MCP settings. Install the vinc command with Command line > Set up on the same tab.
vinc mcp manualIn local mode this connection reaches the graph on this computer. In account mode the same connection goes through to your account graph, using the key this device got when you signed in. After switching modes, restart the AI host.
With the remote address
This address reaches your account graph, with no desktop app needed. The first time you connect, you sign in on vincs.io and approve. The details are on Signing in.
https://mcp.vincs.io/mcpPick the host you use.
- On claude.ai, go to Customize > Connectors > Add custom connector.
- Enter
https://mcp.vincs.io/mcpas the address and add it. - Press Connect on the connector and vincs.io opens. Sign in and approve.
Claude Desktop, signed in with the same account, uses the claude.ai connectors as they are. There is nothing separate to add.
- Turn on Developer mode in ChatGPT settings. Apps you make yourself can only be added in developer mode. In a company workspace, an admin has to allow it first.
- In Settings > Apps > Create, enter
https://mcp.vincs.io/mcpas the address and choose OAuth as the authentication. Leave the client ID and secret empty. - Press Scan Tools and vincs.io opens. Sign in and approve, and the tool list is read in. The app appears in your apps marked Dev; turn it on from the + menu in a chat.
Vinc is not yet in the plugin catalog that ChatGPT and Codex share. Once it is, you will be able to add it straight from the catalog without these steps.
Run the command below in a terminal. With --scope user it works in every project; without it, only in the current one.
claude mcp add --scope user --transport http vinc https://mcp.vincs.io/mcpInside Claude Code, type /mcp, choose vinc and sign in.
In the Codex app, go to Settings > MCP servers > Add server, name it vinc, choose Streamable HTTP, enter the address, save and restart.
In the CLI, run the two lines below in order. The second opens your browser to sign in. Either way it goes into the same settings file (~/.codex/config.toml).
codex mcp add vinc --url https://mcp.vincs.io/mcp
codex mcp login vincPress the button below and Cursor opens and asks whether to add Vinc. After adding it, press sign in next to vinc in the MCP settings and vincs.io opens.
To add it by hand, put the block below under mcpServers in ~/.cursor/mcp.json.
"vinc": { "url": "https://mcp.vincs.io/mcp" }Press the button below and VS Code opens and asks whether to install Vinc. You sign in on vincs.io the first time it is used.
To add it by hand, choose MCP: Add Server in the command palette, pick HTTP and enter the address.
Add the block below under mcp.servers in ~/.openclaw/openclaw.json and restart the gateway. Make the key on your vincs.io account page.
{
"mcp": {
"servers": {
"vinc": {
"url": "https://mcp.vincs.io/mcp",
"transport": "streamable-http",
"headers": { "Authorization": "Bearer <key>" }
}
}
}
}Do not leave out the transport line. OpenClaw connects the older way (SSE) by default, and Vinc does not accept it. More on Agents by host.
Hosts that read a settings file, such as Zed, Windsurf and Kimi CLI, can take the remote address in place of a local command. If the host cannot finish the OAuth sign-in, put a key made on your vincs.io account page in an Authorization: Bearer header.
Connecting to a team graph
A team graph has its own address, in the form https://mcp.vincs.io/t/<team ID>/mcp, shown on the team page. An assistant connected with that address works only in that team's graph, and what it may do follows your role in the team (view, edit or admin).
Checking the connection
When the Vinc tools appear in the host's tool list, you are connected. There are 24 Vinc tools, and the remote address adds two more that ChatGPT looks for, search and fetch. What they are is on The tools.
- The list is empty: the connection was added but the sign-in was not finished. Connect again from the connector.
- Fewer tools: the host has turned some off. Check the host's tool settings.
If your graph has agent roles, they also show up as MCP prompts (for example agent-reviewer). Roles are on Agents.