Autumn MCP by usefulapi
by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi
MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.
18 tools: 6 can delete or cancel things, 1 change things and 11 only read.
Scanned Oct 21, 2026
- Deletes or cancels6Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things1Claude Code: ask: see these tools
- Only reads11Claude Code: allow: see these tools
2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http autumn https://autumn.usefulapi.io/mcpFindings
Matches of fixed checks, with the text they matched.
- Warnautumn_request
The server marks "autumn_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "autumn_request" says "request": a word for a change.
The server marks "get_or_create_customer" destructive (destructiveHint: true), and its name says "get", a word for reading.
What this check looks forMatched text
annotations: {"destructiveHint":true}; The name "get_or_create_customer" says "get": a word for reading.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
18 tools
Deletes or cancels 6Claude Code: deny
attach_planMUTATES Autumn billing data — attaches (subscribes) a plan to a customer; may create an invoice / return a payment URL.No findings
Why it is in this group
- The name "attach_plan" says "attach": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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 }.
Annotations the server declares
- title: Attach a plan
- destructiveHint: true
create_entityMUTATES Autumn billing data — creates an entity (e.g.No findings
Why it is in this group
- The name "create_entity" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it MUTATES Autumn billing data — creates an entity (e.g. a seat) under a customer, tied to a feature. Autumn API: POST /v1/entities.create.
Annotations the server declares
- title: Create an entity
- destructiveHint: true
get_or_create_customerMUTATES Autumn billing data — fetches a customer by id, creating them if they do not exist.1 finding
Why it is in this group
- The name "get_or_create_customer" says "get": a word for reading.
- The server marks it destructive (destructiveHint: true).
Findings
- Warn
The server marks "get_or_create_customer" destructive (destructiveHint: true), and its name says "get", a word for reading.
What this check looks forMatched text
annotations: {"destructiveHint":true}; The name "get_or_create_customer" says "get": a word for reading.
Description, as the server wrote it MUTATES Autumn billing data — fetches a customer by id, creating them if they do not exist. Autumn API: POST /v1/customers.get_or_create.
Annotations the server declares
- title: Get or create a customer
- destructiveHint: true
open_customer_portalMUTATES Autumn billing data — creates a Stripe billing-portal session for a customer to manage their subscription.No findings
Why it is in this group
- The name "open_customer_portal" says "open": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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 }.
Annotations the server declares
- title: Open customer billing portal
- destructiveHint: true
track_usageMUTATES Autumn billing data — records a usage event (deducts/credits a feature balance).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Track usage
- destructiveHint: true
update_customerMUTATES Autumn billing data — partially updates a customer.No findings
Why it is in this group
- The name "update_customer" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it MUTATES Autumn billing data — partially updates a customer. Only provided fields change. Autumn API: POST /v1/customers.update.
Annotations the server declares
- title: Update a customer
- destructiveHint: true
Changes things 1Claude Code: ask
autumn_requestPower-user escape hatch: POST to any Autumn read/preview endpoint not wrapped by a dedicated tool.1 finding
Why it is in this group
- The name "autumn_request" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "autumn_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "autumn_request" says "request": a word for a change.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Raw read request
- readOnlyHint: true
Only reads 11Claude Code: allow
checkREAD-ONLY entitlement check: does a customer have access to (or enough balance of) a feature?No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check feature access / balance
- readOnlyHint: true
get_customerFetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances).No findings
Why it is in this group
- The name "get_customer" says "get": a word for reading.
Description, as the server wrote it Fetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances). Autumn API: POST /v1/customers.get.
Annotations the server declares
- title: Get a customer
- readOnlyHint: true
get_entityFetch a single entity (e.g.No findings
Why it is in this group
- The name "get_entity" says "get": a word for reading.
Description, as the server wrote it Fetch a single entity (e.g. a seat) belonging to a customer. Autumn API: POST /v1/entities.get.
Annotations the server declares
- title: Get an entity
- readOnlyHint: true
get_featureFetch a single feature by id.No findings
Why it is in this group
- The name "get_feature" says "get": a word for reading.
Description, as the server wrote it Fetch a single feature by id. Autumn API: POST /v1/features.get.
Annotations the server declares
- title: Get a feature
- readOnlyHint: true
get_planFetch a single plan by id (optionally a specific version).No findings
Why it is in this group
- The name "get_plan" says "get": a word for reading.
Description, as the server wrote it Fetch a single plan by id (optionally a specific version). Autumn API: POST /v1/plans.get.
Annotations the server declares
- title: Get a plan
- readOnlyHint: true
list_customersList/filter customers with cursor pagination.No findings
Why it is in this group
- The name "list_customers" says "list": a word for reading.
Description, as the server wrote it List/filter customers with cursor pagination. Autumn API: POST /v1/customers.list. Returns { list, next_cursor }.
Annotations the server declares
- title: List customers
- readOnlyHint: true
list_entitiesList a customer's entities with cursor pagination and optional filters.No findings
Why it is in this group
- The name "list_entities" says "list": a word for reading.
Description, as the server wrote it List a customer's entities with cursor pagination and optional filters. Autumn API: POST /v1/entities.list. Returns { list, next_cursor }.
Annotations the server declares
- title: List entities
- readOnlyHint: true
list_featuresList all features in the current environment.No findings
Why it is in this group
- The name "list_features" says "list": a word for reading.
Description, as the server wrote it List all features in the current environment. Autumn API: POST /v1/features.list. Returns { list }.
Annotations the server declares
- title: List features
- readOnlyHint: true
list_invoicesList invoices with cursor pagination and optional filters.No findings
Why it is in this group
- The name "list_invoices" says "list": a word for reading.
Description, as the server wrote it List invoices with cursor pagination and optional filters. Autumn API: POST /v1/invoices.list. Returns { list, next_cursor }.
Annotations the server declares
- title: List invoices
- readOnlyHint: true
list_plansList all plans (products) in the current environment.No findings
Why it is in this group
- The name "list_plans" says "list": a word for reading.
Description, as the server wrote it List all plans (products) in the current environment. Autumn API: POST /v1/plans.list. Returns { list }.
Annotations the server declares
- title: List plans
- readOnlyHint: true
preview_attachPreview the cost/effect of attaching a plan to a customer WITHOUT charging or changing anything.No findings
Why it is in this group
- The name "preview_attach" says "preview": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Preview attaching a plan
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.16.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http autumn https://autumn.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__autumn__get_customer",
"mcp__autumn__list_customers",
"mcp__autumn__check",
"mcp__autumn__list_invoices",
"mcp__autumn__get_entity",
"mcp__autumn__list_entities",
"mcp__autumn__list_features",
"mcp__autumn__get_feature",
"mcp__autumn__list_plans",
"mcp__autumn__get_plan",
"mcp__autumn__preview_attach"
],
"ask": [
"mcp__autumn__autumn_request"
],
"deny": [
"mcp__autumn__get_or_create_customer",
"mcp__autumn__update_customer",
"mcp__autumn__track_usage",
"mcp__autumn__attach_plan",
"mcp__autumn__create_entity",
"mcp__autumn__open_customer_portal"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as autumn. Review it before you use it.