Connects AI clients to Bugfender to access logs, crashes, devices, and user feedback for app monitoring and debugging.
Also known as bugfender/bugfender-mcp, bugfender-mcp, @bugfender/mcp
- Stars
- 0
- Tools
- 25
- Downloads, 30 days
- 692
- Latest version
- 0.6.0
- Last commit
- Nov 12, 2026
- License
- Apache-2.0
What is Bugfender MCP?
Bugfender connects AI clients to Bugfender to access logs, crashes, devices, and user feedback for app monitoring and debugging. It exposes 25 tools, such as who_am_i, list_teams, list_apps.
Summary generated from the project's README
About Bugfender MCP server
Bugfender provides a hosted MCP service that connects AI clients to your Bugfender account for app monitoring and debugging. Developers can use this to access logs, crashes, device data, and user feedback through remote Streamable HTTP using OAuth authentication. This setup allows AI agents to interact with your application's health data without requiring you to manually manage API tokens in the connection settings.
For those requiring local setups or self-hosted environments, a deprecated stdio fallback is available via the @bugfender/mcp npm package. This local version requires a BUGFENDER_API_TOKEN and can optionally use a BUGFENDER_REFRESH_TOKEN for automatic credential rotation. The server includes a wide array of tools such as search_logs, get_crashes, and update_issue_status to facilitate deep technical investigations.
Beyond raw data access, the service supports companion skills that provide opinionated workflows for common tasks. These skills help automate SDK onboarding and structured debugging processes, making it easier for AI clients to navigate complex crash reports or summarize feedback trends.
What you can do with it
- 1Crash InvestigationRequest a detailed analysis of the most frequent crashes occurring in a specific application version.
- 2Issue Status ManagementInstruct the AI agent to update the status of a specific reported issue within the Bugfender dashboard.
- 3Trend SummarizationHave the AI summarize how user feedback or issue trends have changed over a specific period.
Written from the project's README. Every use case is checked against a quote from it.
How to install Bugfender MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Bugfender MCP in Claude Code
$ claude mcp add --env 'BUGFENDER_API_TOKEN=<YOUR_BUGFENDER_API_TOKEN>' --env 'BUGFENDER_REFRESH_TOKEN=<YOUR_BUGFENDER_REFRESH_TOKEN>' bugfender-mcp -- npx -y @bugfender/mcpInstall Bugfender MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"bugfender-mcp": {
"command": "npx",
"args": [
"-y",
"@bugfender/mcp"
],
"env": {
"BUGFENDER_API_TOKEN": "<YOUR_BUGFENDER_API_TOKEN>",
"BUGFENDER_REFRESH_TOKEN": "<YOUR_BUGFENDER_REFRESH_TOKEN>"
}
}
}
}Install Bugfender MCP in VS Code
.vscode/mcp.json
{
"servers": {
"bugfender-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@bugfender/mcp"
],
"env": {
"BUGFENDER_API_TOKEN": "<YOUR_BUGFENDER_API_TOKEN>",
"BUGFENDER_REFRESH_TOKEN": "<YOUR_BUGFENDER_REFRESH_TOKEN>"
}
}
}
}Install Bugfender MCP in VS Code CLI
$ code --add-mcp '{"name":"bugfender-mcp","type":"stdio","command":"npx","args":["-y","@bugfender/mcp"],"env":{"BUGFENDER_API_TOKEN":"<YOUR_BUGFENDER_API_TOKEN>","BUGFENDER_REFRESH_TOKEN":"<YOUR_BUGFENDER_REFRESH_TOKEN>"}}'Install Bugfender MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"bugfender-mcp": {
"command": "npx",
"args": [
"-y",
"@bugfender/mcp"
],
"env": {
"BUGFENDER_API_TOKEN": "<YOUR_BUGFENDER_API_TOKEN>",
"BUGFENDER_REFRESH_TOKEN": "<YOUR_BUGFENDER_REFRESH_TOKEN>"
}
}
}
}Install Bugfender MCP in Codex
$ codex mcp add bugfender-mcp --env 'BUGFENDER_API_TOKEN=<YOUR_BUGFENDER_API_TOKEN>' --env 'BUGFENDER_REFRESH_TOKEN=<YOUR_BUGFENDER_REFRESH_TOKEN>' -- npx -y @bugfender/mcpInstall Bugfender MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.bugfender-mcp] command = "npx" args = ["-y", "@bugfender/mcp"] [mcp_servers.bugfender-mcp.env] BUGFENDER_API_TOKEN = "<YOUR_BUGFENDER_API_TOKEN>" BUGFENDER_REFRESH_TOKEN = "<YOUR_BUGFENDER_REFRESH_TOKEN>"
Install Bugfender MCP in Gemini CLI
$ gemini mcp add -s user -e 'BUGFENDER_API_TOKEN=<YOUR_BUGFENDER_API_TOKEN>' -e 'BUGFENDER_REFRESH_TOKEN=<YOUR_BUGFENDER_REFRESH_TOKEN>' bugfender-mcp npx -- -y @bugfender/mcpInstall Bugfender MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"bugfender-mcp": {
"command": "npx",
"args": [
"-y",
"@bugfender/mcp"
],
"env": {
"BUGFENDER_API_TOKEN": "<YOUR_BUGFENDER_API_TOKEN>",
"BUGFENDER_REFRESH_TOKEN": "<YOUR_BUGFENDER_REFRESH_TOKEN>"
}
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @bugfender/mcp 0.6.0 in an isolated container with no network and no keys. It answered and listed 25 tools.
Bugfender MCP tools 25
Read from the server with tools/listwho_am_ilist_teamslist_appsget_applist_app_versionsget_sdk_snippetget_app_summaryget_crashesReturns 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_statsget_crash_device_statsget_crash_detailssearch_logs
| who_am_i | — | |
| list_teams | — | |
| list_apps | — | |
| get_app | — | |
| list_app_versions | — | |
| get_sdk_snippet | — | |
| get_app_summary | — | |
| get_crashes | 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_stats | — | |
| get_crash_device_stats | — | |
| get_crash_details | — | |
| search_logs | — |
Show all 25 toolsShow fewer tools
count_logscount_devices_with_logsget_network_aggregatesget_network_detailssearch_devicescount_deviceslist_issuesLists 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_issueupdate_issue_statusUpdates the status of an issue group (issues aggregation). Use this to mark issues as resolved, closed, in progress, etc.
get_feedbackget_issue_statsget_issue_device_statsget_issue_devices
| count_logs | — | |
| count_devices_with_logs | — | |
| get_network_aggregates | — | |
| get_network_details | — | |
| search_devices | — | |
| count_devices | — | |
| list_issues | 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_issue | — | |
| update_issue_status | Updates the status of an issue group (issues aggregation). Use this to mark issues as resolved, closed, in progress, etc. | |
| get_feedback | — | |
| get_issue_stats | — | |
| get_issue_device_stats | — | |
| get_issue_devices | — |
Configuration
BUGFENDER_API_TOKENRequiredSecretBugfender API access token from MCP setup.
BUGFENDER_REFRESH_TOKENSecretRefresh token for automatic session renewal (recommended).
BUGFENDER_API_URLAPI base URL override; defaults to https://dashboard.bugfender.com/api
| Name | Description | |
|---|---|---|
| BUGFENDER_API_TOKEN | Bugfender API access token from MCP setup. | RequiredSecret |
| BUGFENDER_REFRESH_TOKEN | Refresh token for automatic session renewal (recommended). | Secret |
| BUGFENDER_API_URL | API base URL override; defaults to https://dashboard.bugfender.com/api |
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablebugfender/bugfender-mcp is public and reachablegithub.com/bugfender/bugfender-mcp ↗Pass
- Package names this repository as its source@bugfender/mcp names bugfender/bugfender-mcp as sourcenpmjs.com/package/@bugfender/mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/bugfender/bugfender-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @bugfender/mcpPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model3 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubBugfender MCP
Bugfender's hosted MCP service connects AI clients to Bugfender through remote Streamable HTTP and OAuth:
https://mcp.bugfender.com/mcp
The @bugfender/mcp npm package remains available as a deprecated local stdio
fallback for existing and self-hosted installations.
What It Provides
- user-scoped Bugfender read access through MCP
- automatic access-token refresh when a refresh token is configured
- logs, devices, app metadata, crash aggregation, and issue aggregation tools
- SDK snippet retrieval for app onboarding
- resource templates for snippets, logs, and issue groups
- companion Bugfender skills distributed from
bugfender/bugfender-skills
Maintainers
- development workflow: DEVELOPMENT.md
- release and publish flow: RELEASING.md
Recommended: hosted OAuth
In ChatGPT or Codex, install the public Bugfender plugin and connect the included
Bugfender app. In any compatible remote MCP client, add
https://mcp.bugfender.com/mcp and choose OAuth authentication.
The client discovers the protected resource and Bugfender authorization server, opens the Bugfender sign-in and consent UI, and manages short-lived access and refresh tokens. Hosted users must not manually copy an API token into the connection.
OAuth scopes
mcp:readgrants read-only access to identity, teams, apps, SDK metadata, logs, devices, crashes, issues, feedback, network data, and summaries the signed-in user can already access.mcp:issues:writegrants onlyupdate_issue_status. It does not grant general Bugfender administration or other write operations.
Disconnect and revoke
Use the client's Bugfender Disconnect action to revoke the hosted grant and its access and refresh tokens. If a client lists the plugin and connection separately, disconnect the connection before uninstalling the plugin. A future tool call must start a new OAuth flow.
Privacy
The hosted MCP forwards the request bearer token to the Bugfender API and returns data the signed-in user is authorized to access. It does not persist user credentials or expose them in tool results. The MCP client and AI provider may separately process tool inputs and return Bugfender data under their own privacy and retention terms. See Bugfender's Privacy Policy and Terms of Service.
Deprecated: local stdio package
Existing installations and clients without remote OAuth can continue to run:
npx -y @bugfender/mcp
Do not use this setup for a new public-cloud connection. Prefer the hosted URL or public plugin instead.
After adding or updating the MCP server in your IDE or agent, restart that client so it reloads the new MCP configuration cleanly.
If you are running from inside this repository checkout, do not use npx @bugfender/mcp or npx -p @bugfender/mcp bugfender-mcp. npm can resolve the current package instead of the published tarball and fail with bugfender-mcp: not found.
For local development, build and run the generated entrypoint directly:
pnpm build
pnpm start
Local stdio configuration
BUGFENDER_API_TOKEN: required access tokenBUGFENDER_REFRESH_TOKEN: recommended for automatic token refreshBUGFENDER_API_URL: optional override, defaults tohttps://dashboard.bugfender.com/api~/.bugfender/mcp.json: optional config file and local token store for rotated credentials
{
"default": {
"apiToken": "YOUR_ACCESS_TOKEN",
"refreshToken": "YOUR_REFRESH_TOKEN",
"apiUrl": "https://dashboard.bugfender.com/api"
}
}
When a refresh token is provided, the MCP stores rotated credentials in ~/.bugfender/mcp.json so automatic refresh survives restarts. Updating the IDE config with a newly generated refresh token resets that local state.
These credentials and the local token store apply only to the stdio executable.
The hosted HTTP executable reads a bearer token from each request and never
reads or writes ~/.bugfender/mcp.json.
If you are using local or self-hosted Bugfender credentials, BUGFENDER_API_URL must point to the matching backend. For example, local credentials generated from https://dashboard:3000 will not work against https://dashboard.bugfender.com/api.
Legacy Cursor / Claude Code configuration
{
"mcpServers": {
"bugfender": {
"command": "npx",
"args": ["-y", "@bugfender/mcp"],
"env": {
"BUGFENDER_API_TOKEN": "YOUR_ACCESS_TOKEN",
"BUGFENDER_REFRESH_TOKEN": "YOUR_REFRESH_TOKEN",
"BUGFENDER_API_URL": "https://dashboard.bugfender.com/api"
}
}
}
}
Legacy Codex CLI configuration
codex mcp add bugfender \
--env BUGFENDER_API_TOKEN='YOUR_ACCESS_TOKEN' \
--env BUGFENDER_REFRESH_TOKEN='YOUR_REFRESH_TOKEN' \
--env BUGFENDER_API_URL='https://dashboard.bugfender.com/api' \
-- npx -y @bugfender/mcp
After running codex mcp add, restart the Codex session before testing who_am_i or list_apps.
Legacy Gemini CLI configuration
gemini mcp add bugfender npx -y @bugfender/mcp \
--env BUGFENDER_API_TOKEN='YOUR_ACCESS_TOKEN' \
--env BUGFENDER_REFRESH_TOKEN='YOUR_REFRESH_TOKEN' \
--env BUGFENDER_API_URL='https://dashboard.bugfender.com/api'
After running gemini mcp add, start a new Gemini CLI session or reload MCP servers before testing who_am_i or list_apps.
Legacy Codex App configuration
In the custom MCP server form:
Name:bugfenderCommand to launch:npxArgument 1:-yArgument 2:@bugfender/mcpBUGFENDER_API_TOKEN:YOUR_ACCESS_TOKENBUGFENDER_REFRESH_TOKEN:YOUR_REFRESH_TOKENBUGFENDER_API_URL:https://dashboard.bugfender.com/api
Add the arguments as separate rows, not as one combined string.
After saving the server, restart the app before testing who_am_i or list_apps.
Hosted Streamable HTTP deployment
Build and start the HTTP entry point with:
pnpm build
pnpm start:http
It exposes:
POST /mcp: stateless MCP Streamable HTTP endpointGET /healthz: liveness checkGET /readyz: readiness check
TLS is terminated by the production ingress. Every /mcp request must include
Authorization: Bearer <token>. The process creates an isolated MCP server and
Bugfender API client for that request; the token is neither shared nor persisted.
Hosted configuration:
BUGFENDER_API_URL(defaulthttps://dashboard.bugfender.com/api)BUGFENDER_MCP_HOST(default0.0.0.0)BUGFENDER_MCP_PORT(default3002)BUGFENDER_MCP_MAX_REQUEST_BYTES(default1048576)BUGFENDER_MCP_MAX_RESPONSE_BYTES(default524288)BUGFENDER_MCP_MAX_CONCURRENCY(default100)BUGFENDER_MCP_REQUEST_TIMEOUT_MS(default35000)BUGFENDER_MCP_SHUTDOWN_TIMEOUT_MS(default10000)
The hosted entry point uses JSON response mode within the Streamable HTTP
protocol. It is intentionally stateless, so GET and DELETE on /mcp return
405 Method Not Allowed.
The production container can be built and exercised locally with:
docker build -t bugfender-mcp .
docker run --rm --read-only --tmpfs /tmp:rw,noexec,nosuid,size=16m \
-p 3002:3002 bugfender-mcp
The image runs as UID/GID 10001, writes structured JSON logs to stderr, and
exposes Prometheus metrics on GET /metrics for cluster-internal scraping.
Hosted mode publishes OAuth protected-resource metadata at
GET /.well-known/oauth-protected-resource. Authentication challenges point
clients to that document. Production defaults to resource
https://mcp.bugfender.com/mcp, issuer https://dashboard.bugfender.com, and API
https://dashboard.bugfender.com/api;
staging deployments must override BUGFENDER_MCP_RESOURCE_URL and
BUGFENDER_OAUTH_ISSUER and BUGFENDER_API_URL with their staging values.
Documentation, privacy, and terms links can be overridden with BUGFENDER_MCP_DOCUMENTATION_URL,
BUGFENDER_MCP_PRIVACY_POLICY_URL, and BUGFENDER_MCP_TERMS_URL.
Hosted authentication troubleshooting
- Use the exact endpoint and OAuth resource
https://mcp.bugfender.com/mcp. - Do not configure
BUGFENDER_API_TOKENor paste a bearer token into a remote-hosted connection. - Disconnect and reconnect to recover from expired or revoked grants or to request different scopes.
update_issue_statusrequiresmcp:issues:write; investigation tools requiremcp:read.- A client must support remote Streamable HTTP, OAuth discovery, Authorization Code with PKCE, and resource indicators. Otherwise, use the deprecated local stdio fallback.
- Hosted OAuth currently supports Bugfender's public cloud. Self-hosted
deployments must use local stdio and set
BUGFENDER_API_URLto their backend.
Tools
who_am_ilist_teamslist_appsget_applist_app_versionsget_sdk_snippetget_crashesget_crash_statsget_crash_device_statsget_crash_detailssearch_logscount_logscount_devices_with_logsget_network_aggregatesget_network_detailssearch_devicescount_deviceslist_issuesget_issueupdate_issue_statusget_issue_statsget_issue_device_statsget_issue_devicesget_feedbackget_app_summary
Resources
bugfender://snippet/{app_id}/{platform}bugfender://app/{app_id}/logs?...bugfender://issue/{issue_id}?app_id={app_id}
Companion Skills
The companion skills now live in the separate bugfender/bugfender-skills repository. They encode opinionated workflows on top of the MCP tools:
- use aggregation before logs
- narrow time ranges early
- size impact before deep-diving
- end with a short triage summary
The MCP package gives the agent raw Bugfender capabilities. The skill adds an opinionated investigation workflow on top of those capabilities.
Use the skill when you want Cursor, Codex, or Claude Code to do things like:
- help set up the Bugfender SDK in an app with the minimum required steps
- fetch the SDK snippet for a platform and explain exactly where it goes
- investigate the top crashes in an app
- summarize issue or feedback trends over a time range
- compare impact before and after an app version
- identify likely cause, scope, and next checks
The investigation skill source lives in:
https://github.com/bugfender/bugfender-skills/tree/main/skills/bugfender
SDK Setup Skill
The dedicated onboarding skill also lives in bugfender/bugfender-skills.
Use it when you want Cursor, Codex, or Claude Code to:
- detect the project platform automatically
- fetch the correct Bugfender SDK snippet
- map the setup to the real repository files
- ask one short feature question when optional capabilities like crash reporting or Android logcat matter
- apply the minimum integration changes
- reduce the developer’s work to one final verification step
It also includes platform-specific references for:
- iOS
- Android
- Flutter
- Unity
- .NET MAUI
- Cordova
- Ionic
- Angular
- React
- Vue
- JavaScript
- jQuery
- Titanium
- Web
- React Native
The skill source lives in:
https://github.com/bugfender/bugfender-skills/tree/main/skills/bugfender-sdk-setup
Install Skills In Cursor, Codex, Or Claude Code
Cursor, Codex, and Claude Code can install the skills directly from GitHub without cloning the repo manually.
In the agent chat inside your IDE, run this prompt with the built-in installer skill:
Use $skill-installer to install these skills from https://github.com/bugfender/bugfender-skills:
- skills/bugfender
- skills/bugfender-sdk-setup
After installation, restart the client and use:
Use $bugfender-sdk-setup to set up Bugfender in this app with the minimum required changes.
Bugfender MCP questions
How do I add Bugfender MCP to Claude Code?
Run claude mcp add --env 'BUGFENDER_API_TOKEN=<YOUR_BUGFENDER_API_TOKEN>' --env 'BUGFENDER_REFRESH_TOKEN=<YOUR_BUGFENDER_REFRESH_TOKEN>' bugfender-mcp -- npx -y @bugfender/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Bugfender MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Bugfender MCP provide?
It exposes 25 tools, including who_am_i, list_teams, list_apps, get_app, list_app_versions.
What permissions does the mcp:read scope grant?
It provides read-only access to identity, teams, apps, SDK metadata, logs, devices, crashes, issues, feedback, network data, and summaries.
Can I use Bugfender MCP for local development?
Yes, you can use the deprecated local stdio fallback via the @bugfender/mcp npm package using npx.
Does the hosted MCP service store my credentials?
No, the hosted MCP forwards the bearer token to the Bugfender API and does not persist user credentials.