Bring Subscriptions
to Pydantic AI
Learn how to connect Recharge to Pydantic AI 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 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 a subscription
Get details for a specific customer
Get details for a specific order
Get details for a specific subscription
List billing charges
List Recharge customers
List all subscription products
List customer addresses
List processed orders
List Recharge subscriptions
Update an existing subscription
Why Pydantic AI?
Pydantic AI validates every Recharge tool response against typed schemas, catching data inconsistencies at build time. Connect 11 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.
- —
Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application
- —
Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your Recharge integration code
- —
Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors
- —
Dependency injection system cleanly separates your Recharge connection logic from agent behavior for testable, maintainable code
Recharge in Pydantic AI
Recharge and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Recharge to Pydantic AI 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 Recharge in Pydantic AI
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 Pydantic AI 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 for Pydantic AI
Every tool call from Pydantic AI to the Recharge 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 active and cancelled subscriptions in your account.
How does Pydantic AI discover MCP tools?
Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.
Does Pydantic AI validate MCP tool responses?
Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.
Can I switch LLM providers without changing MCP code?
Absolutely. Pydantic AI abstracts the model layer. your Recharge MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.
MCPServerHTTP not found
Update: pip install --upgrade pydantic-ai