Connect your AI tool

Connect an AI tool you already use so its agent can read and write your Patchnet projects.

When to use this

You want to work in Patchnet from Claude Code, Codex, or another tool that supports MCP (Model Context Protocol) — for example, to have your coding or research agent file decisions and notes into a shared project.

Before you begin

• A Patchnet Projects account you can sign in with.
• An AI tool that supports remote MCP servers with OAuth sign-in.
• Your connection details. In Patchnet, open Settings → My workers and find the External connection card. Copy the MCP server URL (the address your tool connects to; it ends in /api/patchnet/mcp) and the Connection name (the name to give the connection in your tool).

Each value has a Copy button. The examples below use YOUR_MCP_SERVER_URL and YOUR_CONNECTION_NAME as placeholders.

How sign-in works

You do not copy a password or key into your tool. When you connect, your tool opens a browser window, you sign in to Patchnet as usual, and you approve the connection. Your tool then refreshes its access on its own.

The tool acts as you and gets your project roles — nothing more. See Roles and access.

Claude Code

Add the server from your terminal:

claude mcp add --transport http --scope user YOUR_CONNECTION_NAME YOUR_MCP_SERVER_URL

Use --scope user to use the connection in every folder on this computer, or leave it out to use it only in the current folder. Then sign in:

1. Start Claude Code and type /mcp. The connection shows that it needs authentication.
2. Choose Authenticate. A browser window opens.
3. Sign in to Patchnet and approve the connection.
4. Type /mcp again. The connection shows as connected.

Codex CLI

Open your Codex config file — ~/.codex/config.toml on macOS and Linux, or %USERPROFILE%\.codex\config.toml on Windows — and add the server, using your connection name as the key:

[mcp_servers.YOUR_CONNECTION_NAME]
url = "YOUR_MCP_SERVER_URL"

Start the sign-in:

codex mcp login YOUR_CONNECTION_NAME

Sign in to Patchnet in the browser window and approve the connection. Codex confirms that you are logged in. Run codex mcp list to check that the connection is there.

Other MCP clients

Any client that supports remote MCP servers with OAuth sign-in can connect. Add a remote server with your MCP server URL, choose the Streamable HTTP transport if your client asks, and leave authentication to the client. It finds the Patchnet sign-in on its own and opens your browser.

Step-by-step guides for more tools will be added here as each one is verified.

Check the connection

Start a new conversation in your tool and ask:

Using Patchnet, list the projects I can access.

Your agent should return the same projects you see in the browser. Next, see Work with Patchnet from your AI tool.

If something fails

• The browser window never opens — some remote or headless environments cannot open a browser for sign-in. Connect from a computer with a browser.
• The browser shows a sign-in page that never returns to your tool — your browser may have an old session. Sign out of Patchnet, or try a private browser window.
• The connection is missing or fails right away — check that the URL is exactly the MCP server URL from the External connection card, including /api/patchnet/mcp, with no trailing slash.
• Your agent sees fewer projects than you expect — the tool only sees projects you have access to. Ask a project admin to share the project with you.

Older key-based connections

Earlier versions of Patchnet Projects connected tools with a copied key. New key-based connections are no longer available. If you still have one, you can revoke it under Settings → My workers → Previous external connections, then reconnect with the steps above.

See also

• Work with Patchnet from your AI tool
• MCP tools reference