Paddle MCP. Manage every aspect of SaaS billing from chat.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Paddle MCP Server manages all billing operations for your SaaS platform. It lets your agent read customer profiles, list active and past-due subscriptions, fetch detailed transaction ledgers, and even pause or cancel recurring plans—all without you ever touching the Paddle dashboard.
This tool handles everything from catalog pricing to complex tax calculations.
What your AI agents can do
Cancel subscription
Cancels an active subscription, letting you specify if the effect is immediate or at the end of the current billing period.
Get customer details
Fetches all core data points for a specific customer ID within Paddle's system.
Get subscription details
Retrieves the current status and billing schedule for an individual subscription using its unique ID.
Marks an active service plan for cancellation; you specify if the change takes effect immediately or when the current paid period ends.
Retrieves all key details, including tax boundaries and billing status, for a specific Paddle account ID.
Gets the current state of a service plan—whether it's active, suspended, or expired—along with its next billing date.
Retrieves full details for any single payment record, allowing you to check tax amounts and proration charges.
Gets a complete list of your SaaS offerings and the corresponding localized price structures defined in Paddle.
Pulls an array of IDs for every customer account managed through Paddle, useful for bulk operations or reporting.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Paddle MCP Server: 10 Tools for Billing Ops
These tools let your AI client handle every aspect of billing—from listing products to pausing subscriptions—without needing direct access to the Paddle dashboard.
019d75edcancel subscription
Cancels an active subscription, letting you specify if the effect is immediate or at the end of the current billing period.
019d75edget customer details
Fetches all core data points for a specific customer ID within Paddle's system.
019d75edget subscription details
Retrieves the current status and billing schedule for an individual subscription using its unique ID.
019d75edget transaction details
Pulls every specific detail associated with a single payment transaction, including tax breakdowns.
019d75edlist catalog prices
Returns a complete list of all defined pricing structures and their localized checkout prices for your products.
019d75edlist catalog products
Retrieves the names, IDs, and general details for every product listed in your Paddle catalog.
019d75edlist customers
Generates a list of all customer account IDs currently managed by Paddle.
019d75edlist subscriptions
Pulls an array of IDs and basic status information for every subscription active in your system.
019d75edlist transactions
Provides a paginated list of all billing transactions, useful for auditing recent payments or filtering by date range.
019d75edpause subscription
Temporarily suspends an active subscription's billing status without deleting the customer account.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Paddle, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Paddle MCP Server - Billing Management
This server gives your agent direct access to all of Paddle's billing data, letting you run complex financial queries or manage service plans without ever logging into the main dashboard. You don't need to touch the UI; you just tell your AI client what you need done. It handles everything from checking tax boundaries on a single customer account to listing every product price in the entire catalog.
Customer and Account Records
You can start by getting a full roster of who’s paying you with list_customers, which pulls an array of every current customer ID managed within Paddle. Once you have that list, you run get_customer_details against any specific ID to pull all the core data points for that client—this includes their billing status and crucial tax identification boundaries.
Knowing these details lets your agent verify if a customer is set up correctly before running any changes.
Subscriptions and Plans
The subscription tools let you manage the entire service lifecycle. If you want an overview, list_subscriptions pulls basic status information and IDs for every plan active in your system. To drill down on one specific client's plan, use get_subscription_details. This tells you if the plan is currently active, suspended, or expired, plus its next scheduled billing date.
When it comes time to adjust a plan, you have three options: pausing an account. Running pause_subscription temporarily suspends the client's ability to be billed without deleting their whole account record. If you need to cancel, cancel_subscription marks the service for termination; remember that this tool lets you specify whether the change needs to take effect immediately or if it should wait until the end of their current paid billing cycle.
Transaction Auditing and History
The financial tools let you audit every single dollar coming in. You can get a high-level overview using list_transactions, which provides a paginated list of all billing transactions, making it easy to filter for payments within a specific date range or check recent activity. For the deep dive—the kind that tracks down where a tax charge came from—you use get_transaction_details.
This pulls every single piece of data associated with one payment record, including detailed breakdowns of any proration charges or localized taxes applied.
Product and Pricing Catalog
To manage what you're selling, your agent uses the catalog tools. You can get a complete inventory list using list_catalog_products, which returns the names, IDs, and general details for every single product defined in your Paddle setup. Separately, if you need to know how much those products cost right now, run list_catalog_prices.
This pulls a full definition of all pricing structures, including the localized checkout prices that apply across different regions.
By combining these tools—listing customer IDs with list_customers, pulling their core data with get_customer_details, checking their plan status with get_subscription_details, and then running an audit on a specific payment using get_transaction_details—your agent manages your entire billing backend. You'll handle everything from catalog pricing to complex tax calculations, keeping you out of the Paddle dashboard entirely.
How Paddle MCP Works
- 1 Subscribe to the server and provide your necessary Paddle API Key.
- 2 Your AI client calls a tool (e.g.,
list_transactions) specifying required parameters like dates or IDs. - 3 The server executes the corresponding Paddle API call, returning structured JSON data directly to your agent.
The bottom line is: it turns complex, multi-step billing dashboard actions into simple, reliable tool calls from chat.
Who Is Paddle MCP For?
This is for the FinOps specialist or support engineer who gets stuck having to jump between a CRM and the billing portal just to check one payment status. If your job involves revenue auditing, subscription lifecycle management, or dealing with complex tax calculations, you need this. It lets you run those checks from where you are working.
Uses get_customer_details and get_subscription_details to quickly confirm a customer's payment status or verify if a requested pause is possible, without escalating the ticket.
Runs list_transactions and list_subscriptions in bulk to spot revenue anomalies, check for expired plans, or pull structured data arrays for quarterly reporting.
Uses get_transaction_details and list_catalog_prices to verify tax compliance boundaries across different regions or calculate historical proration charges.
What Changes When You Connect
- Instant Billing Audit: You don't need to navigate the Paddle portal. Use
list_transactionsorget_transaction_detailsto pull specific payment records—like a proration charge from six months ago—and get the data instantly for your agent to analyze. - Precise Subscription Control: Don't just guess if a plan is active. Run
get_subscription_detailsto confirm the next billing date and status, or usepause_subscriptionwhen you need temporary service interruption without canceling the account. - Tax Compliance Verification: Dealing with tax boundaries shouldn't be guesswork. By calling
list_catalog_prices, your agent retrieves localized pricing definitions and tax-inclusive amounts, ensuring billing accuracy before a user even checks out. - Bulk Customer Visibility: Need to check 50 accounts? Instead of running 50 manual searches, use
list_customersto get the IDs, then batch runget_customer_detailsto gather all necessary tax and contact data for compliance reports. - Full Lifecycle Management: From listing products with
list_catalog_productsto cancelling a plan usingcancel_subscription, this single server handles the entire billing lifecycle. Your agent moves from catalog view straight into account management in one session.
Real-World Use Cases
Investigating a mysterious failed payment.
A customer reports they were charged twice, but can't find the proof. They ask their agent to check the ledger. The agent runs list_transactions filtered by date, finds two transactions (one marked 'Paid,' one marked 'Prorated'), and uses get_transaction_details on both IDs to show the customer the exact breakdown of charges.
A departing client needs their access paused.
The account manager talks to their agent: 'Pause sub_clientxyz for 30 days.' The agent runs pause_subscription, which updates the status and prevents billing until the planned reactivation date. This avoids accidental cancellations.
Checking pricing before a new regional launch.
A dev asks their agent: 'What's the price for Product B in Germany?' The agent runs list_catalog_products to find the ID, then uses list_catalog_prices to retrieve the localized checkout and tax-inclusive definition for that region.
Preparing a list of high-risk accounts.
RevOps needs to audit all users whose plans are about to lapse. The agent runs list_subscriptions, filters by status (e.g., 'past_due'), and uses get_customer_details on the resulting IDs to pull the associated tax ID for compliance.
The Tradeoffs
Trying to get customer data in one API call.
A developer writes a single, massive query hoping to grab customer details, transaction history, and current subscriptions all at once. This fails because the underlying data model is too complex for one endpoint.
→
Instead, break it down: Start with get_customer_details to get the ID. Then, use that ID's context to run list_subscriptions (for status) and list_transactions (for history). It requires 2-3 calls, but each call is clean and reliable.
Assuming 'Active' means paid.
A support agent sees a subscription listed as 'Active' in the dashboard and assumes payment was just processed. They don't check the actual transaction records.
→
Always cross-reference status with transactions. Run get_subscription_details to confirm the billing cycle, then use list_transactions to verify that a recent successful payment actually occurred.
Confusing products and pricing definitions.
A developer tries to list all prices but only gets product names back. They miss the critical tax or localization information needed for billing logic.
→
Never rely on list_catalog_products alone. Always follow up by calling list_catalog_prices. That tool provides the necessary localized, tax-inclusive pricing definitions.
When It Fits, When It Doesn't
Use this server if your job involves reading or modifying billing state: checking payment status, pausing/canceling plans, auditing revenue ledgers, or verifying product pricing. You need it when operational visibility into Paddle’s core data is required.
Don't use this if you just need to know a customer's email address or their name—that requires a general CRM tool. Also, don't use it if your primary goal is running marketing campaigns; that needs a separate outreach platform. Stick to billing cycles and account records.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Paddle. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually checking payment status shouldn't require logging into three different dashboards.
Right now, finding out why a customer’s access lapsed is a multi-step pain. You jump to the CRM (to check their contact info). Then you switch to the billing portal (to find the subscription ID). Finally, you run reports or manually search transaction logs to see if the payment failed and why. It takes 10 clicks, five tabs open, and half an hour of copy-pasting IDs.
With this MCP server, your agent does it all in one prompt. You ask: 'Why did sub_id fail?' The agent automatically runs `get_subscription_details` to see the status, then calls `list_transactions` using that context to pull the failure record and the specific tax boundary applied at the time.
Paddle MCP Server gives you full control over billing actions.
You're no longer stuck waiting for a support agent with 'read access.' You can tell your agent to pause a subscription (`pause_subscription`) or cancel it outright (`cancel_subscription`) right from the chat interface, triggering the necessary system changes instantly. It’s immediate operational control.
This means you run compliance checks on demand. Need to validate that Product X is priced correctly in Brazil? Call `list_catalog_prices`. You get a clean, structured array of data—no more manual spreadsheet work or ambiguous screenshots.
Common Questions About Paddle MCP
How do I check if a customer's subscription status changed recently using list_transactions? +
You can use list_transactions and filter the results by type (e.g., 'cancellation') or date range. The transaction record will show whether the payment was for renewal, proration, or an adjustment.
Can I pause a subscription using the get_subscription_details tool? +
No. get_subscription_details only retrieves data; it's read-only. To change the status, you must use the dedicated pause_subscription tool.
What is the difference between list_customers and get_customer_details? +
list_customers gives you a raw array of IDs for all accounts. You need to run get_customer_details on each ID individually if you want specific information like tax boundaries.
Do I need the API key just for list_catalog_prices? +
No, you'll need your Paddle API Key for virtually every tool. It authenticates your agent to perform any billing action or data read from the platform.
When running list_transactions, what specific Paddle API scopes must my AI client have for full read access? +
Your agent needs 'read' scope permissions. This ensures your client can pull historical data without failing due to insufficient access rights. It covers viewing payment status, proration details, and ledger entries.
If I run list_catalog_products, how does the server help me get corresponding localized pricing using list_catalog_prices? +
You must call these tools in sequence. The agent first uses list_catalog_products to gather product IDs, and then passes those IDs to list_catalog_prices. This lets you link specific products to their exact tax-inclusive price points.
When calling list_subscriptions, what should my AI client do if the returned data set is extremely large or hits a rate limit? +
The server handles standard API pagination. Your agent must check for any next_page tokens in the response payload. This ensures you pull all subscription records and don't stop after hitting an artificial data cap.
Does get_transaction_details include specific, localized sales tax calculations from Paddle? +
Yes, it pulls detailed ledger entries that specify the exact jurisdiction and applicable tax rate for that transaction. This is critical for finance teams evaluating native transactional tax boundaries.
Can I cancel a customer subscription directly from chat? +
Yes. The agent leverages the cancel_subscription tool to stop recurring plans natively. You can instruct the agent to cancel it "immediately" or "at the next_billing_period" according to Paddle's API logical boundaries.
How do I fetch the exact localized checkout prices? +
The list_catalog_prices query extracts the complete Price definitions from your Paddle system. It details the billing frequency, currency boundaries, tax-inclusiveness flags, and item descriptions seamlessly.
Is Paddle Classic Supported or is this for Paddle Billing? +
This integration targets the modern Paddle Billing REST API which leverages robust structural objects (like Customers, Businesses, and Subscriptions) ensuring clean MoR tax boundaries and granular item mappings.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Amazon Selling Partner
E-commerce and marketplace orchestration — manage orders, FBA inventory, and catalogs via AI.
TaxJar
Connect your AI to TaxJar. Calculate sales tax dynamically, validate active nexus regions, and assess order tax liability natively from the terminal.
Bold
Automate payments via Bold Colombia — manage terminals, process transactions, generate payment links, and track settlements from any AI agent.
You might also like
Walmart Drop Ship Vendor
Exclusive 1P Supplier logistics server. Map DSV operations like Lag Times and physical supply nodes securely.
3Scribe
Automated audio and video transcription — create jobs, monitor progress, and retrieve text via AI.
Nhost
Manage Nhost authentication and storage — handle user sign-ins, registrations, profile management, and file uploads directly from any AI agent.