Throttle + Claude
Ask Claude about your Throttle orders, revenue, subscriptions, and checkout failures through Throttle's MCP server, read-only with customer PII withheld.
What the integration does
Throttle runs a Model Context Protocol (MCP) server, which lets Claude look things up in your store and answer in plain English: “Why did checkouts fail yesterday?”, “Which subscriptions churned this month and why?”, “What’s overdue on invoice terms?”
The hosted server gives Claude dozens of read-only tools covering:
- orders, payments, customers, invoices, quotes, subscriptions, discounts, and abandoned carts,
- analytics — sales over time, a business summary, conversion funnel, revenue breakdown, subscription movement, and an “what needs attention” digest,
- diagnosis — explaining why a specific checkout failed and checking integration health,
- developer help — searching the Throttle docs and validating API payloads.
It can read across every application in a workspace, and says which application each figure comes from.
Safe by design
- Read-only. The hosted connector can’t change anything in your store.
- Customer PII withheld. Names, emails, phone numbers, and street addresses are not shared with the assistant.
- One environment per connection. You choose the workspace and environment when you connect, and the session can’t wander into another one.
- Revocable. Connected assistants are listed in the dashboard, where you can disconnect them at any time.
Connecting Claude
Developers can connect today from Claude Code or Claude Desktop, either by running the @usethrottle/mcp package locally or by pointing at the hosted server with an API key — the MCP server docs have the exact config. The local package can also seed test data and, when you explicitly allow it, make changes in non-production environments.
A one-click listing in Claude’s connector directory, for teams who don’t want to handle API keys, is on the way.