Skip to Main Content

New accounts get 30 days of Pro free. No credit card. Start Free

Docs / Guides / FeedBlox MCP

How to Use FeedBlox MCP

FeedBlox MCP lets Cursor and other MCP clients read your sites and inbox, inspect client debug on a report, pull 30-day analytics, and update triage. It is included on Pro and Max.

Auth is a dashboard API key (fbx_...), not your password and not the dashboard access token. After you create a key, the API Keys page can print a ready-to-paste Cursor config.

Set Up

  1. Use a Pro or Max Account

    MCP is included on Pro and Max. Free keys receive 403. Open Billing if you need to upgrade.

  2. Create an API Key

    In the dashboard, open Settings, API Keys. Name the key (for example Cursor), click Create Key, and copy the fbx_ token. FeedBlox stores only a hash, so the secret cannot be shown again.

  3. Add the Server in Your Client

    Paste the MCP URL and Authorization Bearer header into Cursor, VS Code, or another Streamable HTTP MCP client. Reload MCP servers after saving.

  4. Ask in Chat

    Once the server is connected, ask the agent to list sites, search the inbox, read a report, or update triage. You do not call the tools by hand unless you are debugging.

Create a key at Settings, API Keys. Upgrade at Billing if you are on Free.

Connect Cursor

Open Cursor Settings, MCP, and add a remote HTTP server. Or save this as .cursor/mcp.json in a project. Replace YOUR_API_KEY with the token you copied, then reload MCP servers.

JSON 
{
  "mcpServers": {
    "feedblox": {
      "url": "https://api.feedblox.net/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Keep the token out of git. Prefer Cursor's secret field or an env var when the client supports it. Revoke the key from the same dashboard page if a laptop is lost or a config file leaked.

Connect VS Code

In VS Code, add a remote MCP server (for example in .vscode/mcp.json) with the same URL and Bearer header:

JSON 
{
  "servers": {
    "feedblox": {
      "type": "http",
      "url": "https://api.feedblox.net/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Other Streamable HTTP clients (including Claude Desktop remote MCP) use the same URL and Authorization header.

Use It in Chat

After the server shows as connected, talk to the agent in plain language. It will call FeedBlox tools on your behalf. Useful prompts:

  • List my FeedBlox sites.
  • Show the latest negative reports for acme.test.
  • Search the inbox for checkout and summarize the themes.
  • Open that report and quote the console errors and failed network calls.
  • Mark this report in_review, tag it checkout, and add a note that engineering has the repro.
  • Give me 30-day sentiment totals for acme.test.

Name the site the way it appears in the dashboard path (the hostname, such as acme.test) or pass the site id. The agent can call list_sites first if you are not sure.

Tool Reference

You rarely invoke these by name. This is what the server exposes so you know what an agent can do.

list_sites

Lists sites this account can access (id, name, URL, path, verification, triage flag). No arguments.

list_inbox

Lists report summaries. Omit site to search every accessible site.

  • site - hostname path or site id
  • sentiment - positive, neutral, or negative
  • status - open, in_review, or done
  • q - search comment and extra response text
  • tags - match automation or triage tags
  • limit - 1 to 100 (default 25)
  • offset - skip earlier rows

Rows omit the client debug blob so lists stay small. Use get_feedback for console, network, JS errors, the intent trail, and attachments.

get_feedback

Reads one report. Required: feedbackId. Returns the comment, tags, triage fields, client debug, intent trail, and attachment metadata.

get_analytics

30-day sentiment totals and daily counts. Required: site (hostname path or id).

update_triage

Updates one report. Required: feedbackId.

  • status - open, in_review, or done
  • tags - replace triage tags
  • note - triage note

The key can only update reports on sites you own or can triage as a member. Site secrets such as embed tokens are never returned.

Test the Connection

If a client will not connect, confirm the API key and plan with a JSON-RPC call. A 200 body with a tools list means auth works.

Bash 
curl -sS https://api.feedblox.net/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

List recent negative reports for one site:

Bash 
curl -sS https://api.feedblox.net/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_inbox","arguments":{"site":"acme.test","sentiment":"negative","limit":10}}}'

Auth Errors

  • 401 - missing, revoked, or unknown API key
  • 403 - the key is valid but the account is on Free

Last-used time on the API Keys page updates when MCP calls succeed. If Cursor shows the server as failed, reload MCP servers, confirm the URL is https://api.feedblox.net/mcp, and confirm the header is Authorization: Bearer fbx_... with no extra quotes.

FAQ

Do I use my login password?

No. Create a dashboard API key and send it as Authorization Bearer. Email, password, and the short-lived dashboard JWT are not accepted.

Where do I put the config file in Cursor?

Use Cursor Settings, MCP for a global server, or add .cursor/mcp.json in a project. Reload MCP servers after you save. Do not commit the token.

Why do I get 403?

The key is valid but the account is on Free. Upgrade to Pro or Max, then retry. 401 means the key is missing, revoked, or unknown.

Can the agent see client debug?

list_inbox returns report summaries without the debug blob. Ask the agent to call get_feedback on a report id when you need console, network, JS errors, and the intent trail.