Overview

Connect the CollabOps MCP server and AI clients like Claude or Cursor can read and act on your CollabOps issues, change requests (CRs), repositories, docs, and sprints directly. Ask things like "tidy up my issues" or "call out the review points in this CR" without leaving your IDE or chat window.

Before you start

You only need two things:

A CollabOps account you can sign in with — you authenticate with it when connecting.

Node.js (LTS) — only needed for clients that connect through the mcp-remote bridge (Claude Desktop, Windsurf, Zed, etc.). Clients with native remote-MCP support (Claude Code, Cursor, VS Code) don't need it.

Server address

Every client uses the single address below. Registering this value is all it takes.

https://mcp.collabops.ai/mcp

Setup per client

Claude Code

Add the server from your terminal.

claude mcp add --transport http collabops https://mcp.collabops.ai/mcp

Run /mcp inside Claude Code to list your registered MCP servers. The collabops server you just added shows a needs authentication status because it isn't connected yet.

Collabops MCP Server

Status:            △ needs authentication
Auth:              ✗ not authenticated
URL:               https://mcp.collabops.ai/mcp
Config location:   ~/.claude.json

❯ 1. Authenticate
  2. Disable

Select collabops, then choose 1. Authenticate. Your default browser opens the CollabOps sign-in and consent screen.

After you sign in and approve, close the browser window to return to Claude Code. Reopen /mcp — once the status reads connected, you're done.

Claude Desktop

Add the following to claude_desktop_config.json (Settings → Developer → Edit Config), then restart the app. A sign-in window opens on first use.

{
  "mcpServers": {
    "collabops": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.collabops.ai/mcp"]
    }
  }
}

Cursor

Open Settings → MCP → Add new global MCP server and add the following to ~/.cursor/mcp.json. Saving it triggers the sign-in window, and the tool list appears in the MCP settings once connected.

{
  "mcpServers": {
    "collabops": {
      "url": "https://mcp.collabops.ai/mcp"
    }
  }
}

VS Code

Create .vscode/mcp.json in your workspace with the following. In Copilot Chat's Agent mode, click Start on the server to authenticate.

{
  "servers": {
    "collabops": {
      "type": "http",
      "url": "https://mcp.collabops.ai/mcp"
    }
  }
}

Windsurf · Zed · Others (mcp-remote)

Clients without native remote-MCP support connect through the mcp-remote bridge. Windsurf uses ~/.codeium/windsurf/mcp_config.json with the mcpServers form below.

{
  "mcpServers": {
    "collabops": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.collabops.ai/mcp"]
    }
  }
}

Zed uses a different key — place it under context_servers in settings.json.

{
  "context_servers": {
    "collabops": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.collabops.ai/mcp"],
      "env": {}
    }
  }
}

Codex CLI

Add the remote server from your terminal (remote MCP may be an experimental feature).

codex mcp add collabops --url https://mcp.collabops.ai/mcp

How authentication works

The first time a client connects, a browser opens and runs the standard OAuth flow:

CollabOps sign-in — skipped automatically if you're already signed in.

Consent screen — review which client is requesting which permissions, then approve.

After you approve, you return to the client and the connection is complete. No re-login is needed afterward.

What you can do

Once connected, the AI client uses tools across these areas:

Try asking

"Show my open issues ordered by priority"

"Summarize the changes in CR #1234 and list the points to raise in review"

"What's left in this sprint, and which issues are at risk of slipping?"

"Draft a bug issue from this error log, including reproduction steps"

Verify the connection

Confirm it worked two ways: (1) the collabops server shows as "connected" in the client's MCP settings with a visible tool list, and (2) asking "show my profile" returns your account info. If both work, you're set.

FAQ

Do I need an API key?

No. You sign in to your CollabOps account via browser OAuth — there's no key to generate or manage.

How much of my data can the AI access?

Only within the permissions of your signed-in account. Workspaces, issues, and repositories your account can't see are invisible to the AI too.

Can I use multiple workspaces?

Yes. You can work across the workspaces your account belongs to, and tools support specifying a workspace. Name the workspace in your request to target a specific one.

How do I disconnect?

Remove the collabops server in your client settings, and to clear stored auth run rm -rf ~/.mcp-auth.

Troubleshooting