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.

Paddle MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Paddle
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Paddle through Vinkius, pass the Edge URL in the `mcps` parameter and every Paddle tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Paddle Specialist",
    goal="Help users interact with Paddle effectively",
    backstory=(
        "You are an expert at leveraging Paddle tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Paddle "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Paddle MCP Server

Bring the Paddle Billing API directly into your AI workflows. Acting as your Merchant of Record (MoR) interface, this integration allows your agent to seamlessly query customer billing states, manage SaaS subscriptions, retrieve invoice ledgers, and pause actively churning plans natively.

When paired with CrewAI, Paddle becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Paddle tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Customers & Billing Details — List and search all CRM accounts managed by Paddle and extract their exact tax identification boundaries
Subscription Lifecycle — Inspect active or past-due subscriptions, cancel recurring flows dynamically, or pause an active schedule right from chat
Transactions & Ledgering — Fetch bulk atomic transactions matching exact one-off payments, prorations, and historical subscription renewals
Catalog Explorer — List your products and retrieve localized checkout prices and native tax-inclusive pricing definitions

The Paddle MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Paddle to CrewAI via MCP

Follow these steps to integrate the Paddle MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Paddle

Why Use CrewAI with the Paddle MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Paddle through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Paddle + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Paddle MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Paddle for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Paddle, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Paddle tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Paddle against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Paddle MCP Tools for CrewAI (10)

These 10 tools become available when you connect Paddle to CrewAI via MCP:

cancel_subscription

Can be set to effective immediately or at the end of the current billing period. Cancel an active subscription

get_customer_details

Get details for a specific customer

get_subscription_details

Get details for a specific subscription

get_transaction_details

Get details for a specific transaction

list_catalog_prices

List all pricing definitions

list_catalog_products

List all products

list_customers

List all customers in Paddle

list_subscriptions

List all subscriptions

list_transactions

List all billing transactions

pause_subscription

Pause an active subscription

Example Prompts for Paddle in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Paddle immediately.

"Find the subscription details for sub_01h9z2..."

"List our most recent revenue transactions on Paddle."

"Cancel subscription sub_active123 at the end of the billing cycle."

Troubleshooting Paddle MCP Server with CrewAI

Common issues when connecting Paddle to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Paddle + CrewAI FAQ

Common questions about integrating Paddle MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.