Skip to main content

Use Bugfender with Claude

Bugfender can be used in Claude in two ways. Both use the same hosted MCP service and Bugfender OAuth connection, and neither requires you to copy an API token into Claude.

  • Bugfender Claude Plugin installs the Bugfender investigation and SDK-setup skills together with the hosted connector. Choose this when you want the guided Bugfender workflows as well as the tools.
  • Direct MCP Connector adds only the hosted Bugfender tools. Choose this when you want to connect Bugfender without installing the plugin.

The Claude Plugin is separate from the Bugfender Codex Plugin. The legacy local npx server is also a different connection method and is not needed for either hosted Claude option.

Supported Claude products​

The hosted Bugfender connector works anywhere Claude supports custom remote MCP connectors, including Claude on the web, Claude Desktop, Cowork, and Claude Code. Custom connector availability and administration can depend on your Claude plan and workspace policy.

The Bugfender Claude Plugin is intended for Claude on the web, Claude Desktop, Cowork, and Claude Code. Plugins require a paid Claude plan. A plugin installed in Claude can synchronize to a recent Claude Code version when both use the same Claude account. See Anthropic's current plugin availability and connector availability for plan and workspace restrictions.

Install the Claude Plugin​

Claude and Claude Desktop​

  1. Open Customize > Plugins > Discover.
  2. Find Bugfender and select Add.
  3. Open the Bugfender plugin and select Connect when prompted.
  4. Sign in to Bugfender, review the permissions, and select Allow.
  5. Start a new conversation and ask Claude to list your Bugfender apps.

If Bugfender is not yet listed in the Claude plugin directory, use the direct connector below or install the repository marketplace in Claude Code.

Claude Code repository marketplace​

From a checkout of bugfender/bugfender-skills:

claude plugin marketplace add ./
claude plugin install bugfender@bugfender-private

Restart Claude Code after installation. For a development session that loads a checkout without installing it, run:

claude --plugin-dir /absolute/path/to/bugfender-skills

The first Bugfender tool call starts OAuth in your browser. The plugin contains the server URL and skills, but no client secret or user token.

Upgrade or remove the repository installation with:

claude plugin update bugfender@bugfender-private
claude plugin uninstall bugfender@bugfender-private
claude plugin marketplace remove bugfender-private

Connect the MCP Connector directly​

  1. Open Customize > Connectors in Claude or Claude Desktop.

  2. Select Add custom connector.

  3. Enter Bugfender as the name and this URL:

    https://mcp.bugfender.com/mcp
  4. Keep the default OAuth configuration. Do not add a bearer token, client secret, or custom authorization header.

  5. Add the connector, select Connect, and complete Bugfender sign-in and consent.

Claude connects to this URL from Anthropic's cloud. A local URL such as localhost therefore cannot be used as a custom connector in hosted Claude.

Claude discovers Bugfender's authorization server from the MCP endpoint and uses Authorization Code with S256 PKCE. After you sign in, the consent screen shows the client requesting access and these possible scopes:

  • mcp:read provides identity and team lookup and read-only access to the apps, SDK metadata, logs, devices, crashes, issues, feedback, network data, and app summaries that your Bugfender account can already access.
  • mcp:issues:write permits only changes made by update_issue_status. It does not grant general administration of apps, teams, accounts, or billing.

All current investigation tools are read-only. update_issue_status is the only state-changing tool. Claude should request confirmation before it changes an issue status, and your Bugfender permissions still apply.

Access and refresh tokens are bound to the signed-in user, OAuth client, MCP resource, and granted scopes. Claude refreshes an expiring access token in the background. Refresh cannot add scopes. If a refresh token is invalid, expired, revoked, or already replaced, Claude must start authorization again.

Connect, disconnect, and reconnect​

To make Bugfender available in a conversation, enable it from the conversation's Connectors menu. To remove the account grant, open Customize > Connectors, select Bugfender, and choose Disconnect.

Disconnecting revokes the hosted Bugfender grant and its access and refresh tokens. Uninstalling the plugin removes its skills and configuration, but it may not revoke a separately stored connection; disconnect first when both actions are shown. Reconnect to switch Bugfender accounts, request different scopes, or recover from revoked credentials.

Claude Code loopback authorization​

