FogBugz

Provides an MCP server to interact with FogBugz via the official XML API, exposing tools to search, audit, and update cases from Codex.
  • javascript

0

GitHub Stars

javascript

Language

4 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "dpupek-fogbugz-mcp": {
      "command": "npx",
      "args": [
        "--yes",
        "-p",
        "github:dpupek/fogbugz-mcp",
        "fogbugz-mcp"
      ],
      "env": {
        "FOGBUGZ_BASE": "https://example.fogbugz.com/api.asp",
        "FOGBUGZ_TOKEN": "paste-your-token-here",
        "FOGBUGZ_MCP_DEBUG": "1",
        "FOGBUGZ_MCP_LOG_FILE": "/tmp/fogbugz-mcp.log"
      }
    }
  }
}

You can run a FogBugz MCP Server to securely and efficiently access FogBugz data from Codex. It exposes curated tools for searching, auditing, and updating cases, while FogBugz handles the actual workflow and state management, keeping your Codex interactions fast and stable.

How to use

You will install and run the FogBugz MCP Server as a local process that Codex connects to via the MCP stdio transport. Use the server to perform common FogBugz operations such as creating cases, adding comments, attaching files, reviewing case histories, and exploring the case hierarchy. Start by configuring your environment with FogBugz credentials, then launch the MCP server from Codex and invoke tools to interact with FogBugz without leaving your workspace.

How to install

Prerequisites and initial setup follow these steps to get you running smoothly.

  1. Ensure you have Node.js 20.x or newer installed, which includes npm. You should also have git available on your system.

  2. Generate a FogBugz API token for your account, then store it securely in your environment. You will reference this token in your MCP configuration.

  3. Create or edit Codex configuration to wire in the FogBugz MCP server. Use a stdio-based MCP server configuration that runs via npx and loads the FogBugz MCP package.

  4. Confirm the FogBugz base URL and API token are available to the MCP server through environment variables. You can also enable verbose logging for debugging during setup.

Additional setup details

Configuration is done through a dedicated MCP server entry in Codex configuration. The standard approach is to run the server via npx with the FogBugz MCP package, passing your FogBugz base URL, API token, and optional logging settings.

Example MCP server configuration you would place in Codex config.toml:

[mcp_servers.fogbugz]
type = "stdio"
command = "npx"
args = ["--yes", "-p", "github:dpupek/fogbugz-mcp", "fogbugz-mcp"]
startup_timeout_sec = 15
shutdown_timeout_sec = 5
tool_timeout_sec = 60
description = "FogBugz MCP server (search/view/create/edit/comment/attach/children/events)"

env = {  "FOGBUGZ_BASE" = "https://example.fogbugz.com/api.asp",   "FOGBUGZ_TOKEN" = "paste-your-token-here",   "FOGBUGZ_MCP_LOG_FILE" = "/tmp/fogbugz-mcp.log",  "FOGBUGZ_MCP_DEBUG" = "1"}

Notes on usage with FogBugz tools

The server exposes a collection of tools that map to FogBugz XML commands. You can search cases, view case details, create or edit cases, add comments, manage attachments, and inspect case hierarchies. You can also fetch metadata such as available categories, areas, statuses, and milestones to help validate inputs before making changes.

Available tools

help

Returns the markdown help/recipes that ship with the server. No arguments.

version

Return the MCP server name plus version.

health

Check configuration and FogBugz API connectivity.

search_cases

Run arbitrary FogBugz searches. Requires q and optional cols.

case_events

Same as search_cases but returns the events column for full history.

view_case

Fetch one case by ixBug with optional columns; includes ixBug by default.

create_case

Create a new FogBugz case with optional parent, milestone, and user story fields.

edit_case

Update an existing FogBugz case. Modify title, userStory, or any XML field via fields.

add_comment

Add a comment or event to a case with optional textType.

add_comment_with_attachment

Add a comment and upload a single attachment in one call.

attach_file

Upload an attachment using base64 content.

list_children

Return the parent case plus its children with key fields.

case_outline

Build the entire descendant tree using FogBugz outline search.

resolve_case

Resolve a case with optional closing comment or field edits.

reactivate_case

Re-open a case with optional comment/field payload.

list_categories

Enumerate every FogBugz category and metadata.

list_areas

List undeleted areas, optionally filtered by project.

list_status

List FogBugz statuses, optionally filtered by category or resolved state.

view_status

View a specific FogBugz status by ixStatus or sStatus and ixCategory.

list_milestones

List milestones (FixFors), optionally filtered by project.

view_milestone

View a specific milestone by ixFixFor.

create_milestone

Create a new milestone in a project.

edit_milestone

Edit an existing milestone with optional fields.

add_milestone_dependency

Add a dependency between milestones.

remove_milestone_dependency

Remove a milestone dependency.

create_area

Create a new area in a project.

edit_area

Edit an existing area.

list_custom_fields

Return custom-field names configured for a specific case.

list_columns

Return case column metadata for safe column assembly.

case_link

Build the FogBugz web URL for a human-clickable link.

search_users

Search people via cached results with optional query and refresh.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational