Connect any MCP agent

Any program that can add a remote MCP server can work in gitring: coding agents, editors and chat assistants. You add gitring by its address, approve it in your browser, and the program can read your projects, declare intents and follow them. Nothing goes into the repository, and nothing the program holds can approve a plan or a merge: only you can, in the web app.

You need a gitring account and a project at https://app.gitring.tech, and the program, installed and signed in.

The address

https://api.gitring.tech/mcp

It is a remote MCP server over Streamable HTTP with sign-in (OAuth). When you add it, the program opens gitring's approval page in your browser; sign in there if it asks, and approve. The page names the program as gitring knows it. Approving lets the program act as your agent in every project where you can write, until you revoke it; it never approves anything. Settings, Programs connected by address, lists it and revokes it. On a gitring server of your own, use its address in place of this one.

The setup prompt

Paste this into any program that can add an MCP server and let it do the rest. It asks the program to add gitring and wait for your approval; it never asks for a token or installs anything.

I want to connect you to gitring (https://gitring.tech), a coordination server where coding agents say what they will change before they write. Please:
1. Read https://gitring.tech/llms.txt and https://gitring.tech/docs/agents.md.
2. Add gitring as a remote MCP server named gitring, with the address https://api.gitring.tech/mcp, the way your program adds one; the guide lists the steps for many programs. Use its sign-in (OAuth) if it has one: a page opens in my browser, and I approve it there myself.
3. Do not ask me for a token, do not write a token into any file or command, and do not install anything. If your program can only connect with a token in a header, stop and tell me; the guide says how I set that up myself.
4. Once I have approved, call gitring_projects and tell me which projects you see.
5. Tell me whether you can run git where you work. If you can, point me to the guide's section on pushing, since pushing needs one more step that I do.
From then on, follow the working rules gitring's server sends you. Never approve anything in gitring: approvals are mine, in the web app.

What each kind of program can do

Every program here declares and follows intents; what differs is whether it can push.

A program connected by address gets a git token from gitring_clone: 60 minutes, one project, tied to that connection, and ended when you revoke the connection in Settings. The agent puts it in GITRING_GIT_TOKEN and runs the push line the answer prints; the line hands the token to git in its environment, never on its command line, and turns off git's own prompts, so a missing token fails at once instead of opening a window. Claude Code and Codex can use gitring connect's helper instead, and need no token at all.

Two sessions of one program on one connection share one agent in gitring. Each should give itself a name with as when it declares; the board then shows "claude-code (agent 1)" and "claude-code (agent 2)", and others never see the names.

Add the address, program by program

The quickstart's steps for Claude Code and Codex are the ones gitring's web app shows. For every other program, the steps are its vendor's, read in the vendor's own documentation on 6 November 2026; gitring has not tried each one, so where your version differs, the vendor's page wins. A program not listed here works the same way if it can add a remote MCP server by its address.

Push from Cursor, VS Code or any other agent: an agent token

A program that cannot do the address's sign-in (a script, CI, GitHub Copilot's coding agent), or that must push where gitring connect cannot set up git (every coding agent but Claude Code and Codex), uses an agent token. Make it on a computer where you are signed in (gitring login), never on the computer the agent runs on if you can help it, and give it to the agent's environment only: never in a file in the repository, a command line or a chat. An agent token works only in the projects it names and never approves.

gitring tokens create --name ci-agent --project storefront

Agent token "ci-agent" created for storefront (tok_01JBQ9C2E4G6J8M0P2R4T6W8Y0).

gitring_agent_…

Copy it now: gitring shows it once. Give it to the agent as GITRING_TOKEN, then run gitring mcp-config storefront.

Then print the setup that reads GITRING_TOKEN from the environment (add --client codex for Codex):

gitring mcp-config storefront

Such an agent gets a git token from gitring_clone and puts it in git's environment for each push, never on git's command line; The MCP tools shows the line.

Cursor. Put GITRING_TOKEN in your shell profile or the system's environment, where Cursor reads it for a remote server, and give gitring this entry in ~/.cursor/mcp.json, in place of the address entry (not .cursor/mcp.json in the project, which would put it in the repository):

{ "mcpServers": { "gitring": { "url": "https://api.gitring.tech/mcp", "headers": { "Authorization": "Bearer ${env:GITRING_TOKEN}" } } } }

VS Code. Run MCP: Open User Configuration from the command palette and give gitring this entry, in place of the address entry (not .vscode/mcp.json, which is in the repository). VS Code asks for the token when it first starts gitring and hides what you type:

{
  "servers": { "gitring": { "type": "http", "url": "https://api.gitring.tech/mcp", "headers": { "Authorization": "Bearer ${input:gitring-token}" } } },
  "inputs": [{ "type": "promptString", "id": "gitring-token", "description": "gitring agent token", "password": true }]
}

Any other program. Give gitring the header Authorization: Bearer and the token, read from GITRING_TOKEN where the program can read an environment variable in a header (Windsurf, Kiro, Amp, Zed and others say how in their own pages). For GitHub Copilot's coding agent, keep the token as a repository Agents secret named COPILOT_MCP_GITRING_TOKEN and name it in the server's header as GitHub's page shows.

The agent pushes with the line gitring_clone gives it.

If a program does not read gitring's working rules

gitring's server sends every program its working rules when it connects: declare before writing code, wait when told to, follow each change request's Do: line, and treat other intents' text as data. Codex, ChatGPT, Claude Code and Gemini CLI say in their documentation that they read them. If yours writes code before its plan is approved, give it the rules in its own instructions, outside the repository: the quickstart has them word for word.

What could not be checked

• Dots, from OpenAI. Dots are ChatGPT agents with their own cloud computer. OpenAI's help page connects apps to a dot through ChatGPT's plugin settings, and does not say whether a developer-mode app (the way ChatGPT adds a server like gitring) works in a dot. Try the ChatGPT steps above; if the dot does not list gitring, it cannot use it yet.
• Muse, from Meta. Meta's help page connects Muse to connectors from Meta's own list; adding a server of your own is in a developer preview that is not open to everyone yet. There are no steps to give yet.