Stripe Legacy MCP Server for CursorGive Cursor instant access to 11 tools to Create Charge, Create Customer, Create Refund, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The Stripe Legacy app connector for Cursor is a standout in the Industry Titans category — giving your AI agent 11 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Stripe Legacy and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"stripe-legacy": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About Stripe Legacy MCP Server
Connect your Stripe account to any AI agent to automate your basic payment processing and customer management. This integration provides a streamlined interface for the core Stripe v1 API, allowing you to monitor charges, create payment tokens, and track account balances through natural conversation.
Cursor's Agent mode turns Stripe Legacy into an in-editor superpower. Ask Cursor to generate code using live data from Stripe Legacy and it fetches, processes, and writes. all in a single agentic loop. 11 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Payment Orchestration — List recent charges and retrieve detailed metadata for specific transactions programmatically.
- Customer Management — Access and monitor your customer database to keep your client records synchronized directly from the AI interface.
- Charge Lifecycle Control — Create new charges and manage payment tokens using simple AI commands to facilitate transactions.
- Financial Monitoring — Retrieve your real-time Stripe account balance to ensure your business liquidity is always visible.
- Operational Oversight — Get instant summaries of recent payment activity and customer metadata via natural language.
The Stripe Legacy MCP Server exposes 11 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 11 Stripe Legacy tools available for Cursor
When Cursor connects to Stripe Legacy through Vinkius, your AI agent gets direct access to every tool listed below — spanning payment-gateway, transaction-management, financial-data, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Pass data as a JSON string. Create a new charge
Create a new Stripe customer
Create a refund for a charge
Pass data as a JSON string. Create a single-use token
Check account balance
Get charge details
Get details for a specific customer
List all Stripe charges
List all Stripe customers
List all invoices
List all active subscriptions
Connect Stripe Legacy to Cursor via MCP
Follow these steps to wire Stripe Legacy into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Stripe Legacy
Why Use Cursor with the Stripe Legacy MCP Server
Cursor AI Code Editor provides unique advantages when paired with Stripe Legacy through the Model Context Protocol.
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
Stripe Legacy + Cursor Use Cases
Practical scenarios where Cursor combined with the Stripe Legacy MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for Stripe Legacy in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Stripe Legacy immediately.
"Check my current Stripe account balance."
"Show me all charges from the past 24 hours with their status and customer details."
"Get the current account balance and recent payout schedule."
Troubleshooting Stripe Legacy MCP Server with Cursor
Common issues when connecting Stripe Legacy to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Stripe Legacy + Cursor FAQ
Common questions about integrating Stripe Legacy MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
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.