BETA
See what the MCP Server could save your team time on, how it works in practice, and what usage will cost from 1 October. Explore more → Frisbii MCP Server
Overview
The Frisbii MCP Connector lets an AI assistant, such as Claude or ChatGPT, read and — if you allow it via you API key — act on your live Frisbii Billing and Payment data during a conversation.
Instead of writing scripts or doing multiple API calls, anyone on your team can ask questions like "which customers have failed payments in the last 30 days?" or "pause this customer's subscription" directly in their chat client, and the assistant looks it up or carries it out against your real account.
Note
The connector is not a chatbot that Frisbii hosts on your data. It's a small server that sits between your AI client and the Frisbii platform. It never stores your data and holds no Frisbii credentials of its own, every request uses the API key you supply.
What is MCP?
MCP (Model Context Protocol) is an open standard that lets an AI assistant connect to an external system in a controlled way, so it can pull in real, current data and, where permitted, perform real actions, instead of only working from what it already knows.
Think of it as a translator between the assistant and Frisbii: the assistant doesn't get raw access to your database or API keys. It can only do what the connector explicitly exposes.
What is a "tool"?
A tool is one specific, well-defined action the assistant is allowed to invoke through the connector — for example "list customers," "get a customer's billing overview," or "refund a charge." Each tool has a fixed set of inputs and outputs, similar to a single API endpoint. The assistant can't run arbitrary code or queries against your data. It can only call the tools it's been given, with the parameters those tools accept.
The tool list is the complete list of things the assistant can ever do through this connector. If it's not a tool, the assistant cannot do it. → See Supported Frisbii MCP tools for the full list.
What can the MCP do
Once connected, the assistant can use MCP-supported capabilities, including:
Customers: Look up customers, balances, and a combined billing overview.
Subscriptions: List and view subscriptions; create, update, pause, resume, cancel; apply or remove coupons.
Invoices: List and view invoices; create, void, refund, download PDF, retry a failed payment.
Charges & payment methods: One-off charges and refunds; add, view, remove, and set default payment methods.
Credit notes & payouts: View credit notes; view payouts and reconcile a payout window.
Plans, add-ons & entitlements: Manage the product catalogue: plans, add-ons, and their entitlements.
Coupons & discounts: Create, update, and remove coupons and discounts.
Dunning & usage-based billing: Manage dunning plans, check dunning status, manage usage-based billing records.
Billing insight helpers: Purpose-built lookups, such as failed payments, blocked payments, dunning/overdue investigation, and a combined customer billing overview, that do a few bounded API calls on your behalf and return a summarized answer instead of making you assemble it from several separate lookups.
How your data is protected
You bring your own API key. The connector never has Frisbii credentials of its own. It uses the key you provide, exactly as if your own systems called the Frisbii API.
Stateless. Nothing is stored between requests. There's no database of your billing data sitting behind the connector.
No arguments or data are logged for billing. Usage is metered for billing purposes, but the recorded event is limited to metadata: which tool was called, whether it was allowed, and when. The customer data itself, and any arguments passed to the tool, are never recorded.
Guardrails on bulk access. List-style tools are paginated with a capped page size, and the composite "investigate" tools cap how many pages they'll fetch in one call — so a single request can't be used to silently pull your entire dataset.
Revocable at any time. Access is tied to the API key you supplied. Rotating or revoking that key in Frisbii immediately cuts off the connector. There's no separate access grant to remember to remove.