MCP

Quickstart

Paid’s MCP server lets you inspect and manage Paid resources directly from AI-powered coding tools like Claude Code, Claude Desktop, Cursor, and Windsurf. Instead of switching between your editor and the Paid API docs, you can ask your assistant to list customers, inspect products, create test data, or run safe read-only checks while it already has context on the code you are building.

Setup

Prerequisites

  • A Paid account with an API key
  • An MCP-compatible AI tool such as Claude Code, Claude Desktop, Cursor, or Windsurf

Get your API key

  1. Log in to Paid.
  2. Go to Settings -> API keys.
  3. Create or copy an API key.

Installation

Add the Paid MCP server to your tool’s MCP configuration. The exact steps depend on which client you use.

Claude Code

$claude mcp add \
>  --transport http \
>  paid \
>  https://mcp.agentpaid.io/mcp \
>  --header "Authorization: Bearer YOUR_PAID_API_KEY"

Claude Desktop

Claude Desktop custom connectors cannot send static bearer headers to hosted MCP servers. Configure Claude Desktop to run a local mcp-remote bridge instead.

Add this server to ~/Library/Application Support/Claude/claude_desktop_config.json:

1{
2  "mcpServers": {
3    "paid": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote",
8        "https://mcp.agentpaid.io/mcp",
9        "--transport",
10        "http-only",
11        "--header",
12        "Authorization:Bearer YOUR_PAID_API_KEY"
13      ]
14    }
15  }
16}

Fully quit and reopen Claude Desktop after changing the config.

Other MCP clients

Most MCP clients support adding servers through a JSON configuration file. Add the following to your client’s MCP config:

1{
2  "mcpServers": {
3    "paid": {
4      "type": "http",
5      "url": "https://mcp.agentpaid.io/mcp",
6      "headers": {
7        "Authorization": "Bearer YOUR_PAID_API_KEY"
8      }
9    }
10  }
11}

Replace YOUR_PAID_API_KEY with the key you copied from Paid. Check your client’s documentation for the specific config file location and whether it expects headers, env, or connector-level auth settings.

Verify the connection

Once connected, confirm things are working by asking your AI assistant:

List my Paid customers.

or:

Show me my Paid products.

If your API key has access to more than one Paid organization, include the organization ID using the paidOrganizationId tool argument:

List Paid customers with paidOrganizationId set to <organization_id>.

What you can do

Once connected, you can ask your AI assistant to:

  • Inspect Paid resources: List customers, products, plans, orders, invoices, checkouts, webhooks, pricing configurations, and value receipts.
  • Create and update test data: Create customers, draft orders, products, contacts, checkouts, and other resources while developing integration flows.
  • Record signals and costs: Send signals and cost events from examples in your codebase to validate billing and analytics behavior.
  • Debug billing flows: Check order state, invoice state, credit balances, customer portal sessions, and related resources without leaving your editor.