Stripe MCP Server

Provides a unified StripeAPI core class that wraps the official Stripe SDK and exposes payment operations through a framework-agnostic interface. Framework-specific integration layers (LangChain, OpenAI, MCP, CrewAI, Vercel AI SDK) adapt this core to each framework's tool calling convention without duplicating business logic. The architecture uses a consistent adapter pattern where each framework's StripeAgentToolkit class transforms core StripeAPI methods into framework-native tool definitions with proper schema validation and error handling.

Implements the MCP specification to expose Stripe operations as MCP tools that can be called by any MCP-compatible client (Claude, other AI agents, IDEs). The MCP toolkit adapter converts StripeAPI methods into MCP tool definitions with JSON schema validation, handles MCP protocol messages (requests/responses), and manages the bidirectional communication channel between MCP clients and the Stripe backend. Supports both stdio and HTTP transport modes for flexible deployment.

Enables agents to search Stripe's official documentation using semantic search (not keyword matching) to find relevant API documentation, guides, and examples. Agents can ask natural language questions like 'How do I handle 3D Secure payments?' and receive relevant documentation excerpts with links. Implemented via embeddings-based search over Stripe's documentation corpus, allowing agents to self-serve documentation lookups without hardcoded knowledge.

Provides identical functionality across TypeScript and Python with separate implementations that share the same API design and behavior. Both implementations wrap the official Stripe SDKs (stripe-node and stripe-python) and expose the same toolkit interfaces (MCP, LangChain, OpenAI, CrewAI, Vercel AI SDK). Enables developers to use the toolkit in their preferred language without learning different APIs or patterns.

Enables agents to operate on behalf of connected accounts (Stripe Connect) by passing account context through configuration or per-operation parameters. The toolkit automatically includes the Stripe-Account header in API requests to route operations to the specified connected account. Supports both standard and express connected accounts with proper permission validation. Agents can switch between accounts without reinitializing the toolkit.

Implements a system where agents can offer paid capabilities that require customers to complete a Stripe Checkout before accessing. Agents create checkout sessions for specific tools/features, and Stripe handles payment collection. After successful payment, agents can verify payment status and grant access to paid features. Integrates with the toolkit's permission system to gate paid operations behind payment verification.

Implements the Model Context Protocol (MCP) specification for Stripe operations, exposing all toolkit capabilities as MCP tools that can be discovered and invoked by MCP-compatible clients (Claude, custom agents, etc.). The MCP implementation follows the standard MCP tool format with JSON schemas for input validation and structured output, enabling seamless integration with any MCP-compatible client without framework-specific adapters. Tools are registered with the MCP server at startup and made available to clients through the standard MCP discovery mechanism.

Implements a declarative permission model where developers specify which Stripe operations are available to AI agents through configuration objects. The system validates tool access at initialization time and enforces permissions at runtime, preventing agents from calling restricted operations. Configuration can be set per-framework integration, allowing different agents to have different permission levels (e.g., read-only vs. write access). Permissions are checked before tool invocation, not after, preventing unauthorized operations from reaching the Stripe API.

Exposes Stripe customer operations through a unified interface that handles customer creation with metadata, listing with pagination and filtering, updating customer attributes (email, name, address, tax ID), and deletion. The implementation wraps Stripe SDK customer methods and normalizes responses across frameworks. Supports idempotency keys for safe retries, metadata attachment for custom data, and tax ID validation. Returns structured customer objects with all Stripe fields (id, email, created timestamp, balance, etc.).

Enables creation of payment intents with amount, currency, and payment method configuration, then tracks their status through the payment lifecycle (requires_payment_method → succeeded/canceled). Supports one-time and recurring payment intents, off-session payments, and confirmation with payment method details. Returns payment intent objects with status, client secret (for frontend integration), and error details. Handles idempotency for safe retries and supports metadata for agent-driven context.

Manages subscription creation with customer, price, and billing cycle configuration, then tracks subscription status through lifecycle (active → past_due → canceled). Supports immediate and future-dated subscriptions, trial periods, and billing interval customization. Handles subscription updates (price changes, pause, resume, cancel) and retrieves subscription details including current period dates, next billing date, and invoice history. Returns subscription objects with all status information and payment history.

Enables creation of invoices for customers with line items (products, amounts, descriptions), automatic or manual finalization, and payment tracking. Supports invoice retrieval by ID or customer, listing with filtering and pagination, and status tracking (draft → open → paid/uncollectible). Handles invoice finalization (moves to open state and sends to customer), payment recording, and void operations. Returns invoice objects with line items, amounts due, payment status, and customer details.

Implements usage-based billing by recording meter events (e.g., API calls, storage GB-hours) that Stripe aggregates and bills on the next billing cycle. Agents can submit meter events with customer ID, meter name, and quantity, and Stripe automatically calculates charges based on configured billing meter prices. Supports event deduplication via idempotency keys to prevent double-charging. Integrates with subscriptions to add usage charges on top of base subscription fees.

Enables creation of full and partial refunds for charges, with reason specification (duplicate, fraudulent, requested_by_customer, etc.) and metadata attachment. Tracks refund status through lifecycle (created → succeeded/failed). Supports dispute retrieval and evidence submission for chargeback handling. Returns refund objects with status, amount, reason, and charge details. Handles idempotency for safe retries and prevents duplicate refunds via idempotency keys.

Retrieves account balance information (available, pending, reserved amounts) and payout history with transaction details. Supports filtering payouts by status (paid, pending, failed) and date range. Returns balance objects with currency-specific amounts and payout objects with amounts, arrival dates, and transaction lists. Enables agents to monitor account financial health and troubleshoot payment processing issues.