What are the API, the MCP and webhooks?
They're three ways of connecting MB Suite to other tools, so nobody has to copy data by hand or keep checking:
| What it is | What it's for | How it connects |
|---|---|---|
| REST API | Your systems, your ERP or a script read and write in MB Suite: create a deal from your website, send leads to your spreadsheet, update tasks from another tool. | With an API key that acts as a person, with the per-module permissions you choose. |
| MCP server | Claude, ChatGPT, Cursor or your own agent work in your MB Suite from the conversation: find a contact, create a deal, check how much you spent on Meta. | Claude, ChatGPT, VS Code and Claude Code ask for your permission on an MB Suite screen; Cursor and your own agents use an API key. Step by step: Connect Claude, ChatGPT or Cursor to MB Suite with the MCP. |
| Webhooks | MB Suite tells your system the moment something happens: a lead comes in, a deal changes stage, a post goes out, a form gets a response. | You paste your system's URL and choose the events; every delivery arrives signed. See Webhooks. |
Who turns them on, and with which plan?
An owner or an admin of the workspace turns them on, once for the whole workspace. They're included in active paid subscriptions: the free trial doesn't include them. If your workspace is on the trial, Settings > API & MCP tells you so and offers Go to Subscription; once the subscription is paid, come back and turn them on in one click. If billing is paused for non-payment, they can be turned on once it's settled.
Until then, the rest of the team sees a notice that they aren't turned on yet, so they can ask an owner or an admin. Once they're on, any member can connect Claude, ChatGPT, VS Code or Claude Code with their own permissions (the MCP tab has the URL and the steps); API keys, webhooks, Usage and the Request log belong to owners and admins.
How do I turn them on?
- In the workspace, go to Settings > API & MCP.
- Check what your plan includes: how many calls per day and how many active API keys. If you'd like to read how it works first, Read the documentation opens it in a new tab.
- Press Turn on API & MCP. The API keys, MCP, Webhooks, Usage, Request log and Documentation tabs appear, and the header shows the On status.
- Go on with what you need: create your first API key, connect Claude, ChatGPT or Cursor or create a webhook.
What happens in the Accounts?
The API and the MCP are turned on in the workspace and apply to all its Accounts: an Account uses its workspace's, and they aren't turned on or off from an Account. If you open API & MCP inside an Account and they aren't on yet, the screen says so: it offers the agency's people Go to the workspace, and tells the client's people to ask the agency.
The workspace's API keys and apps can also work in its Accounts, if you allow it when you create or authorize them. For an Account to have its own API keys: if the agency pays its subscription, the agency allows it from Partners (see API keys); if the Account pays its own subscription, it doesn't need that permission, but it can only create and use its own API keys once that subscription is paid and active (during the free trial, the Account's screen says so).
How do I turn them off, and what happens to what I already created?
- In the workspace's Settings > API & MCP, open the On status in the header.
- Choose Turn off API & MCP, read what happens and confirm with Turn off.
Within a minute, API keys and connected apps (Claude, ChatGPT, Cursor and others) stop responding and webhooks stop sending new events, in every Account of the workspace too. Nothing is deleted: API keys, authorized apps and webhooks stay as they were, and the screen shows an amber notice with who turned them off and when. While they're off, you can't create API keys or webhooks, but you can still edit, rotate, suspend, revoke or delete the ones you have: that's what you need if you turned them off because of a leak. To come back, an owner or an admin presses Turn back on and everything stays as it was.
What happens if the subscription stops being paid?
The API and the MCP pause, just as if you had turned them off: API keys and connected apps answer with a 402 payment_required error, and webhooks stop sending events. It happens when billing is paused for non-payment or when the period of a cancelled subscription ends. Nothing is deleted: in the workspace's Settings > API & MCP, a notice explains it and offers owners and admins Go to Subscription; once the subscription is paid again, everything resumes on its own, without turning anything back on.
Every rejected request says why in its error code, so your integration knows what happened: payment_required (402), billing is paused; platform_requires_paid_plan (403), the subscription is on the free trial or there isn't one; platform_not_enabled (403), the API and the MCP are turned off in the workspace, or haven't been turned on yet. And if MB Suite suspends the workspace, the API and the MCP answer organization_suspended: see My workspace shows as suspended.
How much can I use?
Quotas grow with your plan: calls per day and per minute, and how many API keys and webhooks you can have active at a time. You see the main ones on the screen where you turn the API and the MCP on and, afterwards, all of them on the Usage tab, under Your plan's quotas; the comparison between plans is on Pricing. Daily quotas reset every day at 00:00 UTC.
When a call needs a daily quota that's already used up, it gets a 429 error until the reset. At 80% and at 100% of a quota, owners and admins get a notice by email and in their notifications; for an Account, the workspace's owners and admins too. What you do in MB Suite's own screens doesn't count.
Where do I see how much is used and what was done?
On the Usage tab: today's and this month's calls, reads, writes and errors, how long responses take, the calls of the last 30 days, the API keys or apps that called the most, the most used operations and Your plan's quotas, with how much of each you've used.
On the Request log tab: every API request and every operation the MCP runs in the last 30 days, with who made it, with which API key or app, which operation, how it ended and how long it took. You can filter by day, API key or app, status, operation or error code, search for a request_id, and open a request to see its detail and, if it failed, what the error means. View in request log, in the menu of an API key or a connected app, opens it already filtered. What an API key or an app does inside an Account, even one from the workspace, shows up in that Account's Request log, not in the workspace's. The log doesn't keep what was sent or what was answered: never the API key, the token or the request's data.
Is it safe to connect other tools?
Every API key and every connected app acts as a person in the workspace and can never do more than that person: if that person only sees their own deals, so does the API key or the app; if they're a Viewer, it can only read. On top of that, you choose which modules they reach and whether they can write; deleting comes turned off; and bulk changes, most deletions and anything that sends something outside MB Suite, changes something on another platform or has a separate cost first go through a preview that the tool itself confirms. Everything is recorded under that person's name, and every request, in the Request log.
If an API key is used suspiciously —many rejected requests in a row, or attempts to get into organizations that aren't its own— MB Suite suspends it on its own and sends the owners and admins a notification; once the integration has been checked, it's reactivated from its menu (see API keys).
Which connected platforms can I use through the API and the MCP?
The terms of some platforms limit what can be done with their data outside MB Suite's screens, and the API and the MCP respect them. From Google Ads, Business Profile, YouTube and TikTok, nothing is available this way: neither their data nor changes or posts on them; so the modules that only work with them, like Local SEO or Auto-Budget, aren't available either. From LinkedIn, only the reports of your ad accounts and pages and your Lead Gen Form leads, and only with an API key on the REST API, not through the MCP, a connected app or an API key for an AI agent; its members' comments and mentions aren't available, and nothing can be published or changed on LinkedIn. Your other connected platforms, like Meta, Google Analytics or Search Console, work through the API and the MCP like the rest of MB Suite.
In the CRM, the deals, prospects, people and companies that came in or were completed through TikTok aren't available; those from LinkedIn Lead Gen follow LinkedIn's rule, and those from a Google Ads form come without the form's answers. Nor do the PDFs of a dashboard, a report or a report delivery with data from those platforms come out this way, and a delivery that includes their accounts can't be created or scheduled.
A request those terms don't allow gets a 403 platform_terms_restricted error, which says which platform it is, and the MCP doesn't even offer those operations to the assistant. For the same reason, webhooks don't send some events, or send them without some data: Webhooks says which. In MB Suite's screens everything works as always, and the developer documentation lists these platforms in the Permissions and scopes guide.
What does “Beta” mean?
The API & MCP screen carries the Beta mark: the API, the MCP and webhooks already work with your real data, and they keep adding operations, events and improvements. So that a change doesn't break what you've already connected, each organization is pinned to the API version in force when it creates its first API key, and each API key and each webhook keeps its own until you change it. What changes in each version is in the documentation's changelog.
Where's the technical documentation?
The Documentation tab has the guides, the reference for the modules active in your organization and the webhook events, and Open the developer site takes you to the full site: developers.mb-suite.com, with search, the error codes, the changelog and the status of the API, the MCP and webhooks. For everyday use, go on with these articles: API keys, Connect Claude, ChatGPT or Cursor to MB Suite with the MCP and Webhooks.
The API, the MCP and webhooks take your organization's data —contacts, deals, metrics and whatever else you allow— to the tools you choose, which handle it under their own terms. Their use is governed by our Terms and Conditions and our Data Processing Agreement (DPA).
Still have questions?
Ask MIA, the MB Suite AI assistant: open it with the MB AI button (⌘J) in the top bar. MIA knows the section you're in, so you can ask it about what you see on screen — and it can also answer how-to questions about using MB Suite.