Skip to main content

Bugfender MCP

Bugfender MCP exposes Bugfender data through the Model Context Protocol so AI agents can investigate logs, crashes, issues, devices, feedback, and app metadata directly from your IDE or CLI.

What it provides​

  • User-scoped Bugfender read access
  • Automatic access-token refresh when a refresh token is configured
  • Tools for logs, devices, apps, crashes, issues, feedback, and SDK snippets
  • Resource templates for snippets, logs, and issue groups
  • Companion skills for investigation and SDK setup

Package​

The MCP server is published as @bugfender/mcp.

Run it directly with:

npx -y @bugfender/mcp

If you add or update the MCP server in your IDE or agent, restart that client before testing it.

Credentials​

Bugfender MCP uses these environment variables:

  • BUGFENDER_API_TOKEN: required access token
  • BUGFENDER_REFRESH_TOKEN: recommended for automatic token refresh
  • BUGFENDER_API_URL: optional override, defaults to https://dashboard.bugfender.com/api

If you regenerate MCP credentials, the previous token pair is revoked. Any IDE still using the old values will stop working until both tokens are updated.

If you use local or self-hosted Bugfender credentials, BUGFENDER_API_URL must point to the matching backend. For example, credentials created from https://dashboard:3000 will not work against https://dashboard.bugfender.com/api.

Next steps​