Ask your store a question. Get an answer, not a dashboard.

Questions you’d otherwise build a report for

Throttle speaks the Model Context Protocol (MCP), so an AI assistant such as Claude can look things up in your store and answer in plain English:

• “What did we sell last week compared with the week before?”
• “Why did this customer’s checkout fail?”
• “Which subscriptions moved to past due this month?”
• “What’s outstanding on invoice terms, and how late is it?”

Behind those answers are tools for orders, customers, payments, invoices, receivables aging, quotes, subscriptions, discounts, abandoned carts, events, and webhook deliveries — plus a business summary, sales over time, the checkout funnel, subscription movement, and a digest of what needs attention.

For developers, too

The assistant can search the Throttle docs, describe any API endpoint, and validate a request body — naming retired fields before you ship them — and explain why a checkout or integration is failing.

Safe by default

• Read-only unless you say otherwise. The hosted server never writes. The local package can take actions such as refunds or customer updates only when you explicitly allow writes — and production writes need a second, separate opt-in.
• Scoped by key. Tools appear only for the scopes the key holds; a read-only key gets a read-only assistant.
• One environment at a time. A connection is pinned to one workspace environment.
• Customer PII withheld on assistant connections that sign in with OAuth: names, emails, phone numbers, street addresses, and free-form notes stay out of the conversation.

Two ways to connect

• Hosted at mcp.usethrottle.dev, for assistants that connect over the web.
• Local with npx @usethrottle/mcp and an API key, for Claude Code, Claude Desktop, Cursor, and other MCP clients.

The MCP server docs have the configuration for each. A ChatGPT app is coming soon.