How to integrate Stripe MCP with Codex

Framework Integration Gradient
Stripe Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Stripe MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Stripe MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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.

Conclusion

You've successfully integrated Stripe with Codex using Composio's Rube MCP server. Now you can interact with Stripe directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Stripe operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Stripe operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

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 Codex?

Yes, you can. Codex 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
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
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.