Stripe Billing

io.github.theluckystrikePublished by GitHub account theluckystrikev1.0.1Updated Oct 24, 2026

Read your Stripe billing data from AI chat: balances, invoices, subscriptions. Read-only.

The publisher's own server: Stripe

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

A local Stripe billing server that lets an assistant read your account balance and create real, shareable Stripe payment links from chat.

What you can do
Read your live Stripe account balance, including available and pending amounts, straight from the balance endpoint in chat. Create a real, shareable Stripe payment link for a named price ID, optionally with a quantity. Report plainly when the required Stripe key is missing instead of returning mock data.
When to use it
Useful when you want quick answers about your Stripe balance or need a shareable payment link for an existing price without opening the Stripe dashboard. Suited to small, frequent billing questions during a work session.
Requirements
Runs as a local process on your machine, started via npx from the GitHub package. Needs a Stripe secret key supplied through the STRIPE_SECRET_KEY environment variable, and network access to the Stripe REST API.
Before you install
The server asks for your Stripe secret key, which grants access to your live account; the README recommends a restricted key limited to balance read and payment link write rather than a full secret. Creating a payment link writes to your live Stripe account and produces a shareable, payable link, so review price IDs and quantities before use.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MCP Stripe Billing — check your Stripe balance and build payment links from chat

Give Claude (or any MCP client) two working Stripe tools: stripe_balance reads your live account balance, and stripe_payment_link creates a real Stripe payment link for a price you name. Direct Stripe REST calls from your machine with your own STRIPE_SECRET_KEY — no dashboard round-trip for the two questions you actually ask most.

Why a Stripe server

Most Stripe questions in a work session are small ones: "what's my balance?", "make me a payment link for that $19 price". Opening the dashboard for each is friction. With this server connected, the answer or the link arrives in the conversation — and the link is immediately shareable.

What it does

  • stripe_balance — available and pending balance across your Stripe account, straight from /v1/balance.
  • stripe_payment_link — given a price ID (and optionally a quantity), creates a shareable https://buy.stripe.com/... link via /v1/payment_links.
  • Without STRIPE_SECRET_KEY set, both tools say so plainly instead of pretending — no silent mock data.

Install

json
{  "mcpServers": {    "mcp-stripe-billing": {      "command": "npx",      "args": ["-y", "github:theluckystrike/mcp-stripe-billing"],      "env": { "STRIPE_SECRET_KEY": "sk_live_..." }    }  }}

Use a restricted key (balance read + payment links write) rather than your full secret.

Try it

  • "What's my Stripe balance right now?"
  • "Create a payment link for price_abc123, quantity 1."

Part of the luckystrike MCP suite

Free, part of the luckystrike MCP suite — productivity & finance servers that turn AI chat into working documents and calculations. Listing in the official MCP Registry.

Docs (GitMCP)

Live docs endpoint: https://gitmcp.io/theluckystrike/mcp-stripe-billing

Source: servers/stripe-billing/README.md at commit 1bd9d69

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.1LatestOct 9, 2026
  2. v1.0.0Sep 27, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Stripe integrations