Stripe

io.github.mcp-dirPublished by GitHub account mcp-dirv0.1.0Updated Oct 24, 2026

Payments and billing on Stripe with the full official REST API (api.stripe.com), covers the entire d

The publisher's own server: Stripe

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Hosted MCP endpoint that gives an assistant read-only access to a Stripe account's payments, billing and related objects through Stripe's official REST API.

What you can do
  • Search, describe and invoke catalog tools through a single search_tools entrypoint
  • Query Stripe account data such as balance, payment intents, customers, subscriptions, invoices, refunds, disputes, products, prices, coupons, payment links, checkout, payouts, tax, radar, issuing and connect
  • Check connection status and pending provider connections, and get connect or per-install URLs when credentials are missing
  • Inspect toolkit state: installed MCPs, their connection status, connected accounts and exposed tool counts
  • Browse the mcp.ai marketplace to find MCPs by intent
  • Show platform and adapter versions, and report bugs or feedback
When to use it
Useful when you want an assistant to look up or report on Stripe payment and billing data, such as available balance, recent payment intents or customer records, without building your own API integration.
Requirements
A remote MCP-over-HTTP endpoint; no local package. A Stripe account secret API key, ideally a restricted key with only the needed scopes; if the key is IP-restricted, the fixed outbound IP must be allowed. Authentication is done by logging in via browser and passing the access token as an Authorization Bearer header, or pasting it for a session-only login. Any MCP client that supports MCP over HTTP.
Before you install
You must supply a Stripe secret API key, which grants access to your account; prefer a restricted key with minimal scopes. The README states the tools are read-only, but the description also mentions operations, so verify before relying on that. Data returned by the tools is sent to whichever LLM host you use, a third party outside the provider's control. The hosted server itself is proprietary, not open source.

Installation

In SourceWeft

  1. Open Stripe in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mcp-dir%2Fstripe-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "stripe": {
      "type": "http",
      "url": "https://api.mcp.ai/p_stripe"
    }
  }
}

README

Stripe

Stripe para Claude, ChatGPT e agentes de IA

Pagamentos e billing no Stripe com a API REST oficial completa (api.stripe.com), cobre toda a documentação: clientes, cobranças, payment intents, assinaturas, faturas, reembolsos, disputas, produtos, preços, cupons, payment links, checkout, repasses, payouts, saldo, métodos de pagamento, tax, radar, issuing, connect e mais. Consulta e operação. Autenticação por chave secreta da conta Stripe (em Developers, API keys). Recomendamos uma chave restrita (rk_) com só os escopos necessários. Se restringir a chave por IP, libere o IP fixo de saída 3.94.44.196.

  • 📊 1 ferramenta
  • 🔒 Somente leitura
  • 💬 Funciona com qualquer cliente MCP: Claude Desktop, Cursor, VS Code, Cline, Continue
  • 🔑 Login via magic-link (sem senha)

English version · Documentação completa · Skill pra agentes


Instalar em 1 clique

Claude (Web e Desktop)

A Anthropic unificou a instalação de MCPs em claude.ai/customize/connectors. O mesmo link serve pra Claude Web e Claude Desktop (basta estar logado):

➕ Abrir no Claude e conectar

Manual (se o deeplink não abrir): claude.ai/customize/connectors → + → Adicionar conector personalizado → cole Nome Stripe e URL https://api.mcp.ai/p_stripe.

Cursor

➕ Instalar Stripe no Cursor

VS Code (Copilot Chat)

➕ Instalar Stripe no VS Code

ChatGPT, Manus, OpenClaw e mais 40+ clientes

Funciona em qualquer cliente MCP que suporte MCP over HTTP. A URL do servidor é sempre:

https://api.mcp.ai/p_stripe

Detalhes por cliente: INSTALL.md.


Exemplos de uso

Qual o saldo disponível na minha conta Stripe?Liste os últimos 10 pagamentos (payment intents)Crie um cliente com email [email protected]

1 ferramenta disponível

ToolDescrição
search_toolsSingle entrypoint for MCP catalog.

Detalhe de cada tool: docs/ferramentas.md


Preços

Grátis.


Privacidade & LGPD

  • Somente leitura, nenhuma ferramenta altera dados na origem.
  • Sub-processadores: Stripe, o LLM host que você escolher (Claude, ChatGPT, Cursor, agente próprio). Lista completa em docs/privacidade-lgpd.md.
  • Os dados retornados pelas tools são enviados ao LLM host que você escolher, sub-processador fora do nosso controle. Recomendamos planos com opt-out de treinamento.

Perguntas frequentes

O servidor é open source? O servidor é proprietário (hosted). Este repositório é o wrapper público com manifestos, docs e skills — tudo MIT.

Posso usar com agente próprio (não Claude/Cursor)? Sim — qualquer cliente que suporte MCP over HTTP. URL: https://api.mcp.ai/p_stripe.


Suporte


Licença

MIT — veja LICENSE. O servidor MCP em api.mcp.ai/p_stripe é proprietário (hosted); este repositório (manifestos, docs, skills) é MIT.

Source: README.md at commit 6b10ed2

Tools

7

search_tools

Search Tools

Single entrypoint for MCP catalog. action=search returns available tools ordered by relevance. action=describe returns tool schema. action=invoke executes a tool by ID.

Parametersqueryactionqueriestool_idargumentsmin_scoreforce_reindex

show_version

Show Version

Show the current MCP platform and adapter versions.

Takes no parameters.

report_bug

Report Bug

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Parameterscontextmessagerequiredconversation

connect

Connection Status

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Takes no parameters.

authenticate

Authenticate

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

Parameterstoken

toolkit_info

Toolkit Info

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Takes no parameters.

marketplace

Marketplace

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

Parameterslimitqueryactionmcp_idmessagetool_idargumentsimmediatetier_slugprompt_bodyprompt_slugprompt_tool+11 more

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Stripe integrations