Paddle MCP Server

Official Paddle MCP server from PaddleHQ enabling AI agents to interact with Paddle's merchant-of-record billing platform — querying subscriptions, managing customers and transactions, accessing revenue analytics, handling refunds, and integrating Paddle billing operations into agent-driven business workflows. Paddle handles tax compliance and payments globally.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Other paddle payments billing subscriptions mcp-server official saas revenue
⚙ Agent Friendliness
78
/ 100
Can an agent use this?
🔒 Security
88
/ 100
Is it safe for agents?
⚡ Reliability
78
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
75
Documentation
78
Error Messages
75
Auth Simplicity
85
Rate Limits
80

🔒 Security

TLS Enforcement
95
Auth Strength
88
Scope Granularity
85
Dep. Hygiene
82
Secret Handling
88

HTTPS. API key. PCI-DSS/SOC2. Financial and customer data — highly sensitive. Official Paddle MCP. Use sandbox for testing. Scope to read-only where possible.

⚡ Reliability

Uptime/SLA
82
Version Stability
78
Breaking Changes
75
Error Recovery
75
AF Security Reliability

Best When

A SaaS company using Paddle as their merchant of record needs AI-assisted billing management — querying subscription data, managing customer accounts, and generating revenue reports.

Avoid When

You use Stripe, Chargebee, or other billing platforms — use the appropriate payment processor MCP.

Use Cases

  • Querying subscription status and customer billing data from business intelligence agents
  • Managing subscription changes and cancellations from customer success agents
  • Accessing revenue and transaction data for reporting from analytics agents
  • Handling refund requests from customer service agents
  • Monitoring billing anomalies from operations agents
  • Generating billing reports from financial reporting agents

Not For

  • Teams not using Paddle for billing (use Stripe, Chargebee, or Recurly MCPs for those)
  • Creating new charges or subscriptions without authorization controls
  • Real-time payment processing requiring ultra-low latency

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
Yes

Authentication

Methods: api_key
OAuth: No Scopes: Yes

Paddle API key required. Set PADDLE_API_KEY environment variable. Use sandbox API key for testing. Sandbox vs production environments have different keys. Available from Paddle Dashboard → Developer Tools.

Pricing

Model: usage_based
Free tier: Yes
Requires CC: No

Paddle is merchant of record — they handle taxes and compliance. Per-transaction fees. MCP server is free open source from official PaddleHQ organization.

Agent Metadata

Pagination
cursor
Idempotent
Full
Retry Guidance
Documented

Known Gotchas

  • Always use sandbox API key for testing — sandbox and production have separate credentials
  • Revenue data is highly sensitive — restrict agent access to read-only operations where possible
  • Paddle API v2 has breaking changes from v1 — verify which version your integration uses
  • Official MCP from PaddleHQ — high quality, well-documented, actively maintained
  • Subscription operations have real financial implications — implement confirmation for destructive actions
  • Paddle handles taxes as merchant of record — tax data is included in transaction records

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Paddle MCP Server.

$99

Scores are editorial opinions as of 2026-03-06.

5178
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered