Claude Paddle integration: Paddle MCP server

A billing question should identify the customer, subscription or transaction and state whether the output is a report or a mutation. “Why did this renewal fail?” is a read task. “Cancel the subscription” is a change with immediate business consequences. Have the agent show the relevant record and proposed action before execution.

The remote OAuth connection starts with Paddle’s read permissions. Writing also requires an appropriate change to the provider permissions; changing an AIPx tool mode cannot expand those permissions. Conversely, granting vendor write access does not mean every agent should receive execution authority.

Code-mode execution is the important boundary. A single script can collect records, make a change and collect another result. Confirm applies to that whole invocation, not each individual operation inside it. Review the script as one unit.

Paddle MCP server options

The Paddle MCP documentation and remote-server announcement describe the hosted route. The official repository covers the package implementation. Do not treat old local endpoint-tool counts as the live remote catalog.

A direct official connection is simpler for Paddle-only work. AIPx adds a gateway handling billing context; its benefit is combining that context with other restricted services and reusing the connection across agents.

Connect Claude to Paddle

Choose the official Paddle connection and complete OAuth. A separate sandbox connector uses an API key; keep sandbox and live credentials independently configured.

1. Open the AIPx dashboard, choose Paddle under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Paddle; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to Paddle

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Paddle is the only service you need.

Paddle MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

Use /mcp to authorize, then search Paddle methods before proposing a billing script. Confirm reviews the entire execute invocation, including nested calls. Claude Code MCP setup explains HTTP registration and login.

Paddle MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

After Cursor OAuth, inspect Paddle’s search and execute tools. Show the complete script and billing IDs before execution; report_missing_tool can stay hidden. See Cursor MCP setup for client approval controls.

Paddle MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Paddle credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

ChatGPT custom MCP can use the Paddle agent where access is enabled. Keep billing execution behind review and do not assume sandbox authority applies to live subscriptions. ChatGPT MCP setup explains client and workspace eligibility.

Scope Paddle per agent: writes on Confirm

For documentation research, allow search and hide execute. A billing analyst who must retrieve account records may need execution on Confirm even for read-only scripts, because the same tool can write when upstream permissions permit. This makes the whole script the review point.

Hide report_missing_tool unless you explicitly want to send the external report. General defaults are Allow for reads and Confirm for writes; the table applies stricter recommendations to this mixed surface. MCP permissions explains why tool hiding is stronger than a client approval hint.

Paddle and Stripe in one agent

Connect Stripe separately to compare billing across providers. Keep each environment and account explicit, and produce the reconciliation as a report before approving any change. Google Sheets can hold the reviewed report, and Linear can receive a follow-up ticket after approval.

Paddle billing permissions and environment limits

Check whether a task is targeting live billing or a sandbox. A successful sandbox query does not establish authority to change a live subscription, and a provider permission error cannot be repaired by wording the prompt more strongly.

Keep external capability reporting deliberate. report_missing_tool is a write because it sends a request outside the billing lookup workflow. Hide it for normal analysis. Provider API permissions, quotas and supported methods remain in force; AIPx does not bypass them or insert approvals into the middle of an execution script.

Browse all MCP integrations to choose another connection for this agent.

The Paddle connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.