FeedbackJar
MCP Integration ✓ 1 minute setup

FeedbackJar + Claude Code

.mcp.json (project) or ~/.claude.json (user scope)

Claude Code reads MCP servers from .mcp.json in your project root (or ~/.claude.json for user scope). Add FeedbackJar and your agent can work through the bug queue without leaving the terminal.

How to connect FeedbackJar to Claude Code

1

Create an API token

bash
# Workspace token: Dashboard → Settings → API Tokens → fj_live_...
# Account token: Account → API Tokens → fj_user_...
2

Option A — CLI (fastest)

bash
claude mcp add --transport http feedbackjar \
  https://api.feedbackjar.com/mcp \
  --header "Authorization: Bearer fj_live_..."

Adds to your current project's MCP config. Use --scope user for all projects.

3

Option B — .mcp.json in project root

json
{
  "mcpServers": {
    "feedbackjar": {
      "type": "http",
      "url": "https://api.feedbackjar.com/mcp",
      "headers": {
        "Authorization": "Bearer ${FEEDBACKJAR_API_KEY}"
      }
    }
  }
}

Claude Code supports ${VAR} expansion — keep secrets out of git. Commit .mcp.json, export the key in your shell.

4

Start a session and verify

bash
# Start Claude Code in your project, then run:
/mcp

# Or ask directly:
List the top 5 open bugs from FeedbackJar.

Start a new Claude Code session after editing .mcp.json — config is read at startup.

What you get

  • CLI or .mcp.json setup
  • Environment variable expansion for secrets
  • Project-scoped config for teams
  • HTTP transport (recommended over SSE)
  • OAuth not required — Bearer token auth
  • Full read/write tool access with write keys

Close the loop from Claude Code

Users report bugs through your widget. Your agent reads the top votes via MCP, ships the fix, and every voter gets notified.

Start Free Trial 7-day free trial · No credit card required

Frequently Asked Questions

Looking for the full tool reference? Read the MCP Server docs →