MCP Tools and Resources

The Bugfender MCP server exposes the following capabilities. Use the public app ID returned by list_apps whenever a tool requires app_id.

Account and apps

Tool	Purpose
`who_am_i`	Verify the configured credentials and return the current user.
`list_teams`	List teams available to the current user.
`list_apps`	List accessible Bugfender apps.
`get_app`	Get metadata for one app.
`list_app_versions`	List version IDs that can be used in filters.
`get_sdk_snippet`	Generate an app-key-specific setup snippet for iOS, Android, Web, or Flutter.
`get_app_summary`	Get the daily summary for one app.

Tool	Purpose
`search_logs`	Search and page through log messages with device, date, level, tag, and app-version filters.
`count_logs`	Count logs matching the same filters without retrieving every message.
`count_devices_with_logs`	Count distinct devices that produced matching log text.
`get_network_aggregates`	Aggregate captured network traffic by domain and endpoint, with date, device, version, and OS filters.
`get_network_details`	Inspect one domain and endpoint, including paginated sample requests.

Tool	Purpose
`search_devices`	Search devices by activity range, name, model, OS, version, matching logs, or enabled state.
`count_devices`	Count devices matching device and activity filters.

Tool	Purpose
`get_crashes`	List crash groups for an app and date range.
`get_crash_stats`	Aggregate crash occurrences over a date range.
`get_crash_device_stats`	Measure how many devices are affected by crashes.
`get_crash_details`	Get one crash group's full details and affected devices.
`list_issues`	List issue, crash, or feedback groups with status and content filters.
`get_issue`	Get one issue group.
`update_issue_status`	Change an issue group's status. This is the only tool in the current server that changes Bugfender data.
`get_issue_stats`	Aggregate issue occurrences over a date range.
`get_issue_device_stats`	Measure how many devices are affected by matching issues.
`get_issue_devices`	Page through the devices affected by one issue group.
`get_feedback`	List user-feedback groups for an app and date range.

Valid values for update_issue_status are new, open, in_progress, resolved, closed, muted, and invalid.

Resources provide reusable, read-only context:

URI template	Content
`bugfender://snippet/{app_id}/{platform}`	App-key-specific SDK setup snippet.
`bugfender://app/{app_id}/logs?date_range_start={start}&date_range_end={end}`	Logs for an explicit date range.
`bugfender://issue/{issue_id}?app_id={app_id}`	One issue group as Markdown.

Log searches use the cursor returned in pagination.next.
Device searches use pagination.next_cursor.
Issue and affected-device lists use page numbers.
Page size defaults to 100 and is capped at 200; network request samples are capped at 100 per page.
Date filters accept ISO 8601 timestamps. search_logs also accepts YYYY-MM-DD.