npm stripekitstdioMITupdated 1mo ago
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.
¿Qué puedes hacer con stripekit?
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
Instalación
Añade stripekit a tu cliente. Elige el que uses.
claude mcp add stripekit -- npx -y stripekitcodex mcp add stripekit -- npx -y stripekitamp mcp add stripekit -- npx -y stripekit{
"mcpServers": {
"stripekit": {
"command": "npx",
"args": [
"-y",
"stripekit"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"stripekit": {
"command": "npx",
"args": [
"-y",
"stripekit"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"stripekit","command":"npx","args":["-y","stripekit"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"stripekit": {
"command": "npx",
"args": [
"-y",
"stripekit"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"stripekit": {
"command": "npx",
"args": [
"-y",
"stripekit"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"stripekit": {
"command": "npx",
"args": [
"-y",
"stripekit"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"stripekit": {
"type": "local",
"command": "npx",
"args": [
"-y",
"stripekit"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"stripekit": {
"command": {
"path": "npx",
"args": [
"-y",
"stripekit"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y stripekitRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Puntuación
39 / 100
Incompleta
- Documentación18/25
- Mantenimiento19/25
- Confianza13/20
- Capacidad0/15
- Instalación12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 24 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Historial de versiones
| Versiones | Publicada |
|---|---|
| 0.2.2Última | 7 ago 2026 |
| 0.2.1 | 15 jul 2026 |