MCP server

Before you read on

This page is different from the rest of the docs, and it's worth saying up front: the MCP server isn't built, and it isn't specified either. The API and webhooks contracts are locked in the architecture document, field by field. This one isn't. What follows is product intent, and all of it may change.

If you're deciding whether Payezz is right for you, decide without counting on this. When it exists, it'll be published here with its contract and examples you can copy.

What MCP is

MCP, short for Model Context Protocol, is an open protocol that lets an assistant use tools and read data from an external system in a structured way, instead of someone copying and pasting information into a chat.

For a hosting store, it means asking “how many overdue invoices do I have” or saying “create a 20% coupon for Black Friday” from the assistant you already use, and having the action actually happen in your instance, with its audit trail and permissions.

How we want it to work

The MCP server won't be a parallel system. It will sit on the same API and the same permissions your admin panel already uses, for a simple reason: two different paths to the same data end up disagreeing, and in billing a disagreement is money counted wrong.

• You choose what's exposed. Tool by tool, not all or nothing. An assistant can read your revenue without being able to touch a price.
• Read and write, kept apart. Read tools will run without confirmation; tools that change data will ask for explicit confirmation, and those that move money will also require an action from you in the admin panel.
• Everything is logged. Every call shows up in the activity log with its source, just like a manual action.
• Its own revocable credential. With its scope, its expiry and a button to cut it off, without touching the rest of your integrations.
• No third-party data. An assistant connected to your instance sees your data, and only yours: instance isolation applies here exactly the same.

The tools we have in mind

No final names or parameter signatures, because they don't exist yet:

• Look up revenue, failed payments and sign-ups for a period, broken down by product.
• Find a customer, an order, an invoice or a service.
• See a service's status and its renewal history.
• Create or edit products, prices and coupons.
• Draft and schedule an announcement or a campaign.
• Review the Payezz fees charged and accrued, and the next settlement.

Anything that involves charging, refunding or deleting will stay out of the first version. That line is easy to cross and hard to undo.

In the meantime

What will exist first is the REST API over your instance's resources and signed webhooks. With those two pieces you can build an integration with the assistant of your choice today, without waiting for us to ship the server.

If MCP is a deal-breaker for you, tell us at hola@payezz.app: knowing how many people ask for it is what decides the order we build things in.