Codeable Ticketing MCP

Connect Claude to your Codeable Ticketing Service — manage projects, create tickets, assign work, and track progress through natural conversation.

Built on the Model Context Protocol (MCP), this server gives Claude direct access to your ticketing system's API. Perfect for QAs writing spec sheets, PMs planning sprints, or developers automating ticket creation.

What Can It Do?

Ask Claude things like:

• "Create tickets for the new auth feature based on this spec"
• "Show me all open issues in the MYAPP project"
• "Assign all frontend tickets to Sarah and backend tickets to James"
• "Move MYAPP-15 to In Progress"
• "Add a comment on the login bug about the fix approach"

Available Tools

Projects

| Tool | Description | |------|-------------| | list_projects | List all projects for a user | | get_project | Get project details — members, roles, issue count | | create_project | Create a new project with team and role assignments | | update_project | Update project details, members, or links |

Issues / Tickets

| Tool | Description | |------|-------------| | list_issues | List issues for a project (paginated) | | get_issue | Get full issue details with comments and attachments | | create_issue | Create a single ticket with type, priority, and assignee | | bulk_create_issues | Create multiple tickets at once — with per-ticket error handling | | update_issue | Update any issue field | | move_issue | Move an issue to a different workflow status |

Users & Teams

| Tool | Description | |------|-------------| | search_users | Search users by name or email | | get_user | Get user profile by UID | | list_teams | List all teams for a user | | get_team | Get team details with all members |

Workflow & Comments

| Tool | Description | |------|-------------| | get_workflow_statuses | Get statuses for a project (To Do, In Progress, Done, etc.) | | create_workflow_status | Create a new workflow status | | update_workflow_status | Update status name, color, or description | | add_comment | Add a comment or reply to an issue |

Quick Start

Option 1: Claude Code (CLI)

claude mcp add codeable-ticketing \
  -e CODEABLE_API_BASE_URL=https://your-api.com/api/v1 \
  -e CODEABLE_FIREBASE_API_KEY=your-firebase-web-api-key \
  -e CODEABLE_SERVICE_ACCOUNT_PATH=/path/to/service-account.json \
  -e CODEABLE_USER_UID=your-firebase-uid \
  -- npx codeable-ticketing-mcp

Option 2: Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "codeable-ticketing": {
      "command": "npx",
      "args": ["codeable-ticketing-mcp"],
      "env": {
        "CODEABLE_API_BASE_URL": "https://your-api.com/api/v1",
        "CODEABLE_FIREBASE_API_KEY": "your-firebase-web-api-key",
        "CODEABLE_SERVICE_ACCOUNT_PATH": "/path/to/service-account.json",
        "CODEABLE_USER_UID": "your-firebase-uid"
      }
    }
  }
}

Option 3: Build From Source

git clone https://github.com/gocodeable/codeable-ticketing-mcp.git
cd codeable-ticketing-mcp
npm install && npm run build

Then register locally:

{
  "mcpServers": {
    "codeable-ticketing": {
      "command": "node",
      "args": ["/path/to/codeable-ticketing-mcp/dist/index.js"],
      "env": {
        "CODEABLE_API_BASE_URL": "https://your-api.com/api/v1",
        "CODEABLE_FIREBASE_API_KEY": "your-firebase-web-api-key",
        "CODEABLE_SERVICE_ACCOUNT_PATH": "/path/to/service-account.json",
        "CODEABLE_USER_UID": "your-firebase-uid"
      }
    }
  }
}

Configuration

| Variable | Required | Description | |----------|----------|-------------| | CODEABLE_API_BASE_URL | Yes | Your ticketing API base URL (e.g. https://api.example.com/api/v1) | | CODEABLE_FIREBASE_API_KEY | Yes | Firebase Web API key (from Firebase Console > Project Settings) | | CODEABLE_SERVICE_ACCOUNT_PATH | Yes | Absolute path to your Firebase service account JSON key file | | CODEABLE_USER_UID | Yes | Firebase UID of the user to authenticate as |

Architecture

Claude ←→ MCP Protocol (stdio) ←→ codeable-ticketing-mcp ←→ Codeable Ticketing API

The server is stateless — each tool call translates to one or more REST API calls to your ticketing backend. Authentication uses a Firebase Admin service account to generate ID tokens automatically, with built-in token refresh (no manual token management needed).

Project Structure

src/
├── index.ts              # Entry point — MCP server setup
├── auth.ts               # Firebase Admin auth + token refresh
├── client.ts             # HTTP client with auto-token management
├── types.ts              # TypeScript types for all models
└── tools/
    ├── registry.ts       # Tool registration hub
    ├── projects.ts       # Project CRUD tools
    ├── issues.ts         # Issue/ticket tools + bulk create
    ├── users.ts          # User search and lookup
    ├── workflows.ts      # Workflow status management
    ├── comments.ts       # Issue comments
    └── teams.ts          # Team management

Companion: Claude Skill

Pair this MCP server with the Codeable Ticketing Skill to automatically decompose specs into tickets.

Publishing

Public (npm)

npm login
npm publish

Anyone can then use it with npx codeable-ticketing-mcp.

Private (GitHub Packages)

Update package.json:

{
  "name": "@gocodeable/codeable-ticketing-mcp",
  "publishConfig": {
    "registry": "https://npm.pkg.github.com"
  }
}

npm login --registry=https://npm.pkg.github.com
npm publish

Collaborators will need a .npmrc with your org's GitHub token.

License

MIT