Fogbugz MCP Server

If you already use Fogbugz MCP, the fogbugz mcp mcp server is the piece that lets your assistant work with it directly. FogBugz MCP Server for interacting with FogBugz via LLMs.

What the server does

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

• Search and list cases — using FogBugz query syntax (e.g. project:Website status:Active)
• Read case details — including full event and comment history
• Create and update cases — — set title, project, area, milestone, priority, and comments
• Full lifecycle management — — assign, resolve, reopen, and close cases
• User, project, and area discovery — — list people, categories, projects, milestones, and statuses
• Create new projects — directly from the conversation

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Advanced — The Advanced tool exposed by this server

Installation

@todevs/fogbugz-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: FOGBUGZ_URL, FOGBUGZ_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• FogBugz (on-premise or on-demand) - Node.js 20 or later - A FogBugz API token

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Fogbugz MCP's toolset — Advanced — is a fair guide to whether it matches your workflow. It is maintained by todevelopers; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.