Install
Dashboard

Other MCP clients

Coordigent ships a standard stdio MCP server, coord-mcp, so any app that speaks MCP can run it. This page covers Perplexity, Claude Desktop, and any other client you wire by hand.

Perplexity

Perplexity for Mac has no config file to write into: its connectors are added in the app. So coord install perplexity writes a small launcher script and prints exactly what to enter. coord connect never sets up Perplexity on its own. Run this inside the repo:

coord install perplexity

What gets written

A launcher in the repo, .coordigent/perplexity-mcp.sh:

#!/bin/sh cd '/Users/you/code/your-repo' || exit 1 exec env 'COORDIGENT_CLIENT=perplexity' 'COORDIGENT_REPO=your-org/your-repo' 'sh' '-c' 'exec "${TOWER_BIN_DIR:-$HOME/.tower/bin}/coord-mcp" "$@"' 'coord-mcp'

Perplexity's helper does not start in a repo, so the launcher moves into one. That is why each connector belongs to one repo. COORDIGENT_CLIENT=perplexity is set because Perplexity does not say who it is when it connects. No token is written: coord-mcp reads your login from ~/.tower/config.json.

coord install perplexity --user puts the launcher under ~/.tower/perplexity/ instead, named after a hash of the repo path, so several repos can each have their own connector. Once the launcher exists in a repo, coord connect --repo-files there keeps it up to date.

Add it in the app

The installer prints these steps:

  1. In Perplexity for Mac, open Account settings > Connectors > Add Connector > Simple.
  2. Install the PerplexityXPC helper when prompted.
  3. Set Server Name to Coordigent and Command to /bin/sh followed by the launcher's full path, as printed.
  4. Save, wait for Running, then enable Coordigent under Sources.

Ask Perplexity to call coordigent.status to check it. coord doctor perplexity cannot read the app's settings, so it reports that you need to check in the app.

To update, run coord update, then remove and re-add the connector. To remove it, delete the connector in Account settings > Connectors, then delete the launcher script. coord uninstall deletes the launcher too, unless you edited it.

Claude Desktop

On macOS, coord login (and coord connect) finds Claude Desktop when ~/Library/Application Support/Claude exists, and adds a coordigent entry to claude_desktop_config.json in that folder. There is nothing else to set up and no repo file. Restart Claude Desktop to load the tools. Claude Desktop does not start the server inside a repo, so the server works out the repo on the first coordigent.* call, from the folders the app tells it about. If that call still fails and names COORDIGENT_REPO, add "COORDIGENT_REPO": "owner/name" to that entry's env.

ChatGPT

ChatGPT cannot be connected. It only accepts remote HTTP MCP servers, and coord-mcp runs on your machine over stdio. coord login and coord connect say so in their report.

Any other MCP client

Add the server to your client's MCP config by hand. To print ready-made examples, run this inside the repo; it writes nothing:

coord install generic

It prints two complete configs, one under mcpServers and one under servers, because clients disagree on the key. Copy the one your client uses. Inside a repo they find coord-mcp through $HOME ("command": "sh"); with --user they use its absolute path. If your client does not run sh, use the absolute form:

{ "mcpServers": { "coordigent": { "command": "/Users/you/.tower/bin/coord-mcp", "args": [], "env": { "COORDIGENT_REPO": "your-org/your-repo" } } } }
  • Use the absolute path to coord-mcp. Desktop apps start MCP servers with a short PATH and often cannot find ~/.tower/bin.
  • Set COORDIGENT_REPO to the repo as owner/name if the client does not start the server inside the repo. Otherwise coord-mcp reads it from the repo's origin remote.
  • Set COORDIGENT_CLIENT only to force a client Coordigent knows, such as generic.
  • Never put a token in this file. coord-mcp reads your login from ~/.tower/config.json.

To update, run coord update, then restart your client or reconnect the server. To remove it, delete the coordigent entry from the client's config.

Check it

Your client's MCP panel should list the coordigent.* tools. Ask the agent to call coordigent.status, then look for it in your project on the dashboard. coord doctor generic reminds you of this; it cannot read another app's settings.

What degrades

Coordigent assumes nothing optional from these clients: no resources, prompts, sampling, elicitation, roots or server notifications. It has no hooks in them either, so it does not see what their agents edit. They can still register, read status, and send and read messages. A message or conflict waits until the agent's next coordigent.* tool call and arrives as a ⚠ COORD: banner on its result.

Next

  • MCP tools lists every tool these clients can call.
  • Claude Code is the most complete integration, if you have a choice.