Colabrix MCP Server

Give your AI assistant real, live access to your Colabrix workspace — projects, issues, comments, everything — through the Model Context Protocol. Works with Claude Desktop, Claude Code, Cursor, and any other MCP-compatible client.

No separate permission system to configure: the assistant can only see and do what you can already see and do in Colabrix. If you're a Viewer on a project, so is it. If you're an Admin, so is it.

You: "What's overdue on the Website project?"
Assistant: *checks Colabrix, lists the 3 overdue issues, who they're assigned to*

You: "Create a bug for the broken login button on mobile, assign it to Priya"
Assistant: *creates WEB-142, assigns it, confirms*

Using claude.ai or ChatGPT? Nothing to install

If your client supports remote MCP connectors (claude.ai's Custom Connectors, ChatGPT's Connectors), skip everything below — add a connector pointing at:

https://api.colabrix.in/v1/mcp

Your client discovers the rest itself and walks you through signing in and approving access on Colabrix. This section (and the token below) is only for clients that run MCP servers locally, like Claude Desktop, Claude Code, and Cursor.

Install

Nothing to install ahead of time — npx fetches it on first run. You only need two things:

1. A personal access token. In Colabrix: your avatar → My profile → Integrations → Generate new token. Name it something you'll recognize (e.g. "Claude Desktop"), confirm the consent screen, and copy the token — it's shown exactly once.
2. An MCP client config entry. Add this to your client's config file:

{
  "mcpServers": {
    "colabrix": {
      "command": "npx",
      "args": ["-y", "colabrix-mcp"],
      "env": {
        "COLABRIX_TOKEN": "clbx_your_token_here"
      }
    }
  }
}

Restart your MCP client and you're done.

| Client | Config file | |---|---| | Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows) | | Claude Code | Project .mcp.json, or run claude mcp add colabrix npx -y colabrix-mcp | | Cursor | ~/.cursor/mcp.json or your project's .cursor/mcp.json |

Add COLABRIX_API_URL alongside COLABRIX_TOKEN — it defaults to https://api.colabrix.in.

"env": { "COLABRIX_TOKEN": "clbx_...", "COLABRIX_API_URL": "http://localhost:5000" }

What it can do

| Tool | What it does | |---|---| | list_organizations | Every org you belong to, with your role in each | | list_projects | Projects in an org you have access to | | list_project_members | A project's members, by username — handy before assigning someone | | list_issue_statuses | A project's configured statuses, in order | | list_issues | Issues in a project, filterable by status name, assignee username, priority, type, due date, or a title search | | search_issues | Find an issue's key by title, across every project you're in within an org | | get_issue | Full detail on one issue — description, labels, sub-issues, comment count | | create_issue | Create a new issue — optionally as a sub-issue, with labels and a milestone | | update_issue | Change status (by name), priority, assignee, due date, description, parent issue, milestone, or any other field | | add_comment | Post a comment on an issue, @mentions included | | list_labels | A project's labels, by name and color | | create_label | Create a new label (Admin-only) | | add_label / remove_label | Attach or remove an existing label on an issue | | list_milestones | A project's milestones, with target date, status, and progress | | create_milestone | Create a new milestone (Admin-only) |

Every tool speaks in the same names you'd use talking to a teammate — a project's key (WEB), an issue's key (WEB-42), a person's username, a status's name ("In Progress"). None of Colabrix's internal database ids are ever exposed to the assistant; it never needs to see or remember one.

How it works

This is a thin client, not a second backend. Every tool call is a direct call to the real Colabrix API, with your token as the Authorization header — the exact same API the web app itself uses. All the real logic — permission checks, who can edit what, validation — lives there, so this server can't do anything on your behalf that you couldn't already do yourself in the browser. A request your role doesn't allow, or a status/username/key that doesn't exist, comes back as a plain, specific error ("No status named X. Valid: Todo, In Progress, Done"), not a stack trace.

Security

Treat your token like a password — anyone with it can act as you, in every org and project you belong to, for as long as it's valid.

• Tokens are shown once, at creation, and never again — Colabrix only stores a hash.
• Revoke a token any time from My profile → Integrations; it stops working on the next request.
• Give each client its own token (one for Claude Desktop, a different one for Claude Code, etc.) so you can revoke one without logging everything else out.

License

MIT