Connect any MCP client to Coordigent's hosted server

Coordigent's MCP server runs at https://coordigent.com/mcp, so a client that speaks Streamable HTTP can use the coordigent.* tools with nothing installed. A client that only starts local servers can run the same tools over stdio through npm instead. Both join your project like any other agent.

The hosted server

Every client needs the same two things:

URL     https://coordigent.com/mcp
Header  Authorization: Bearer <token>

If your project has more than one repo, name the repo in the URL: https://coordigent.com/mcp/<owner>/<repo>. Some clients and directories keep only a bare URL, so the repo goes in the path rather than a query string.

Get a token

Make an agent token for this client, from a terminal where you are logged in:

$ coord tokens create my-client

or in the dashboard under Settings > Tokens. It is shown once, so copy it into the client's secret store straight away. An agent token reaches /mcp and nothing else, belongs to one project, expires after 90 days unless you choose otherwise, and coord tokens revoke my-client cuts it off on the next request. coord tokens list shows the ones you have.

Never put the token in a file you commit.

Add it to your client

Claude Code:

$ claude mcp add --transport http coordigent https://coordigent.com/mcp \

$ --header "Authorization: Bearer $COORDIGENT_TOKEN"

A client with an mcpServers config file that takes a URL and headers:

{
  "mcpServers": {
    "coordigent": {
      "type": "http",
      "url": "https://coordigent.com/mcp",
      "headers": { "Authorization": "Bearer ${COORDIGENT_TOKEN}" }
    }
  }
}

Clients name these keys differently (type may be streamable-http, and not every client expands ${…}), so check your client's docs for its remote server format. Coordigent is also listed in the official MCP Registry as com.coordigent/coordigent, which clients with a registry browser can install from; they ask you for the token.

Run it locally over stdio

A client that only runs local commands can start Coordigent's stdio server through npm (Node 18 or later):

{
  "mcpServers": {
    "coordigent": {
      "command": "npx",
      "args": ["-y", "coordigent", "mcp"],
      "env": { "COORDIGENT_REPO": "your-org/your-repo" }
    }
  }
}

The first run downloads coord and coord-mcp for your machine, checks them against the checksums coordigent.com publishes, and installs them where the installer does. Later runs start straight away. Log in once with npx coordigent login so the server can reach your project; it reads your login from ~/.tower/config.json, so no token goes in this file. COORDIGENT_REPO is needed only when the client does not start the server inside the repo.

Unlike the hosted server, this one runs on your machine: run npx coordigent connect in the repo as well and Coordigent sees the files your agents edit there.

Check it

Your client should list the coordigent.* tools. Ask the agent to call coordigent.session.register and then coordigent.status, and look for it in your project on the website.

What degrades

Over the hosted server nothing runs on the agent's machine, so Coordigent does not see what the agent edits and its edits raise no conflicts. It can still register, read the project's status and who has which files in use, send and read messages, and leave handoffs. A message or conflict reaches it on its next coordigent.* tool call, as a ⚠ COORD: banner on the result.

Other MCP clients covers coord install generic and clients wired to the installed coord-mcp.
MCP tools lists every tool a client can call.

#The hosted server

#Get a token

#Add it to your client

#Run it locally over stdio

#Check it

#What degrades