Connecting Claude Desktop
Add OpsDash to the Claude Desktop app with your connection token, so Claude can read and update your projects, tasks, time and invoices.
Claude Desktop can use OpsDash through its MCP server. OpsDash's server signs in with a token in a header, so Claude Desktop connects to it through a small helper, mcp-remote, that runs on your computer.
What you need first
- The Claude Desktop app (Windows or Mac).
- Node.js installed (so the
npxcommand works). Check by runningnode --versionin a terminal. - A staff connection token (choose the Cursor kind) and the MCP address from Settings › Agents.
Add OpsDash
- In Claude Desktop, open Settings › Developer and choose Edit Config. This opens
claude_desktop_config.json. - Add OpsDash under
mcpServers(keep anything already there):
{
"mcpServers": {
"opsdash": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://www.opsdash.io/api/mcp",
"--header",
"Authorization:${OPSDASH_AUTH}"
],
"env": {
"OPSDASH_AUTH": "Bearer paste-your-token-here"
}
}
}
}
- Replace the address if your OpsDash isn't opsdash.io, and put your token after
Bearer(keep the space). - Save the file and quit and reopen Claude Desktop.
Write Authorization:${OPSDASH_AUTH} with no space after the colon, exactly as shown: some systems split the argument at spaces.
Check it works
Start a new chat and ask "Who am I in OpsDash?". Claude uses the whoami tool and tells you your workspace and connection name. The tools menu in the chat box lists OpsDash's tools.
Claude asks before using a tool unless you allow it; you can allow read tools and keep asking for ones that change things.
Keep the token safe
The token is in the config file on your computer. Don't share the file or paste it into chats, and remove the connection in OpsDash if the computer is lost. See keeping tokens safe.
Troubleshooting
- OpsDash doesn't appear in Claude: check the JSON is valid (no trailing commas), then fully quit Claude Desktop (not just close the window) and reopen it. Settings › Developer shows each server's status and log.
- "npx" not found: install Node.js, then restart Claude Desktop.
- 401 Unauthorized: the token is wrong, the connection is switched off or removed, or there's no space after
Bearer. - 403 with "no longer an owner or admin": the person who made the connection left or changed role. An admin needs to make a new connection.
- 429 Too many requests: wait a minute; each connection can make 180 requests a minute.
Settings in OpsDash
These open in OpsDash. You’ll be asked to sign in first if you aren’t already.
Related articles
- Creating a staff connectionMake a connection and token in Settings › Agents for an AI assistant to use OpsDash's MCP server, and manage the connections you have.
- Connecting Claude CodeAdd OpsDash to Claude Code with a .mcp.json file that reads your token from an environment variable, so the token never goes in your code.
- What agents can and can't doThe OpsDash tools an AI assistant can use, grouped by area, and the things it will never do.