Pages · MCP server

MCP server

The Partner API as tools for AI agents: setup, tools and safeguards. Test mode only.

Test mode only. The MCP server accepts tb_test_ keys and refuses live keys, even once the API opens live mode. Test orders are never made, charged for real or shipped.

The Tapebloom MCP server offers the Partner API as tools to AI agents and coding tools that speak the Model Context Protocol. It is at https://mcp.tapebloom.com/mcp (Streamable HTTP, stateless) and authenticates with your API key as a Bearer token, exactly like the API.

Connect

Export your test key as TAPEBLOOM_API_KEY, then add the server to your tool's config. Each snippet reads the key from the environment when the tool starts; never paste the key into the file.

Claude Code: .mcp.json
{
  "mcpServers": {
    "tapebloom": {
      "type": "http",
      "url": "https://mcp.tapebloom.com/mcp",
      "headers": {
        "Authorization": "Bearer ${TAPEBLOOM_API_KEY}"
      }
    }
  }
}
Cursor: .cursor/mcp.json
{
  "mcpServers": {
    "tapebloom": {
      "url": "https://mcp.tapebloom.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TAPEBLOOM_API_KEY}"
      }
    }
  }
}

Other clients: use the URL above with an Authorization: Bearer <key> header.

Tools

Each tool is one API operation and returns that operation's response body, so the reference describes its fields. A tool is listed only when your key has its scope.

ToolOperationScope
list_artwork_templatesGET /artwork_templatesorders:read
create_quotePOST /quotesorders:write
create_uploadPOST /uploadsuploads:write
finalize_uploadPOST /uploads/{id}/finalizeuploads:write
get_uploadGET /uploads/{id}uploads:write
get_billingGET /billingbilling:read
start_billing_setupPOST /billing/setupbilling:write
create_orderPOST /ordersorders:write
list_ordersGET /ordersorders:read
get_orderGET /orders/{id}orders:read
revise_orderPOST /orders/{id}/revisionsorders:write
cancel_orderPOST /orders/{id}/cancelorders:write
list_eventsGET /eventsevents:read

Upload bytes do not go through MCP: create_upload returns a signed URL, the agent PUTs the file there (with curl, say), then calls finalize_upload and checks get_upload until the upload is finalized. Webhook endpoints are managed through the API only.

Safeguards

  • Every write takes a required idempotency_key, sent as the Idempotency-Key header, so an agent can retry safely; reusing one for a different call is idempotency_mismatch.
  • create_order, revise_order and cancel_order are marked destructive. That is a hint to the client: many ask before running such a tool, but MCP does not require it, and how (or whether) a client asks is up to the client and its settings.
  • create_order (and revise_order onto a new quote) needs confirm_total_minor: the quote's subtotal_minor plus the chosen shipping option's amount_minor. A call is refused if the total cannot be worked out (quote_not_found, invalid_shipping_service) or does not match (total_mismatch), before the order is sent.
  • That check proves the agent used the right number, not that a person agreed to it. The server tells agents to show the person the total and wait for their OK, but it cannot see whether they did. In test mode nothing is charged; review your client's tool-approval settings before relying on an agent to order.
  • rights_warranty: true states that the account holder holds the rights to every recording and artwork and accepts the rights warranty. Agents are told to set it only when the person says so.
  • Every MCP message counts once against the key's API rate limit (300 a minute), refused calls included. A failed call returns the API's error, with its code and request_id, as a tool error.
  • Browsers cannot call the server: a request with an Origin header is refused.