Autumn MCP by usefulapi

io.usefulapi/autumn

MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.

Yes, your AI can use this right now.Answered a live MCP handshake in 176 ms with no sign-in needed and exposes 18 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://autumn.usefulapi.io/mcp

18 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
get_customerread-only

Fetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances). Autumn API: POST /v1/customers.get.

list_customersread-only

List/filter customers with cursor pagination. Autumn API: POST /v1/customers.list. Returns { list, next_cursor }.

checkread-only

READ-ONLY entitlement check: does a customer have access to (or enough balance of) a feature? Autumn API: POST /v1/balances.check. This tool never records usage — it does not expose send_event or lock.

list_invoicesread-only

List invoices with cursor pagination and optional filters. Autumn API: POST /v1/invoices.list. Returns { list, next_cursor }.

get_entityread-only

Fetch a single entity (e.g. a seat) belonging to a customer. Autumn API: POST /v1/entities.get.

list_entitiesread-only

List a customer's entities with cursor pagination and optional filters. Autumn API: POST /v1/entities.list. Returns { list, next_cursor }.

list_featuresread-only

List all features in the current environment. Autumn API: POST /v1/features.list. Returns { list }.

get_featureread-only

Fetch a single feature by id. Autumn API: POST /v1/features.get.

list_plansread-only

List all plans (products) in the current environment. Autumn API: POST /v1/plans.list. Returns { list }.

get_planread-only

Fetch a single plan by id (optionally a specific version). Autumn API: POST /v1/plans.get.

preview_attachread-only

Preview the cost/effect of attaching a plan to a customer WITHOUT charging or changing anything. Read-only. Autumn API: POST /v1/billing.preview_attach.

autumn_requestread-only

Power-user escape hatch: POST to any Autumn read/preview endpoint not wrapped by a dedicated tool. READ-ONLY — the path is validated to only allow .get / .list / .check / .preview_* actions; write actions are rejected. Autumn API: POST {path}.

get_or_create_customercan modify

MUTATES Autumn billing data — fetches a customer by id, creating them if they do not exist. Autumn API: POST /v1/customers.get_or_create.

update_customercan modify

MUTATES Autumn billing data — partially updates a customer. Only provided fields change. Autumn API: POST /v1/customers.update.

track_usagecan modify

MUTATES Autumn billing data — records a usage event (deducts/credits a feature balance). Provide EITHER feature_id OR event_name. Autumn API: POST /v1/balances.track.

attach_plancan modify

MUTATES Autumn billing data — attaches (subscribes) a plan to a customer; may create an invoice / return a payment URL. Autumn API: POST /v1/billing.attach. Returns { customer_id, invoice, payment_url, required_action }.

create_entitycan modify

MUTATES Autumn billing data — creates an entity (e.g. a seat) under a customer, tied to a feature. Autumn API: POST /v1/entities.create.

open_customer_portalcan modify

MUTATES Autumn billing data — creates a Stripe billing-portal session for a customer to manage their subscription. Autumn API: POST /v1/billing.open_customer_portal. Returns { customer_id, url }.

Alternatives in Finance & Payments

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”