Claude Code opens Bugfender authorization in your browser and listens on a temporary loopback callback. Bugfender accepts dynamic ports for both forms:

http://localhost:<port>/callback
http://127.0.0.1:<port>/callback

The loopback listener is local even though the MCP service is hosted. Do not replace the generated callback URL or configure a fixed port. If the browser and Claude Code run on different machines or inside different containers, ensure the browser can return to the loopback listener used by Claude Code.

Response size and pagination​

Bugfender tools return normalized, bounded results. Hosted Claude supports tool results up to roughly 150,000 characters, while Claude Code warns and truncates according to its own token limits. Avoid requesting an entire incident history in one call:

  • Continue log searches with pagination.next.
  • Continue device searches with pagination.next_cursor.
  • Continue issue and affected-device lists with page numbers.
  • Page size defaults to 100 and is capped at 200. Network request samples are capped at 100 per page.
  • Use count and summary tools before retrieving detailed records when possible.

Troubleshooting​

Discovery fails or the connector stays unavailable​

  • Confirm the server URL is exactly https://mcp.bugfender.com/mcp.
  • Remove manually configured authorization headers or bearer tokens.
  • Confirm your Claude workspace permits custom connectors.
  • Retry after a short interval if Claude reports a discovery or initialization timeout. Discovery, client registration, and token exchange must each finish promptly; a firewall, proxy, or strict origin policy can interrupt them.

Client registration fails​

Claude first uses Bugfender's published client metadata and can fall back to dynamic client registration when advertised. Remove and re-add the connector to clear stale registration data. Do not create or paste a client secret. If the problem persists, record which Claude product you used and the registration error shown to you.

Callback URI mismatch​

For hosted Claude, the authorization request should use a Claude-hosted callback such as:

https://claude.ai/api/mcp/auth_callback
https://claude.com/api/mcp/auth_callback

Claude Code should use one of the dynamic loopback callbacks described above. Do not edit the callback. Disconnect and add the connector again if an old registration supplied a different URI.

Authorization, scope, or refresh fails​

  • Sign in with the Bugfender account that can access the intended team and app.
  • Approve mcp:read; approve mcp:issues:write only when status updates are required.
  • Disconnect and reconnect after changing accounts or scopes.
  • If a request reports insufficient scope, do not copy a token into Claude. Reconnect and approve the required scope instead.
  • If refresh or reauthorization repeatedly fails, revoke the Bugfender connection, remove it from Claude, add it again, and complete fresh consent.

When contacting support, include the Claude product and version, approximate time and time zone, MCP endpoint, affected operation, and sanitized error or request ID. Never send access tokens, refresh tokens, authorization codes, PKCE verifiers, or raw sensitive log payloads.

Privacy and data processing​

The connector can return Bugfender data that your signed-in account is allowed to view. Depending on the tools you use, that can include logs and network metadata supplied by your applications, device metadata, crashes, issues, feedback, app identifiers, and SDK configuration. Tool requests and results are also processed by Claude under your Anthropic plan and settings.

Connections to Bugfender and Claude are encrypted, but the services process data on their respective infrastructure and under their respective terms. Review your retention, regional-processing, and access-control requirements before using production data. See the Bugfender Privacy Policy, Bugfender Terms of Service, and Anthropic's connector privacy guidance linked under supported products.

Support and escalation​

Contact support@bugfender.com or use Bugfender's support chat. Include the sanitized diagnostic details listed above. For an active incident, follow the escalation and response-time path included in your Bugfender support plan. Report suspected credential exposure or another security issue immediately and revoke the affected connection.

Codex Plugin​

The Codex Plugin packages the same Bugfender MCP tools and companion skills for ChatGPT and Codex. Install Bugfender from the plugin directory, select Connect, and complete Bugfender OAuth. Claude and Codex may store separate grants, so disconnect each client independently when removing access.

Legacy local stdio server​

The @bugfender/mcp npx workflow is retained only for existing local integrations, clients without remote OAuth, and self-hosted Bugfender deployments. It requires a local Node.js process and locally managed credentials, does not install the Claude Plugin skills, does not use the hosted OAuth connection, and cannot be used by Claude's cloud-hosted custom connector.

New Claude installations should use the plugin or direct remote connector. See Client Setup only when maintaining an existing stdio deployment.