stripe-ops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRIPE_API_KEY | Yes | The Stripe API key used to authenticate requests. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_customerA | Busca un customer de Stripe por email o ID y devuelve su perfil con suscripciones activas |
| list_recent_chargesA | Lista los cargos recientes de un customer con monto, estado y motivo de fallo si aplica |
| find_duplicate_chargesA | Detecta posibles dobles cobros: cargos exitosos del mismo monto sobre el mismo customer dentro de una ventana de tiempo |
| revenue_summaryB | Resumen de ingresos de los últimos N días: total cobrado, reembolsado y tasa de fallo de cargos |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing charges, detecting duplicates, summarizing revenue, and fetching customer profiles. No overlap in functionality; an agent can easily select the right tool for the job.
All names use snake_case and are descriptive, but three follow a verb_noun pattern (list_, find_, get_) while revenue_summary is a noun-only phrase. Minor inconsistency, yet still predictable and readable.
Four tools is slightly on the lower side, but the set is tightly scoped to stripe operations monitoring. The count feels acceptable rather than overly thin for a focused utility.
The tools cover only read/analytics operations: listing charges, detecting duplicates, revenue summaries, and customer lookup. Missing obvious operational capabilities like creating refunds, retrieving charge details, or managing customers/subscriptions, leaving significant gaps for real-world ops.