LabscoMCP early access ↗
AStheTECHMCP SERVER

MewCP Stripe MCP

Look up Stripe customers, run charges, manage products and subscriptions — the key travels with the call, not the config.

by AStheTECH ↗Payments, Billing & SubscriptionsCommunity

LABSCO SUMMARY

Stripe's customer and billing surface, with the key supplied per call.

That per-call key is the design decision worth knowing about before you wire this in: nothing is authorized until you hand a key over, and swapping test for live is a change to the argument rather than to the server.

What it is

A server over Stripe's API covering customers, charges and payment intents, the product and price catalog, subscriptions with trials, and account balance.

What you get

  • Customers created, retrieved by ID, searched by email or name, and listed with cursor pagination
  • Customer records that include balance, delinquency status and metadata
  • Payments taken through charges and payment intents
  • Products and prices created and managed
  • Subscription billing, including trials
  • The account balance read in real time

Requirements

A Stripe API key, passed as an argument on each call rather than stored in the server's configuration — every tool takes api_key as a required input. Which key you pass therefore decides, call by call, whether you are touching test data or live money.

Setup effort

Add the hosted endpoint plus a key — paste it into your client, then supply credentials