3,400+ MCP servers ready to use
Vinkius

Bring Subscriptions
to Cline

Learn how to connect Recharge to Cline and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

Cancel SubscriptionGet CustomerGet OrderGet Subscription DetailsList Billing ChargesList CustomersList ProductsList Shipping AddressesList Subscription OrdersList SubscriptionsUpdate Subscription

What is the Recharge MCP Server?

Connect your Recharge account to any AI agent and simplify your subscription management and recurring billing workflows through natural conversation.

What you can do

  • Subscription Management — List all active and cancelled subscriptions, retrieve detailed metadata, and update parameters programmatically
  • Customer Database — Query your database of subscribers and retrieve detailed profile and billing info
  • Order Tracking — Monitor processed subscription orders and stay on top of your fulfillment pipeline
  • Financial Insights — Access processed charges and billing history to understand your recurring revenue
  • Direct Control — Modify subscription quantities and scheduled charge dates without manual dashboard navigation

How it works

1. Subscribe to this server
2. Enter your Recharge API Access Token from your store settings
3. Start managing your subscription commerce from Claude, Cursor, or any MCP-compatible client

Built-in capabilities (11)

cancel_subscription

Cancel a subscription

get_customer

Get details for a specific customer

get_order

Get details for a specific order

get_subscription_details

Get details for a specific subscription

list_billing_charges

List billing charges

list_customers

List Recharge customers

list_products

List all subscription products

list_shipping_addresses

List customer addresses

list_subscription_orders

List processed orders

list_subscriptions

List Recharge subscriptions

update_subscription

Update an existing subscription

Why Cline?

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Recharge tool calls without waiting for prompts between steps. Connect 11 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

  • Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

  • Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

  • Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

  • Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

See it in action

Recharge in Cline

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Recharge and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Recharge to Cline 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.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Recharge in Cline

The Recharge 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 11 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Cline 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.

Recharge
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

The Vinkius Advantage

How Vinkius secures Recharge for Cline

Every tool call from Cline to the Recharge MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I list all my active subscriptions using my AI agent?

Yes! Use the list_subscriptions tool to retrieve a comprehensive list of all active and cancelled subscriptions in your account.

02

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.

03

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.

04

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

05

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.