Autumn MCP Server

io.usefulapi/autumn

not responding

Autumn is listed as active in the registry but did not answer our last check. It exposes 18 tools. Last commit 1 Aug 2026.

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

Uptime history 42 hours of history · worst hour 0%

42 hours agonow

20.7%

Uptime 24h

19 of 92 checks

Tools

read from the server

173 ms

Response time

average over 24h

Stars

last commit 1 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add autumn --transport http https://autumn.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "autumn": {
      "url": "https://autumn.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.autumn]
url = "https://autumn.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "autumn": {
      "url": "https://autumn.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "autumn": {
      "url": "https://autumn.usefulapi.io/mcp"
    }
  }
}

Available tools 18

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

customer

get_customer

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

get_or_create_customer

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_customer

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

entity

create_entity

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

get_entity

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

attach

attach_plan

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 }.

autumn

autumn_request

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}.

check

check

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.

customers

list_customers

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

entities

list_entities

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

feature

get_feature

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

features

list_features

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

invoices

list_invoices

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

open

open_customer_portal

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 }.

plan

get_plan

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

plans

list_plans

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

preview

preview_attach

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.

track

track_usage

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.

Endpoints

URL	Transport	State	Latency	Checked
https://autumn.usefulapi.io/mcp	streamable-http	answering	48 ms	0 min ago

Autumn — questions

Answers built from our own checks of this server.

What can Autumn do?

It exposes 18 tools, read directly from the server on our last check. Among them: attach_plan, autumn_request, check, create_entity, get_customer, get_entity and 12 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Autumn mostly used for?

Its tools cluster around customer and entity. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Autumn working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 19 of 92 checks got a reply (20.7%), average response time 173 ms. The bar chart above shows every period we have measured.

The registry lists Autumn as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Autumn?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Autumn need an API key?

No. Autumn completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 18 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Autumn?

It answers our handshake in 173 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Autumn open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.