3,400+ MCP servers ready to use
Vinkius

Bring Recurring Billing
to Cursor

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

Cancel SubscriptionCreate CustomerCreate SubscriptionGet CustomerGet SubscriptionList AddonsList CustomersList InvoicesList PlansList Subscriptions

What is the Chargebee MCP Server?

Connect your Chargebee site to any AI agent and take full control of your billing workflows through natural conversation.

What you can do

  • Subscription Lifecycle — List active, trialing, or cancelled subscriptions and inspect their metadata
  • Customer Management — Query profiles, billing info, and contact details for any customer in your database
  • Invoicing & Payments — Track paid, pending, and overdue invoices to stay on top of your revenue
  • Product Catalog — List available plans and addons to understand your current offerings
  • Actionable Workflows — Create customers, start new subscriptions, or cancel existing ones programmatically

How it works

1. Subscribe to this server
2. Enter your Chargebee Site name and API Key
3. Start managing your recurring revenue from Claude, Cursor, or any MCP-compatible client

Built-in capabilities (10)

cancel_subscription

Cancel an existing subscription

create_customer

Create a new customer profile

create_subscription

Create a new subscription for a customer

get_customer

Get details for a specific customer

get_subscription

Get details for a specific subscription

list_addons

List available product addons

list_customers

List Chargebee customers

list_invoices

Can be filtered by status or customer. List Chargebee invoices

list_plans

List available product plans

list_subscriptions

Supports filtering via optional parameters. List Chargebee subscriptions

Why Cursor?

Cursor's Agent mode turns Chargebee into an in-editor superpower. Ask Cursor to generate code using live data from Chargebee and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

  • Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

  • Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

  • MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

  • VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

Chargebee in Cursor

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

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

Teams that connect Chargebee to Cursor 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 Chargebee in Cursor

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

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

Chargebee
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 Chargebee for Cursor

Every tool call from Cursor to the Chargebee 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 automatically list all active subscriptions for a site?

Yes! Use the list_subscriptions tool to retrieve all recorded subscriptions. You can then ask the agent to filter them by status if needed.

02

How do I fetch details for a specific customer?

Simply provide the Customer ID to the get_customer_details tool. It will return the full profile, including contact info and billing preferences.

03

Does this integration allow for creating new subscriptions?

Yes, you can use the create_subscription tool by providing the Customer ID and the Plan ID.

04

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

05

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

06

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

07

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

08

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

09

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.