How to integrate Stripe MCP with OpenCode

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Stripe logo
OpenCode logo
divider

How to integrate Stripe MCP with OpenCode

This guide explains how to connect Stripe MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.

There are two ways to set this up:

Also integrate Stripe with

Why use Composio?

Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:

  • Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the LLM context to keep conversations lean.

Connect Stripe with OpenCode

Option 1: Using Composio CLI

1. Install Composio CLI

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login, you will be redirected to the sign-in page. Finish the flow and you are all set.

Composio CLI authorization screen

2. Authorize Stripe

Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:

  1. Launch OpenCode.
  2. Prompt it to "Authenticate with Stripe Composio".
  3. Complete the authentication and authorization flow, and your Stripe integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Stripe to OpenCode by adding Composio as an MCP server through the OpenCode CLI.

1. Add the Composio MCP server

bash
opencode mcp add

This launches an interactive prompt.

2. Fill in the fields

FieldValue
Namecomposio
Typeremote
URLhttps://connect.composio.dev/mcp
Require OAuthYes
Have client IDNo
OpenCode MCP server interactive prompt for Composio

Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.

Open your global OpenCode config:

bash
open ~/.config/opencode/opencode.json

Add this under the mcp key and save the file.

bash
{
  "mcp": {
    "composio": {
      "type": "remote",
      "url": "https://connect.composio.dev/mcp",
      "enabled": true
    }
  }
}

3. Authenticate

Authenticate the Composio MCP server you just added:

bash
opencode mcp auth composio

This opens a browser session. Authorize Composio and you are done.

Composio browser authorization for OpenCode MCP

4. Verify installation

bash
opencode mcp list

5. Connect Stripe with OpenCode

Now, in the chat, ask the agent to connect to Stripe or give it any Stripe-related task.

For example, ask it to:

  • "Create a new Stripe customer with email"
  • "Generate a draft invoice for recent orders"
  • "Cancel an active subscription at period end"

It will prompt you to authenticate and authorize access to Stripe.

That is it. Composio tools are now available in OpenCode, and your Stripe account is ready to use.

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.

Way Forward

Now that Stripe is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

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

Yes, you can. OpenCode 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.