LABSCO SUMMARY

`api_request` runs whatever the configured key is permitted to run, and the tool's own description says so.

Its warning names the shape of the risk — delete, edit users, bulk modify — and points at the FogBugz API reference for the command set, so the credential's own permissions are the boundary rather than the tool list. Everything else here is deliberately narrower: the write tools take named fields, and the lookup tools exist so that an assignee, project, milestone, category or status is resolved to a real value before a case is created or moved. list_statuses is the one worth calling early, since it reports which statuses count as resolved in the workflow you are writing into.

What it is

A FogBugz client exposing 19 tools over the case lifecycle, FogBugz search syntax, and the people, project, area, milestone, category and status lookups a valid case needs, plus a generic XML API escape hatch.

What you get

The case lifecycle as distinct calls: create_case files one with project, area, assignee, milestone and priority; update_case changes those fields; assign_case moves it to a person; and resolve_case, close_case and reopen_case each take a comment that lands on the case.
Search in the syntax the tracker already speaks: search_cases accepts FogBugz queries such as project:Website status:Active or tag:regression milestone:v2.0, while list_my_cases narrows to one assignee's cases by status.
The whole thread rather than a summary: get_case returns a case with its full event and comment history, and cols selects which fields come back.
The lookups that make a write valid: list_people returns assignee names, IDs and email addresses, list_projects returns active projects, list_milestones filters by ixProject, list_categories returns category IDs and names, and list_statuses filters by ixCategory and reports whether each status counts as resolved.
Detail behind an ID: view_project and view_area expand a numeric project or area ID, and create_project opens a new project with a primary contact.
Something to paste into a thread: get_case_link returns a direct URL to a case that can be shared with teammates.
An escape hatch: api_request sends any FogBugz XML API command with its own params when no dedicated tool fits.

Requirements

A FogBugz instance you can reach, given as FOGBUGZ_URL, and an API key for it as FOGBUGZ_API_KEY.

Setup effort

One command plus a key — npx @todevs/fogbugz-mcp, then supply credentials

See installation options

USE CASES

01

Filing a bug without leaving the branch you are on

Resolve the project and the person it should land on, then create the case with its area, milestone and priority already correct.

list_projectslist_peoplecreate_case

02

Clearing the queue that is assigned to you

Pull your active cases, open the ones with history worth reading, and resolve them with the commit or the reasoning attached.

list_my_casesget_caseresolve_case

03

Rounding up regressions ahead of a release

Query by tag and milestone in FogBugz syntax, confirm which milestone you actually mean, and read each case before deciding what blocks the release.

search_caseslist_milestonesget_case

04

Handing a case to whoever owns that area

Find the right person, move the case to them, and send them a link that opens it directly.

list_peopleassign_caseget_case_link

05

Reopening something that shipped broken

Find the closed case, reopen it with the reproduction attached, and move it onto the milestone that will actually carry the fix.

search_casesreopen_caseupdate_case

06

Reaching a command no dedicated tool covers

Send the raw FogBugz XML API command with its own parameters when the operation you need has no wrapper.

api_request

19 tools

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`api_request`

Generic XML API escape-hatch for FogBugz commands not covered by dedicated tools — see the FogBugz API reference at https://api.manuscript.com/. WARNING: Can execute any API command the configured key permits, including destructive operations (delete, edit users, bulk modify). Prefer specific tools when available; use this only when no dedicated tool fits the need. Examples: cmd=listProjects; cmd=listCategories; cmd=search with params {"q": "project:Website", "cols": "sTitle,sStatus", "max": "10"}.

BEFORE YOU INSTALL

What to know first

Tools you get

19 tools when we connected. api_request can run any API command your key permits, including deletes and bulk edits. On FogBugz 8.x, HTML and Markdown are stored and displayed literally.

Requires

npx on PATH
Node.js 20 or later
FOGBUGZ_URL in your environment
FOGBUGZ_API_KEY in your environment

Where it runs

Both documented clients run the server on your machine.

CONTEXT COST

Light Standing cost

Rated by the size of the 19 tool definitions that ride along on every turn, not by how many there are

INSTALLATION

Connect your client

Server setup

TERMINAL

npx @todevs/fogbugz-mcp

MCP Clients

Claude Desktop, Claude Code

JSON

{
  "mcpServers": {
    "fogbugz": {
      "command": "npx",
      "args": [
        "-y",
        "@todevs/fogbugz-mcp"
      ],
      "env": {
        "FOGBUGZ_URL": "<YOUR_FOGBUGZ_URL>",
        "FOGBUGZ_API_KEY": "<YOUR_FOGBUGZ_API_KEY>"
      }
    }
  }
}

FogBugz

`api_request` runs whatever the configured key is permitted to run, and the tool's own description says so.

What it is

What you get

Requirements

Setup effort

Filing a bug without leaving the branch you are on

Clearing the queue that is assigned to you

Rounding up regressions ahead of a release

Handing a case to whoever owns that area

Reopening something that shipped broken

Reaching a command no dedicated tool covers

19 tools

`api_request`

`assign_case`

`close_case`

`create_case`

`create_project`

`get_case`

`get_case_link`

`list_milestones`

`list_my_cases`

`list_people`

`list_projects`

`list_statuses`

`reopen_case`

`resolve_case`

`search_cases`

`update_case`

`view_area`

`view_project`

What to know first

Tools you get

Requires

Where it runs

Light Standing cost

Connect your client

Server setup

MCP Clients

Claude Desktop, Claude Code

FogBugz

`api_request` runs whatever the configured key is permitted to run, and the tool's own description says so.

What it is

What you get

Requirements

Setup effort

Filing a bug without leaving the branch you are on

Clearing the queue that is assigned to you

Rounding up regressions ahead of a release

Handing a case to whoever owns that area

Reopening something that shipped broken

Reaching a command no dedicated tool covers

19 tools

api_request

assign_case

close_case

create_case

create_project

get_case

get_case_link

list_categories

list_milestones

list_my_cases

list_people

list_projects

list_statuses

reopen_case

resolve_case

search_cases

update_case

view_area

view_project

What to know first

Tools you get

Requires

Where it runs

Light Standing cost

Connect your client

Server setup

MCP Clients

Claude Desktop, Claude Code

Same category

Saga

Yandex Tracker

Todoist MCP

ATLAS: Task Management System

`api_request`

`assign_case`

`close_case`

`create_case`

`create_project`

`get_case`

`get_case_link`

`list_categories`

`list_milestones`

`list_my_cases`

`list_people`

`list_projects`

`list_statuses`

`reopen_case`

`resolve_case`

`search_cases`

`update_case`

`view_area`

`view_project`