Skip to main content

Set Up Bugfender MCP

Use hosted OAuth unless you specifically need a local stdio process or a self-hosted Bugfender backend.

For Claude, use the dedicated Claude Plugin and Connector guide. It covers supported Claude products, plugin and custom connector installation, OAuth callbacks, disconnecting, privacy, and troubleshooting.

ChatGPT and Codex Plugin​

  1. Open Plugins.
  2. Find and install Bugfender.
  3. Select Connect for the Bugfender app included with the plugin.
  4. Sign in to Bugfender, review the requested scopes, and approve access.
  5. Start a fresh task and run the verification prompt below.

No Bugfender access or refresh token needs to be copied into ChatGPT or Codex.

Direct remote MCP connection​

For a client that supports remote Streamable HTTP with OAuth, add this server URL:

https://mcp.bugfender.com/mcp

Choose OAuth authentication if the client asks. The client should discover:

  • protected-resource metadata from https://mcp.bugfender.com/.well-known/oauth-protected-resource
  • authorization-server metadata from https://dashboard.bugfender.com/.well-known/oauth-authorization-server

Complete the browser sign-in and consent flow opened by the client. A client that requires a command, environment token, or manually entered bearer token is configuring local stdio, not the hosted OAuth connection.

Disconnect and reconnect​

Use the client's Disconnect action for the Bugfender connection. This revokes the hosted OAuth grant, including its access and refresh tokens. If the plugin and connection are shown separately, disconnect the connection before uninstalling the plugin.

Reconnect when you need different scopes, switch accounts, or see an expired or revoked-token challenge.

Legacy local stdio​

The npx package is deprecated for new installations but remains available as a compatibility fallback for clients without remote OAuth and for self-hosted Bugfender installations.

Cursor / Claude Code​

Use a standard MCP config file:

{
"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"
}
}
}
}

Codex CLI​

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 it.

Codex App​

In the custom MCP server form:

  • Name: bugfender
  • Command to launch: npx
  • Argument 1: -y
  • Argument 2: @bugfender/mcp
  • BUGFENDER_API_TOKEN: YOUR_ACCESS_TOKEN
  • BUGFENDER_REFRESH_TOKEN: YOUR_REFRESH_TOKEN
  • BUGFENDER_API_URL: https://dashboard.bugfender.com/api

Add the arguments as separate rows, not as one combined string.

Gemini CLI​

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 it.

Verify the setup​

Start a fresh task and run:

Check that the Bugfender MCP is working.
Call who_am_i.
Call list_apps and confirm the expected app is visible.
Reply with a one-line confirmation only.

For hosted connections, a missing, invalid, expired, revoked, wrong-audience, or insufficient-scope token should trigger the client's connection flow. If it does not:

  • Confirm the URL is exactly https://mcp.bugfender.com/mcp.
  • Remove any manually configured bearer token from the remote connection.
  • Disconnect and reconnect Bugfender to obtain a fresh grant.
  • Approve mcp:read; approve mcp:issues:write when using update_issue_status.
  • Start a fresh task so the client reloads the connection and tools.

For legacy local stdio failures, check these first:

  • The token pair is the latest generated pair
  • BUGFENDER_API_URL matches the environment where the credentials were created
  • Both the access token and refresh token were updated

Supported clients and limitations​

  • The Claude Plugin is the recommended Claude setup when you also want the Bugfender skills; the direct Connector provides only the MCP tools.
  • The Codex Plugin is the recommended setup for ChatGPT and Codex.
  • Direct URL setup requires a client that supports remote Streamable HTTP, OAuth discovery, Authorization Code with PKCE, and resource indicators.
  • Legacy stdio works only where the client can launch a local Node.js process and pass environment variables.
  • Hosted Bugfender OAuth currently targets Bugfender's public cloud. Self-hosted installations must use legacy stdio with BUGFENDER_API_URL set to their own backend until hosted OAuth for custom deployments is supported.