Stripekit

io.github.rafaelcgPublished by GitHub account rafaelcgv0.2.2Updated Oct 24, 2026

Reconcile a declarative Stripe catalog and inspect your account — plan, push, pull, check.

VerifiedSTDIODesktop onlyDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Lets an assistant reconcile a declarative Stripe catalog against a live account and inspect it via plan, push, pull, and check tools.

What you can do
Stripekit exposes its reconciler as MCP tools: plan, push, pull, and check. Plan and push converge a Stripe account to a declarative stripe.config.ts covering products, prices, webhook endpoints, and the customer portal, treating prices as immutable and archiving rather than deleting. Pull reads the account state back, and check verifies keys, config validity, config-versus-account drift, and webhook/portal wiring. Commands accept --json and --yes for non-interactive use.
When to use it
Useful when an assistant needs to set up or keep a Stripe catalog in sync with a config file in a repository, or to audit drift between that config and the live account. It fits teams that manage Stripe products and prices as code and want an agent to run the reconciliation.
Requirements
Runs locally over stdio, installed from the npm package stripekit and started with npx. Requires Node.js and a Stripe account with API keys; the README mentions a test account for trying it out. No environment variables or headers are declared in the manifest.
Before you install
Push and pull act on a live Stripe account and can create or archive products, prices, webhook endpoints, and portal settings, so run against a test account first. Stripe API keys are needed but are not declared in the manifest, so confirm how they are supplied. The README also mentions a dev command that wraps stripe listen to capture a webhook signing secret.

Installation

In SourceWeft

  1. Open Stripekit 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

stripekit

[npm] [CI] [license] [docs]

The create-next-app of Stripe. One command takes an app from zero to working payments on your Stripe account: it provisions your catalog from a config file in your repo, and drops in correct-by-construction billing code you own. No hosted service. No revenue share. Nothing to depend on at runtime. Works identically whether a human or an agent runs it.

Documentation →

Repository layout

PathWhat it is
packages/stripekitThe stripekit npm package — CLI + config API.
examples/playgroundA scratch project to try stripekit against a Stripe test account.
docsThe VitePress documentation site.
DESIGN.mdThe MVP design: CLI surface, config schema, generated code, build order.

Status

Built and tested: stripekit init | plan | push | pull | dev | check | mcp.

  • Reconciler (plan / push / pull) — reconciles your Stripe account to a declarative stripe.config.ts (products, prices, webhook endpoint, customer portal), treating prices as immutable, archiving instead of deleting, and converging idempotently.
  • init — scaffolds stripe.config.ts plus correct-by-construction billing code (webhook handler, state sync, checkout/portal routes) into a Next.js App Router app.
  • dev — wraps stripe listen to forward webhooks locally and capture the signing secret.
  • check — a doctor that verifies keys, config validity, config-vs-account drift, and webhook/portal wiring.

There's also a VitePress docs site with a landing page — run pnpm docs:dev. Roadmap (see DESIGN.md): init support beyond Next.js and richer catalog features.

See the package README for usage.

For AI agents

stripekit is built to be driven by agents, not just humans:

  • llms.txt and llms-full.txt — the docs as clean markdown for LLM context.
  • SKILL.md — point your coding agent at this and it can set stripekit up for you.
  • stripekit mcp — an MCP server exposing plan/push/pull/check as tools an agent can call.
  • Every command accepts --json and --yes for deterministic, non-interactive use.

Install the MCP server one-click in Cursor:

[Add to Cursor]

…or in Claude Code as a plugin:

bash
/plugin marketplace add rafaelcg/stripekit/plugin install stripekit@stripekit-marketplace

See the MCP docs for other clients (Claude Desktop, .cursor/mcp.json, claude mcp add).

Working on stripekit? See AGENTS.md.

Develop

bash
pnpm installpnpm -C packages/stripekit build      # bundle CLI + typespnpm -C packages/stripekit test       # unit + integration testspnpm -C packages/stripekit typecheck

License

MIT

Source: README.md at commit fc3372d

Tools

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

Version history

1
  1. v0.2.2LatestSep 16, 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