Where does Cursor store MCP configuration?

Project-scoped servers go in .cursor/mcp.json at your repo root. Global servers go in ~/.cursor/mcp.json. Project config is ideal for team-shared FeedbackJar access.

Can I use an account token across multiple workspaces?

Yes. Omit X-Organization-Id and ask your agent to call list_organizations first, then pass organization_id to other tools. Or pin to one workspace with X-Organization-Id.

My MCP server shows as disconnected — what do I check?

Verify the API token is valid, the url is https://api.feedbackjar.com/mcp, and the Authorization header uses Bearer fj_live_... or fj_user_... format. Reload Cursor after editing mcp.json.

Does Cursor support token-in-URL auth?

If your setup can't send headers, use https://api.feedbackjar.com/mcp?token=fj_live_... instead. Headers are preferred — URL tokens may appear in logs.

MCP Integration ✓ 1 minute setup

FeedbackJar + Cursor

.cursor/mcp.json (project) or ~/.cursor/mcp.json (global)

Cursor supports HTTP MCP servers via project or global config. Add FeedbackJar once and your agent can read top-voted bugs, pull widget metadata, and close the loop from the editor.

Create API token → API tokens guide →

How to connect FeedbackJar to Cursor

Create an API token

bash

# Workspace token (one project): Dashboard → Settings → API Tokens
# Account token (all workspaces): Account → API Tokens

# Workspace tokens start with fj_live_
# Account tokens start with fj_user_

→ See the API Tokens guide for workspace vs account token tradeoffs.

Add to .cursor/mcp.json

json

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

→ Create .cursor/mcp.json in your project root, or edit ~/.cursor/mcp.json for a global setup.

Account token — pin to one workspace (optional)

json

{
  "mcpServers": {
    "feedbackjar": {
      "type": "http",
      "url": "https://api.feedbackjar.com/mcp",
      "headers": {
        "Authorization": "Bearer fj_user_...",
        "X-Organization-Id": "your_workspace_id"
      }
    }
  }
}

→ With X-Organization-Id set, tools behave like a workspace token — no organization_id param needed.

Reload and try it

bash

# In Cursor chat, ask:
What are the top open bugs in FeedbackJar?

# Or:
Get post cm1abc123 and summarize the widget metadata.

→ Restart Cursor or reload the window if the server doesn't appear immediately.

What you get

✓ Project or global MCP config
✓ HTTP transport with Bearer auth
✓ Works in Agent and Chat modes
✓ Supports env var expansion in headers
✓ Full FeedbackJar tool suite
✓ Organization scoped access

Close the loop from Cursor

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 →

Widget integrations → All MCP agents → Compare alternatives →