Model Context Protocol (MCP)

Connect your AI assistant to Pelcro's APIs through the Model Context Protocol (MCP). Pelcro exposes two MCP servers:

• Core API — manage an account as a publisher or operator: customers, subscriptions, invoices, products, and more.
• Open API — act on behalf of a single signed-in subscriber: their own subscriptions, addresses, payment methods, and more.

📘

We add tools and refine parameters as the APIs evolve. MCP clients should fetch tool definitions from the server at the start of each session rather than caching or hardcoding schemas. Want a tool we don't offer yet? Email us at [email protected].

Installation

Each client takes two entries — pelcro-api-core for the Core API and pelcro-api-open for the Open API.

Claude Code

claude mcp add --transport http pelcro-api-core https://mcp.pelcro.com/
claude mcp add --transport http pelcro-api-open https://mcp.pelcro.com/open

Start a new session with claude, type /mcp, select the server, and click Authenticate.

Cursor

Add to your project's .cursor/mcp.json:

{
  "mcpServers": {
    "pelcro-api-core": { "url": "https://mcp.pelcro.com/" },
    "pelcro-api-open": { "url": "https://mcp.pelcro.com/open" }
  }
}

VS Code

Add to your workspace's .vscode/mcp.json. See the VS Code MCP documentation for more details.

{
  "servers": {
    "pelcro-api-core": { "type": "http", "url": "https://mcp.pelcro.com/" },
    "pelcro-api-open": { "type": "http", "url": "https://mcp.pelcro.com/open" }
  }
}

Windsurf

Add to ~/.windsurf/mcp.json:

{
  "mcpServers": {
    "pelcro-api-core": { "url": "https://mcp.pelcro.com/" },
    "pelcro-api-open": { "url": "https://mcp.pelcro.com/open" }
  }
}

ChatGPT

ChatGPT supports remote MCP servers for Pro, Plus, Business, Enterprise, and Education accounts. Create a custom connector in Settings > Apps & Connectors for each server, selecting OAuth as the authentication method:

• Core API: https://mcp.pelcro.com/
• Open API: https://mcp.pelcro.com/open

See the OpenAI developer mode guide for detailed setup steps.

Other MCP clients

Any client that supports remote MCP servers over Streamable HTTP can connect to https://mcp.pelcro.com/ (Core API) or https://mcp.pelcro.com/open (Open API). The server handles OAuth discovery automatically via RFC 9728.

Authorize

After installing, your MCP client opens a browser window to complete authentication:

1. Log into your Pelcro account
2. Select which account to grant access to
3. Click Authorize
4. Return to your AI tool — the tools are now available

The token is scoped to a single account's API endpoints. Public Open API tools require no authentication; tools that act on a specific subscriber's data run under that subscriber's access token.

Manage your connection

Multi-account access

Each MCP server entry is scoped to one account. To access multiple accounts, add multiple entries with different names:

claude mcp add --transport http pelcro-acme https://mcp.pelcro.com/
claude mcp add --transport http pelcro-other https://mcp.pelcro.com/

Each entry triggers its own OAuth flow where you pick a different account on the consent screen.

Re-authenticate

If your token expires or you want to switch accounts, remove the server and re-add it:

claude mcp remove pelcro-api-core
claude mcp add --transport http pelcro-api-core https://mcp.pelcro.com/

Refreshing tools

MCP clients cache the list of available tools when they first connect. If new tools are added to a server, start a new session or reconnect to pick them up.

Environments

Core API tools

Most tools require a site_id parameter. If you don't know your site ID, use get_account first to discover your available sites. List tools support page and limit for pagination.

Every tool maps to a Core API endpoint, so the Core API reference documents the same parameters, filters, and response fields. The definitive list of tools is the one your MCP client shows after connecting — clients fetch it live from the server, so it always matches the current release.

Response size

Tool responses are capped at 25,000 characters to protect AI context windows. If a response is truncated, use a smaller limit value or add filters to narrow your results.

Error handling

API errors (400, 404, 429, 500, etc.) come back as tool results with isError: true rather than protocol-level failures, so the AI can read the error and retry with different parameters. The message carries the upstream status and response body, and on 429 the server's Retry-After.

The one exception is 401: a rejected access token returns an HTTP 401 with WWW-Authenticate so your client knows to re-authenticate, instead of reporting itself connected while every call fails.

Open API tools

Customer-facing tools served at https://mcp.pelcro.com/open. Public tools need no authentication; the rest act on the signed-in subscriber's own data. The underlying endpoints are documented in the Open API reference.

Additional customer-facing endpoints are reachable via open_api_discover (search) and open_api_call (execute), restricted to a curated allowlist.

Health check

curl https://mcp.pelcro.com/health

{ "status": "ok", "environment": "prd" }