MCP Hub
Back to servers

FogBugz

A MCP server for interacting with FogBugz issue tracker through LLMs such as Claude. Supports both the XML API (/api.asp) and the JSON API (/f/api/0/jsonapi) with automatic version detection at startup. Works with on-premise and on-demand FogBugz installations.

glama
Stars
1
Updated
Apr 17, 2026
Validated
Apr 24, 2026

FogBugz MCP Server icon FogBugz MCP Server

Test count Version License Node MCP

A Model Context Protocol (MCP) server for interacting with FogBugz through LLMs such as Claude. Supports both the XML API (/api.asp) and the JSON API (/f/api/0/jsonapi) with automatic version detection at startup. Works with on-premise and on-demand FogBugz installations.

Overview

Allows LLMs to perform FogBugz operations:

  • Creating, updating, resolving, reopening, and closing cases
  • Assigning cases to specific users
  • Searching and listing cases with full event/comment history
  • Listing users, categories, projects, and areas
  • Creating new projects
  • Generic API requests for advanced use cases

API Auto-Detection

At startup the server automatically selects the right API client for your FogBugz instance:

  1. Probes /api.xml to read the FogBugz version number.
  2. If version ≥ 9, attempts to reach the JSON API (/f/api/0/jsonapi) — uses FogBugzJsonClient on success.
  3. Falls back to FogBugzXmlClient (XML API via /api.asp) for version < 9 or if the JSON endpoint is unreachable.

No configuration is needed — the correct client is selected automatically.

FogBugz versionAPI used
≥ 9 (JSON API available)JSON API (/f/api/0/jsonapi)
< 9 or JSON API unreachableXML API (/api.asp)

Note on text formatting: Plain text only is supported in descriptions and comments when connected to FogBugz 8.x via the XML API. HTML and Markdown are stored and displayed literally.

Getting a FogBugz API Token

You need an API token to authenticate the MCP server with FogBugz. There are two ways to obtain one:

1. Via the web UI

Go to Account & Settings → User Options and click the Create API Token link.

See the official guide: Create API Token using the FogBugz UI

2. Via API request

Send the following request (replace placeholders with your values):

https://[your-fogbugz-server]/api.asp?cmd=logon&email=[your-email]&password=[your-password]

The response will contain your API token.

See the official guide: Get an API Token using FogBugz API commands

Installation

One-click install (Claude Desktop)

Download the latest .mcpb package from the Releases page and open it — Claude Desktop will install and configure the server automatically, prompting you for your FogBugz URL and API key.

Manual install

git clone https://github.com/todevelopers/fogbugz-mcp.git
cd fogbugz-mcp
npm install
npm run build

MCP Client Configuration

Add to your MCP client config (e.g. Claude Desktop claude_desktop_config.json):

{
  "mcpServers": {
    "fogbugz": {
      "command": "node",
      "args": ["/absolute/path/to/fogbugz-mcp/dist/index.js"],
      "env": {
        "FOGBUGZ_URL": "https://your-fogbugz-server.com",
        "FOGBUGZ_API_KEY": "your-api-token"
      }
    }
  }
}

Alternatively, pass credentials as command-line arguments:

{
  "mcpServers": {
    "fogbugz": {
      "command": "node",
      "args": [
        "/absolute/path/to/fogbugz-mcp/dist/index.js",
        "https://your-fogbugz-server.com",
        "your-api-token"
      ]
    }
  }
}

Running Manually

# With command-line arguments
node dist/index.js https://your-fogbugz-server.com your-api-token

# With environment variables
FOGBUGZ_URL=https://your-fogbugz-server.com FOGBUGZ_API_KEY=your-api-token npm start

# With a .env file
cp .env.example .env   # fill in FOGBUGZ_URL and FOGBUGZ_API_KEY
npm start

Development

npm run dev    # run via ts-node (no build needed)
npm run build  # compile TypeScript to dist/
npm test       # run all Jest tests

MCP Tools

Case Management

ToolDescription
create_caseCreate a new case
update_caseUpdate an existing case (title, comment, project, area, milestone, priority)
assign_caseAssign a case to a user
resolve_caseResolve (mark as fixed/completed) a case
reopen_caseReopen a resolved or closed case
close_caseClose a case

Search & View

ToolDescription
search_casesSearch using FogBugz query syntax (e.g. project:Website status:Active)
list_my_casesList cases assigned to a user (defaults to current user)
get_caseGet detailed case info including full event/comment history
get_case_linkGet a direct URL to a case

Reference Data

ToolDescription
list_peopleList all users with IDs, names, and emails
list_categoriesList case categories (Bug, Feature Request, etc.)
list_projectsList all active projects with IDs and names
list_milestonesList milestones/fix-fors, optionally by project
list_statusesList case statuses with resolved flags, optionally by category
view_projectGet detailed project information
view_areaGet detailed area information
create_projectCreate a new project

Advanced

ToolDescription
api_requestGeneric XML API escape-hatch for commands not covered by dedicated tools.
⚠️ WARNING: can execute any API command the configured key permits, including destructive operations (delete, edit users, bulk modify).

Environment Variables

VariableRequiredDescription
FOGBUGZ_URLYesBase URL of your FogBugz instance (e.g. https://company.fogbugz.com)
FOGBUGZ_API_KEYYesFogBugz API token

Compatibility

Tested with FogBugz 8.8.53 (XML API). JSON API support is implemented by specification. The server auto-detects which API to use at startup.

Acknowledgements

This project is based on the original work by Sarasvati Akari Lara-Almeida — thank you for the foundation.

License

MIT © Tomáš Gažovič, ToDevelopers s.r.o.

Reviews

No reviews yet

Sign in to write a review