FogBugz
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOGBUGZ_URL | Yes | Base URL of your FogBugz instance (e.g. https://company.fogbugz.com) | |
| FOGBUGZ_API_KEY | Yes | FogBugz API token |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_caseA | Creates a new FogBugz case. Example: create a bug titled "Login fails on Safari" in project "Website", area "Auth", assigned to "john@example.com", priority 2. |
| update_caseA | Updates an existing FogBugz case with new field values. Example: change the title of case 42 to "Improved error message", move it to milestone "v2.1", or add a comment explaining what changed. |
| assign_caseA | Assigns a FogBugz case to a specific user. Example: assign case 42 to "jane@example.com" or to "Jane Smith". |
| resolve_caseA | Resolves (marks as fixed/completed) a FogBugz case. Example: resolve case 42 with comment "Fixed in commit abc123". |
| reopen_caseA | Reopens a previously closed or resolved FogBugz case. Example: reopen case 42 with comment "Issue reproduced on v2.1". |
| close_caseA | Closes a FogBugz case (marks it as will not fix / done). Example: close case 42 with comment "Closed — duplicate of case 10". |
| list_my_casesA | Lists FogBugz cases assigned to a specific user. Example: list all active cases assigned to "john@example.com", or list up to 20 cases for the current user. |
| search_casesA | Searches for FogBugz cases using FogBugz search syntax. Examples: "project:Website status:Active" to find open Website cases; "assignedTo:jane priority:1" for Jane's urgent cases; "tag:regression milestone:v2.0" for regression bugs in a milestone. |
| get_case_linkA | Returns a direct URL to a FogBugz case that can be shared with teammates. Example: get the link for case 42. |
| get_caseA | Gets detailed information about a specific FogBugz case, including its full event/comment history. Example: fetch all details and comments for case 42. |
| list_peopleA | Lists all people (users) in FogBugz with their IDs, names, and email addresses. Useful for finding the correct assignee name or ID before creating or updating a case. |
| list_categoriesA | Lists all case categories defined in FogBugz (e.g., Bug, Feature Request, Inquiry). Returns category IDs and names. |
| list_projectsA | Lists all active (non-deleted) projects in FogBugz with their IDs and names. Example: retrieve all projects to find the correct project ID before creating a case. |
| list_milestonesA | Lists milestones (fix-for versions) in FogBugz. Optionally filter by project ID. Example: list all milestones for project 5 to find the right target release. |
| list_statusesA | Lists all case statuses defined in FogBugz. Optionally filter by category ID. Returns status names and whether each status counts as resolved. Example: list statuses for category 1 (Bug) to see available workflow states. |
| view_projectA | Gets detailed information about a specific FogBugz project by its numeric ID. Example: view details for project with ID 3. |
| view_areaA | Gets detailed information about a specific FogBugz area by its numeric ID. Example: view details for area with ID 7. |
| create_projectA | Creates a new project in FogBugz. Example: create project "Mobile App" with primary contact "alice@example.com". |
| api_requestA | Generic XML API escape-hatch for FogBugz commands not covered by dedicated tools. 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"}. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/todevelopers/fogbugz-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server