MCP Server (AI Agents)

Miniback ships a remote MCP (Model Context Protocol) server so AI coding agents — Cursor, Claude Code, Windsurf, and anything else that speaks MCP — can pull a bug report with its full captured context and act on it. This is the “bug report → AI agent fix” pipeline: a teammate files a bug through the widget, and your agent picks it up with the URL, console errors, failed network requests, interaction steps, and screenshot already attached.

⚡ Quick Start

Mint an account API token in Settings → API (starts with mba_).

Point your MCP client at https://www.miniback.io/api/mcp/mcp.

Authenticate with the token as a bearer token or x-api-key header.

Plans: Builder unlocks the bug tools • Studio adds project-management tools.

Authentication

The MCP server authenticates with your account API token, not a project key.

Credential	Prefix	Use
Account token (`User.apiToken`)	`mba_`	Account-wide REST API and the MCP server
Project key (`Project.apiKey`)	`mbk_`	A single project’s feedback/settings over REST — not MCP

Mint, view (once), rotate, or revoke the account token in Settings → API. Treat it like a password — it grants account-wide access.

Connecting

The server speaks Streamable HTTP at:


https://www.miniback.io/api/mcp/mcp

The quickest path is the Connect to AI agents (MCP) card in Settings → API — pick your client and copy the snippet with your token already filled in. The same configs are below.

Cursor (~/.cursor/mcp.json) — native remote HTTP:


{
  "mcpServers": {
    "miniback": {
      "type": "http",
      "url": "https://www.miniback.io/api/mcp/mcp",
      "headers": { "x-api-key": "mba_your_account_token" }
    }
  }
}

Claude Code — one command:


claude mcp add --transport http miniback https://www.miniback.io/api/mcp/mcp --header "x-api-key: mba_your_account_token"

VS Code — one command:


code --add-mcp '{"name":"miniback","type":"http","url":"https://www.miniback.io/api/mcp/mcp","headers":{"x-api-key":"mba_your_account_token"}}'

Claude Desktop, Windsurf & other stdio-only clients — bridge with mcp-remote. In Claude Desktop this goes in claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json), then restart the app:


{
  "mcpServers": {
    "miniback": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://www.miniback.io/api/mcp/mcp",
        "--header", "x-api-key: mba_your_account_token"
      ]
    }
  }
}

Tools & plan gating

Every tool call counts against your monthly API quota and is gated by plan.

Bug tools — Builder plan and up

Tool	What it does
`list_bugs`	List recent bugs across your projects (filter by project slug / status).
`get_bug`	Fetch one bug as an AI-ready prompt with its full captured context.
`update_bug_status`	Set a bug to `NEW`, `IN_PROGRESS`, `RESOLVED`, or `DISMISSED`.

A typical loop: list_bugs → get_bug (reproduce & fix) → update_bug_status to RESOLVED.

Project-management tools — Studio plan only

Tool	What it does
`create_project`	Create a new project (returns its slug).
`pause_project`	Pause a project by slug (stops accepting feedback).
`unpause_project`	Reactivate a paused project by slug.
`customize_widget`	Update a project’s widget appearance/text by slug.
`manage_categories`	List / create / rename / delete a project’s categories by slug.

Plan identifiers: The dashboard shows plans as Hobby, Builder, and Studio, and tool messages use those display names. The API’s internal plan identifiers are FREE, STARTER, and PRO.

Troubleshooting

401 Unauthorized — the account token is missing or wrong. Re-check the header value and that the token hasn’t been rotated/revoked.
“available on the Builder and Studio plans” — the bug tools require a paid plan (STARTER/PRO).
“Project-management tools are available on the Studio plan only” — upgrade to Studio to create/manage projects from your agent.
“API call limit reached” — you’ve hit your monthly quota; it resets at the start of the month, or upgrade for a higher limit.

See also the API Reference and the API Security Guide.