Compatible with every major AI agent and IDE
What is the Recharge Alternative MCP Server?
Connect your Recharge account to any AI agent to streamline your subscription operations and customer management through natural conversation.
What you can do
- Customer Profiles — Create, retrieve, and update customer records, including credit summaries and delivery schedules.
- Subscription Management — Fetch detailed subscription data to track recurring orders and customer status.
- Address & Logistics — Manage shipping addresses, merge duplicate records, and update delivery locations.
- Operational Control — Skip future charges for specific addresses and manage child resources for customer accounts.
- Data Analysis — List and sort customers or addresses to generate reports on your subscription base.
How it works
- Subscribe to this server
- Enter your Recharge API Access Token
- Start managing your recurring revenue directly from Claude, Cursor, or any MCP-compatible client
Who is this for?
- E-commerce Managers — quickly check customer delivery schedules and subscription statuses without leaving your workflow.
- Support Teams — update shipping addresses or skip charges for customers instantly during a chat.
- Operations Leads — analyze customer lists and credit summaries to monitor business health.
Built-in capabilities (70)
Reactivate a cancelled subscription
Add tasks to an async batch
Apply a discount to a queued charge
Bulk manage plans for a product
Cancel a subscription
Update the associated address for a subscription
Clone an order for prepaid subscriptions
Create a new address
Create an async batch
Create a checkout
Create a customer
Create a metafield
Create a payment method
Create a plan
Create a product
Create a subscription
Create a webhook
Delay a prepaid order by one interval
Only works if there are no active subscriptions. Delete an address
Delete a customer and all child resources
Delete a metafield
Delete a scheduled order
Delete a payment method
Delete a plan
Delete a product
Delete a subscription
Delete a webhook
Retrieve an address
Retrieve an async batch
Retrieve a charge
Retrieve a checkout
Retrieve available shipping rates for a checkout
Retrieve a customer
Retrieve credit balance for a customer
Retrieve projected deliveries for a customer
Retrieve a metafield
Retrieve an order
Retrieve a payment method
Retrieve a plan
Retrieve a product
Retrieve a subscription
Retrieve a webhook
List addresses
List charges
List customers
List metafields
List orders
List plans
List subscriptions
Merge up to 10 source addresses into 1 target
Process an async batch
Manually process a queued charge
Process the checkout
Refund a processed charge
Remove a discount from a charge
Change the next charge date for a subscription
Skip a future charge for specific subscriptions on an address
Skip a charge
Test a webhook
Unskip a charge
Update an address
Update a checkout
Update a customer
Update a metafield
Update an order
Update a payment method
Update a plan
Update a product
Update a subscription
Update a webhook
Why CrewAI?
When paired with CrewAI, Recharge Alternative becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Recharge Alternative tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Recharge Alternative in CrewAI
Recharge Alternative and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Recharge Alternative to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Recharge Alternative in CrewAI
The Recharge Alternative 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. All 70 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Recharge Alternative for CrewAI
Every tool call from CrewAI to the Recharge Alternative MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see when a customer's next delivery is scheduled?
Yes! Use the get_customer_delivery_schedule tool with the Customer ID. It will return the projected delivery dates and associated items for that specific user.
Is it possible to skip a specific charge for a customer's address?
Absolutely. Use the skip_address_charges action by providing the Address ID and the subscription details in the payload to bypass the next scheduled payment.
How do I handle duplicate shipping addresses for a single customer?
You can use the merge_addresses tool. It allows you to merge up to 10 source addresses into a single target address, keeping your customer records clean.
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.
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.
Explore More MCP Servers
View all →
Open-Meteo Historical Weather
3 toolsUnlock 84 years of global weather history (1940–present): temperature, precipitation, wind, and snow data for any coordinate — the ultimate climate research companion.

SendGrid
12 toolsDeliver transactional and marketing emails at massive scale with industry-leading deliverability and real-time analytics.

Deel
10 toolsManage global contracts, team members, invoices, payments, time-off, and expenses — global HR for AI agents.

Medium
10 toolsPublish and manage content on Medium — create posts and manage publications directly from any AI agent.
