io.github.rafaelcg/stripekit
Reconcile a declarative Stripe catalog and inspect your account — plan, push, pull, check.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
stripekitclaude mcp add stripekit -- npx -y stripekit@0.2.2 mcp
{
"mcpServers": {
"stripekit": {
"command": "npx",
"args": [
"-y",
"stripekit@0.2.2",
"mcp"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
stripekit
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.
Repository layout
| Path | What it is |
|---|---|
packages/stripekit | The stripekit npm package — CLI + config API. |
examples/playground | A scratch project to try stripekit against a Stripe test account. |
docs | The VitePress documentation site. |
DESIGN.md | The 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 declarativestripe.config.ts(products, prices, webhook endpoint, customer portal), treating prices as immutable, archiving instead of deleting, and converging idempotently. init— scaffoldsstripe.config.tsplus correct-by-construction billing code (webhook handler, state sync, checkout/portal routes) into a Next.js App Router app.dev— wrapsstripe listento 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 exposingplan/push/pull/checkas tools an agent can call.- Every command accepts
--jsonand--yesfor deterministic, non-interactive use.
Install the MCP server one-click in Cursor:
…or in Claude Code as a plugin:
/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
pnpm install
pnpm -C packages/stripekit build # bundle CLI + types
pnpm -C packages/stripekit test # unit + integration tests
pnpm -C packages/stripekit typecheck
License
MIT
Frequently asked questions
What is io.github.rafaelcg/stripekit?
Reconcile a declarative Stripe catalog and inspect your account — plan, push, pull, check.
How do I install io.github.rafaelcg/stripekit?
It runs on your machine. In Claude Code: claude mcp add stripekit -- npx -y stripekit@0.2.2 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.rafaelcg/stripekit need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.rafaelcg/stripekit open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.rafaelcg/stripekit?
It is published by rafaelcg. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.