bugfender-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUGFENDER_API_URL | No | Optional override, defaults to https://dashboard.bugfender.com/api | |
| BUGFENDER_API_TOKEN | Yes | Required access token for Bugfender API | |
| BUGFENDER_REFRESH_TOKEN | No | Recommended for automatic token refresh |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| who_am_iD | – |
| list_teamsD | – |
| list_appsD | – |
| get_appD | – |
| list_app_versionsD | – |
| get_sdk_snippetD | – |
| get_app_summaryD | – |
| get_crashesA | Returns a list of crash groups for an app, optionally filtered by date range. Does not support filtering by status — use list_issues with type=crash and issue_status if you need open/resolved/closed crashes only. |
| get_crash_statsD | – |
| get_crash_device_statsD | – |
| get_crash_detailsD | – |
| search_logsD | – |
| count_logsD | – |
| count_devices_with_logsD | – |
| get_network_aggregatesD | – |
| get_network_detailsD | – |
| search_devicesD | – |
| count_devicesD | – |
| list_issuesA | Lists issue groups for an app. Supports filtering by type (issue, crash, feedback) and status (open, resolved, closed). Use this instead of get_crashes or get_feedback when you need status filtering or combined results. |
| get_issueD | – |
| update_issue_statusA | Updates the status of an issue group (issues aggregation). Use this to mark issues as resolved, closed, in progress, etc. |
| get_feedbackD | – |
| get_issue_statsD | – |
| get_issue_device_statsD | – |
| get_issue_devicesD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Many tools have similar names (e.g., get_crashes, get_crash_details, get_crash_stats) and most lack descriptions, making it hard to distinguish their exact purposes. An agent would likely misselect between crash-related tools.
The naming generally follows a verb_noun snake_case pattern (e.g., list_apps, get_crashes, search_logs). However, 'who_am_i' is an outlier that breaks the pattern, and the mix of 'list', 'get', 'search', 'count' is acceptable but slightly inconsistent.
With 25 tools, the server is on the heavy side for a monitoring/tracking API. While each tool may serve a specific need, the count is borderline and could be reduced by combining related tools (e.g., crash stats into one tool with parameters).
The tool surface covers reading and listing for most resources (crashes, issues, feedback, logs, devices, network). However, it lacks create, update (except for issue status), and delete operations, which limits the agent's ability to manage resources fully.