@mudravaorg/mcp-server

MCP (Model Context Protocol) server for PixelFixer — a visual bug tracking and kanban board tool. Connects AI agents (Claude, Cursor, VS Code Copilot, Windsurf) to your PixelFixer projects.

What it does

This MCP server gives AI agents full access to your PixelFixer workspace:

v1.0 highlights

• Session context — call init_session once; all tools auto-use your team/project IDs

• Task numbers — get_task, start_task, etc. accept taskNumber: 42 instead of raw IDs

• Compact responses — list views return summaries (~90% fewer tokens than v0.2)

• Retry & timeout — automatic retry with backoff on 429/5xx, 30s request timeout

• Better errors — human-readable messages that help AI self-correct

Related MCP server: kanban-mcp

Quick Start

1. Get an API Token

Go to PixelFixer → Team Settings → API Tokens and create a token with read + write scopes.

2. Configure your IDE

VS Code (.vscode/mcp.json):

{
  "servers": {
    "pixelfixer": {
      "command": "npx",
      "args": ["-y", "@mudravaorg/mcp-server"],
      "env": {
        "PIXELFIXER_API_TOKEN": "pf_your_token_here",
        "PIXELFIXER_API_URL": "https://pixelfixer.mudrava.com"
      }
    }
  }
}

Cursor (.cursor/mcp.json) / Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "pixelfixer": {
      "command": "npx",
      "args": ["-y", "@mudravaorg/mcp-server"],
      "env": {
        "PIXELFIXER_API_TOKEN": "pf_your_token_here",
        "PIXELFIXER_API_URL": "https://pixelfixer.mudrava.com"
      }
    }
  }
}

Note: VS Code uses "servers" as the root key, while Cursor and Claude Desktop use "mcpServers".

3. Start using it

Ask your AI agent:

• "Check my PixelFixer tasks and fix what's in the AI queue"

• "Start task #42 and fix it"

• "Search for high-priority open bugs"

• "Create a PR that fixes the button color issue from task #15"

Environment Variables

Local Development

If you're running PixelFixer from source, you can use the local build instead of the npm package:

cd packages/mcp-server
pnpm install
pnpm build

Then point your IDE to the local file:

{
  "servers": {
    "pixelfixer": {
      "command": "node",
      "args": ["${workspaceFolder}/packages/mcp-server/dist/index.js"],
      "env": {
        "PIXELFIXER_API_TOKEN": "pf_your_token_here",
        "PIXELFIXER_API_URL": "http://localhost:3000"
      }
    }
  }
}

Tool Reference

init_session

The recommended first call in every session. Auto-discovers your team and project (if you have exactly one of each), sets the session context, and returns the AI task queue as compact summaries. After this, all tools auto-fill teamId/projectId.

start_task

Start working on an AI task. Moves the task to In Progress, sets AI status to PROCESSING, and returns full context: task details, comments, GitHub info, columns, and a workflow guide. Accepts taskId or taskNumber.

search_tasks

Search with multiple filters:

• q — text search (title, description, task number)

• status — OPEN, IN_PROGRESS, RESOLVED, CLOSED

• priority — LOW, MEDIUM, HIGH, CRITICAL

• aiStatus — NONE, QUEUED, PROCESSING, COMPLETED, FAILED

• assigneeId, columnId, tag

create_pull_request

Creates a branch and PR in the connected GitHub repo. Example:

branchName: "fix/PF-42-button-color"
title: "Fix button color on dashboard"
body: "Resolves PF-42. Changed primary button color..."

Security

• API tokens are hashed (SHA-256) in the database — even a DB leak won't expose tokens

• Tokens have scoped permissions (read / write / admin)

• The MCP server runs locally on your machine — data goes directly to your PixelFixer instance over HTTPS

• No data is sent to third parties

License

MIT