How to integrate Stripe MCP with Claude Agent SDK

Framework Integration Gradient
Stripe Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Stripe to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Stripe agent that can create a new stripe customer with email, generate a draft invoice for recent orders, cancel an active subscription at period end, issue a refund for a specific payment through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Stripe account through Composio's Stripe MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Stripe
  • Configure an AI agent that can use Stripe as a tool
  • Run a live chat session where you can ask the agent to perform Stripe operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Stripe MCP server, and what's possible with it?

The Stripe MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Stripe account. It provides structured and secure access to your payments platform, so your agent can perform actions like creating customers, managing subscriptions, issuing refunds, and generating invoices on your behalf.

  • Automated customer management: Effortlessly create, update, or delete Stripe customers—enabling streamlined onboarding and account maintenance through your agent.
  • Subscription and recurring billing automation: Have your agent create, configure, or cancel subscriptions, supporting trials, discounts, and advanced billing scenarios with ease.
  • Smart payment and refund processing: Allow your agent to initiate payment intents, confirm transactions, and issue full or partial refunds as needed, all through secure APIs.
  • Seamless invoice and price creation: Generate draft invoices for customers, create new products, and set up pricing structures—saving you time on manual billing tasks.
  • Advanced product and pricing management: Let your agent create new products and prices, helping you roll out new offerings or adjust monetization strategies with just a prompt.

Supported Tools & Triggers

Tools
Triggers
Cancel subscriptionCancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Confirm payment intentConfirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Create CustomerCreates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Create an invoiceCreates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Create payment intentCreates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Create a priceCreates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
Create productCreates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Create RefundCreates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Create subscriptionCreates a new, highly configurable subscription for an existing stripe customer, supporting multiple items, trials, discounts, and various billing/payment options.
Delete customerPermanently deletes an existing stripe customer; this irreversible action also cancels their active subscriptions and removes all associated data.
List ChargesRetrieves a list of stripe charges with filtering and pagination; use valid cursor ids from previous responses for pagination, and note that charges are typically returned in reverse chronological order.
List Stripe couponsRetrieves a list of discount coupons from a stripe account, supporting pagination via `limit`, `starting after`, and `ending before`.
List customer payment methodsRetrieves a list of payment methods for a given customer, supporting type filtering and pagination.
List customersRetrieves a list of stripe customers, with options to filter by email, creation date, or test clock, and support for pagination.
List InvoicesRetrieves a list of stripe invoices, filterable by various criteria and paginatable using invoice id cursors obtained from previous responses.
List payment intentsRetrieves a list of stripe paymentintents, optionally filtered and paginated using paymentintent ids as cursors.
List payment linksRetrieves a list of payment links from stripe, sorted by creation date in descending order by default.
List productsRetrieves a list of stripe products, with optional filtering and pagination; `starting after`/`ending before` cursors must be valid product ids from a previous response.
List RefundsLists stripe refunds, sorted by creation date descending (newest first), with optional filtering by charge or payment intent and pagination support.
List Stripe shipping ratesRetrieves a list of stripe shipping rates, filterable by active status, creation date, and currency; useful for managing or displaying shipping options.
List subscriptionsRetrieves a list of stripe subscriptions, optionally filtered by various criteria such as customer, price, status, collection method, and date ranges, with support for pagination.
List tax codesRetrieves a paginated list of globally available, predefined stripe tax codes used for classifying products and services in stripe tax.
List tax ratesRetrieves a list of tax rates, which are returned sorted by creation date in descending order.
Retrieve BalanceRetrieves the complete current balance details for the connected stripe account.
Retrieve Charge DetailsRetrieves full details for an existing stripe charge using its unique id.
Retrieve customerRetrieves detailed information for an existing stripe customer using their unique customer id.
Retrieve payment intentRetrieves a paymentintent by its id; `client secret` is required if a publishable api key is used.
Retrieve a refundRetrieves details for an existing stripe refund using its unique `refund id`.
Retrieve subscriptionRetrieves detailed information for an existing stripe subscription using its unique id.
Search Stripe customersRetrieves a list of stripe customers matching a search query that adheres to stripe's search query language.
Update CustomerUpdates an existing stripe customer, identified by customer id, with only the provided details; unspecified fields remain unchanged.
Update Payment IntentUpdates a stripe paymentintent with new values for specified parameters; note that if `currency` is updated, `amount` might also be required, and certain updates (e.
Update SubscriptionUpdates an existing, non-canceled stripe subscription by its id, ensuring all referenced entity ids (e.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Stripe account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Stripe functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Stripe
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["stripe"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Stripe
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Stripe tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Stripe
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Stripe and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Stripe
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["stripe"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Stripe tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Stripe through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Stripe MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Stripe MCP?

With a standalone Stripe MCP server, the agents and LLMs can only access a fixed set of Stripe tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Stripe and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Stripe tools.

Can I manage the permissions and scopes for Stripe while using Tool Router?

Yes, absolutely. You can configure which Stripe scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Stripe data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.