Exposing OpenAPI.json as a resource is the part that changes behaviour: response fields come from the specification rather than from the model's memory of what a billing API usually returns. Worth knowing before you wire it into anything customer-facing — this is an unofficial project, and the key you paste in is a live billing credential.
An unofficial server for Autumn's pricing API. Alongside the tools it exposes Autumn's OpenAPI specification as a resource, so the model can read the request and response shapes rather than guessing them, plus a prompt aimed at AI app builders such as Lovable, Bolt.new and v0.
- Create a customer, and fetch an existing one by id
- Read a customer's entitlements — what their plan actually allows
- Manage their invoices
- Generate a billing portal link to hand to that customer
- The bundled OpenAPI.json covers /attach, /entitled, /events, /customers, /customers/:id and /customers/:id/billing_portal
An Autumn API key, passed as `--apiKey` on the launch command. Bun is the runtime: clone the repository, `bun install`, then point your client at `bun run <path to index.ts>`. Smithery will write that configuration for you. Either the public or the secret key works, but some features are unavailable with the public key.
One command plus a key — npx -y @smithery/cli install @SirTenzin/autumn-mcp-server --client claude, then supply credentials