Skip to main content
Glama
Sign In

Stripe MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted Stripe MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/stripe-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation3/5

query_data and execute_action are nominally split into read vs. write, but their descriptions are near-verbatim boilerplate ('Step 3 (FINAL) of workflow' with identical required preamble), so an agent must infer the boundary from the tool name alone. prompts_menu and query_contexts also share a duplicated 'list menu then fetch details' pattern, and query_contexts admits request='available_actions' is redundant with the accounts response. The set is workable but the boundaries are softer than they should be.

Naming Consistency3/5

query_contexts, query_data, and execute_action follow a verb_noun pattern, but prompts_menu inverts to noun_noun and breaks the verb-first convention. The three query/execute names also blur the shared 'query' prefix across two tools with different targets.

Tool Count4/5

Four tools is lean but defensible for a generic meta-tool design where one action executor and one data query cover the entire Stripe surface via available_actions. No tool is clearly dead weight, though the set sits at the thin end of the acceptable range.

Completeness3/5

Read (query_data) and write (execute_action) paths plus prompt discovery are covered via the generic action catalog, so core lifecycle is reachable. However there is no dry-run/validation step, no error-recovery or pagination guidance, and action discovery is only reachable as a sub-request rather than a first-class operation, leaving agents dependent on a rigid two-step preamble.

Available Tools

4 tools
execute_actionStripe Execute ActionA
Destructive
Inspect

Execute Stripe action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

Inputs: body (required). Returns: object

prompts_menuStripe PromptsA
Read-only
Inspect

Browse the Stripe prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsStripe Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe Stripe data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, other source metadata, AND available_actions (all tables you can query).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataStripe Data QueryB
Read-only
Inspect

Query Stripe data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • MCP Stripe Finance

      phanhuycuong33-alt
      A
      license
      Not graded
      quality
      C
      maintenance
      Production-grade MCP server for Stripe financial operations, enabling AI assistants to manage payments, customers, subscriptions, invoices, products, prices, refunds, and balance checks.
      MIT

    • saas-brain-mcp

      Mohd16kaif
      F
      license
      Not graded
      quality
      D
      maintenance
      Open-source MCP server for Claude AI that connects Stripe and Supabase to enable natural language SaaS analytics, including churn analysis, subscription tracking, and revenue insights.
      -

    • razorpay-mcp

      indiamcp
      A
      license
      B
      quality
      D
      maintenance
      An MCP (Model Context Protocol) server that connects AI assistants like Claude directly to your Razorpay account.
      14
      41 npm
      1
      MIT
    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources