Bring Subscriptions
to LlamaIndex
Learn how to connect Recurly to LlamaIndex and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Recurly MCP Server?
Connect your Recurly account to any AI agent and simplify your subscription billing, revenue management, and customer orchestration through natural conversation.
What you can do
- Subscription Management — List all active and expired product subscriptions, and retrieve detailed metadata and plan info
- Account Coordination — Query your database of billing accounts and retrieve detailed metadata, balance, and status
- Billing Tracking — Access a history of generated invoices and monitor their payment status directly from your agent
- Plan catalog — Query available subscription plans and their pricing to choose the right context for each interaction
- Direct Enrollment — Register new customer accounts programmatically directly from your agent
How it works
1. Subscribe to this server
2. Enter your Recurly API v3 Key from your account settings
3. Start managing your subscription commerce from Claude, Cursor, or any MCP-compatible client
Built-in capabilities (11)
Register a new account
Get details for a specific account
Get details for a specific invoice
Get revenue export dates
Get details for a specific subscription
List billing accounts
List invoices
List all active coupons
List available plans
List Recurly subscriptions
List recent transactions
Why LlamaIndex?
LlamaIndex agents combine Recurly tool responses with indexed documents for comprehensive, grounded answers. Connect 11 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Recurly tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Recurly tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Recurly, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Recurly tools were called, what data was returned, and how it influenced the final answer
Recurly in LlamaIndex
Recurly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Recurly to LlamaIndex 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 | 3,400+ 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 Recurly in LlamaIndex
The Recurly 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 LlamaIndex 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
Recurly for LlamaIndex
Every tool call from LlamaIndex to the Recurly MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I list all my active subscriptions using my AI agent?
Yes! Use the list_subscriptions tool to retrieve a comprehensive list of all subscriptions registered in your Recurly account.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Recurly tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp