Skip to main content

Set Up Bugfender MCP

Use the setup that matches your client. In every case, restart the client after adding or updating the MCP server.

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​

After restarting the client, 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.

If who_am_i or list_apps fails with token_expired, 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