How do I find my Subdomain and API Key?

Your subdomain is the first part of your Recurly portal URL (e.g., if you log in at `myproject.recurly.com`, your subdomain is `myproject`). To get your API Key, navigate inside Recurly to Integrations > API Credentials and generate or copy your 'Private API Key'.

Can it accidentally charge my customers?

While the server can manage subscriptions (e.g., setting up a customer with a plan), it strictly follows the billing logic predefined in your Recurly catalog settings. It doesn't bypass credit card validation or execute arbitrary charges directly without a plan context.

Does cancelling a subscription remove the account entirely?

No, using `cancel_subscription` stops future renewals for that specific plan item instance. The underlying user billing account remains intact and can hold other valid subscriptions or past invoices.

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

Name: Recurly
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Recurly through Vinkius, pass the Edge URL in the `mcps` parameter and every Recurly 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="Recurly Specialist",
    goal="Help users interact with Recurly effectively",
    backstory=(
        "You are an expert at leveraging Recurly 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 Recurly "
        "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 Recurly MCP Server

Connect your Recurly subscription billing and management platform securely to your conversational AI agent. Activating this integration transforms your AI into a dynamic revenue operations assistant, giving it the autonomy to look up accounts, adjust active subscription states, and analyze invoice pipelines directly from the terminal.

When paired with CrewAI, Recurly becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Recurly 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

Account Management — Quickly list your customer directory, view detailed billing profiles, or instantly create a new account mapping without opening the vendor console.
Subscription Operations — Easily search and read subscription lifecycle states, enroll users in fresh catalog plans, un-cancel previous subscriptions, or permanently cancel an ongoing billing mandate.
Invoice & Plan Catalogs — Retrieve the list of historical generated invoices to verify successful automated payments or pull all active billing models (Catalog Plans) to review available products.

The Recurly 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 Recurly to CrewAI via MCP

Follow these steps to integrate the Recurly 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 Recurly

Why Use CrewAI with the Recurly MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Recurly 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

Recurly + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Recurly 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 Recurly, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Recurly 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 Recurly against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Recurly MCP Tools for CrewAI (10)

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

cancel_subscription

This action is irreversible. Cancels an active subscription

create_account

Specify code, email, and name. Creates a new customer account

create_subscription

Creates a new subscription for an account

get_account_details

Retrieves details for a specific customer account

get_subscription_details

Retrieves details for a specific subscription

list_accounts

Lists all customer accounts in Recurly

list_catalog_plans

Lists all available subscription plans in the product catalog

list_invoices

Lists all generated invoices

list_subscriptions

Lists all subscriptions managed by Recurly

reactivate_subscription

Reactivates a previously cancelled or expired subscription

Example Prompts for Recurly in CrewAI

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

"List the last 5 invoices generated in our account."

"Cancel the subscription with ID 'sub_39xjd82kw0'."

"Retrieve the billing details for account code 'cus_alpha_92'."

Troubleshooting Recurly MCP Server with CrewAI

Common issues when connecting Recurly 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.

Recurly + CrewAI FAQ

Common questions about integrating Recurly 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.