In two lines: the MCP is the door through which an AI assistant works inside MB Suite. You paste the server URL into Claude, ChatGPT, Cursor or another app, authorize in MB Suite what it can do, and from then on you ask it for things in plain language: it does them as you, with your permissions, and everything is recorded under your name.

What is the MCP and what can I do with it?

MCP (Model Context Protocol) is an open standard that lets AI assistants use other applications. With MB Suite connected, you can ask Claude, for example, “which open deals do I have in the sales pipeline?”, “find Laura Gómez and tell me which stage her deal is in”, “create a deal for Acme and log a note with what we discussed” or “how much did I spend on Meta this month compared with last month?”, and the assistant does it in your MB Suite without you copying anything by hand.

The assistant works as the person who authorized it: it sees what they see and does what they can do, within the permissions they gave it, never more. Every action is recorded under their name. By default, every app only reads, even if it asks to write: if you want it to also create or change records, you turn that on when you authorize it (how, below).

What do I need to connect it?

To be a member of an organization with the API and the MCP turned on: an owner or an admin of the workspace turns them on (see API, MCP and webhooks). Claude, ChatGPT, VS Code and Claude Code connect with OAuth: they ask for your permission on an MB Suite screen and you decide what to give them, without creating anything first. Cursor, your own agent or a script connect with an API key, which an owner or an admin creates. Custom connectors depend on your Claude or ChatGPT plan: if you don't see the option, check with them.

What is the server URL?

It's in Settings > API & MCP, on the MCP tab, under MCP server, with its Copy button: https://mcp.mb-suite.com. It's the same for everyone: the organization and the permissions are chosen when you authorize or, with an API key, set by the API key. If you already connected an app with the previous address, https://mb-suite.com/api/platform/mcp, you don't need to change it.

Under Connect, the same tab has the step-by-step for each app —Claude, ChatGPT, Cursor, VS Code, Claude Code and Other app—, with the configuration or the command ready to copy (Copy configuration, Copy command). They're the same steps as below.

How do I connect Claude?

In Claude, open Settings → Connectors → Add custom connector.
Paste the server URL (if it asks for a name, call it MB Suite) and save.
Claude takes you to MB Suite to choose the organization and review the permissions (what's on that screen is explained below). When you press Allow, you're back in Claude, already connected.
In a conversation, try “What can I do in MB Suite?”. The first thing the assistant uses is mb_context, which tells it who you are, which organization it's in and what it can do. If you don't see it active, turn it on from the chat's tools menu.

On Claude's Team and Enterprise plans, an owner of the Claude account first adds the connector from the admin settings; then each person connects it and authorizes it with their own MB Suite user.

How do I connect ChatGPT?

In ChatGPT, open Settings → Apps & Connectors → Advanced settings and turn on developer mode. On business plans, an administrator enables it.
Back in Apps & Connectors, choose Create, paste the server URL as an MCP server and, if it asks, choose OAuth as the authentication.
ChatGPT takes you to MB Suite to authorize: review the organization and the permissions and press Allow.
In a conversation, turn on the MB Suite app and ask it something about your CRM.

OpenAI changes these menus often: connectors are now called apps, and developer mode has moved more than once. If you can't find it, look up “developer mode” in ChatGPT's help.

How do I connect Cursor?

Create an API key on the API keys tab. If you'd rather the agent see a typed tool for each operation, choose One tool per operation under Advanced.
On the MCP tab, under Connect, choose Cursor and copy the configuration with Copy configuration.
In Cursor, open Cursor Settings → Tools & MCP → New MCP Server, paste the configuration, replace mbs_live_YOUR_API_KEY with your whole API key and save.
MB Suite's tools show up in Cursor's agent.

The configuration looks like this: {"mcpServers": {"mb-suite": {"url": "https://mcp.mb-suite.com", "headers": {"Authorization": "Bearer mbs_live_YOUR_API_KEY"}}}}.

Keep the configuration with your API key in Cursor's global file (~/.cursor/mcp.json), not in a project's .cursor/mcp.json: that file lives inside the repository and can end up pushed along with the code.

How do I connect VS Code?

In VS Code, open the Command Palette and choose “MCP: Add Server”. You need GitHub Copilot.
Choose HTTP, paste the server URL and save it for your user or for the project. If you'd rather edit the file, Copy configuration on the MCP tab gives you the .vscode/mcp.json configuration.
The first time, VS Code asks for permission to sign in and takes you to MB Suite to choose the organization and review the permissions. VS Code isn't one of the apps MB Suite recognizes, so the screen asks you to check “I understand that MB Suite has not verified this app…” before you can press Allow.
In Copilot Chat, in Agent mode, try “What can I do in MB Suite?”.

How do I connect Claude Code?

In the terminal, add the server with the command from the MCP tab (Copy command): claude mcp add --transport http mb-suite https://mcp.mb-suite.com. Add --scope user and it's available in all your projects.
Open Claude Code, type /mcp and choose mb-suite to authenticate.
Claude Code opens MB Suite in the browser to choose the organization and review the permissions; when you press Allow, you're back in Claude Code, already connected.
Try “What can I do in MB Suite?”.

How do I connect another app, my own agent or a script?

On the MCP tab, under Connect, Other app explains the three ways, with the configuration ready to copy: if the app accepts remote MCP servers with OAuth, paste the server URL and it brings you to MB Suite to authorize it, like Claude; if it asks for an API key instead, create one on the API keys tab and use it as a Bearer token in the Authorization header; and if the app only accepts local servers, connect it through the mcp-remote bridge, which needs Node.js. Your own agent or a script does the same with any MCP client: it connects over HTTP to the server URL and sends the API key in the Authorization header of every request.

In an Account whose agency hasn't allowed its own API keys yet, the MCP tab says so when you pick Cursor or Other app: apps that connect with OAuth —Claude, ChatGPT, VS Code or Claude Code— can still be connected.

What do I see when I authorize an app?

When Claude, ChatGPT or another app asks for access, MB Suite opens the “… wants to access your MB Suite” screen, with the app's name (if you're not signed in, it asks you to sign in first). Before you press Allow:

Check who's asking, under the title. MB Suite recognizes Claude, Claude Code and ChatGPT by their domain, not by the name they declare: they show their own logo next to MB Suite's and Identified by its domain, followed by their domain (such as claude.ai or chatgpt.com). An app that registers itself when it connects —VS Code, for example— shows its initial instead of a logo and, in amber, No verified identity (the name, logo and links were declared by the app itself) or, if it identifies itself by its own domain, Identified by its domain with that domain. If an app MB Suite doesn't recognize is going to send you to a website when you finish, the address shows at the top, in amber: “When you finish it will send you to…”. Only apps published or verified by MB Suite show Verified app.
In Organization, choose where it will work: an organization you're a member of, with the API and the MCP turned on. If none of yours has them on, the screen tells you so: an owner or an admin turns them on in Settings > API & MCP, with an active paid subscription.
Under Requested permissions, the See your information row sums up what the app will be able to read: “Read access to … modules, with the same permissions as you”. Right below, you always see the detail of the modules with sensitive data —for example, which CRM data, the SMS in Phones, the direct messages in Inbox, the responses in Web Forms or the audiences in Email Marketing—, and Show modules opens the full list.
Writing is off by default, even if the app asks for it. If you want the app to also create and modify records, turn on the Read and write row: if the app asked for specific permissions, it covers only the modules where it asked to write, and if it asked only to read, the row doesn't show up. Deleting is separate.
Writing in a sensitive module —Members, Branding, Accounts, Client Portal, Email Marketing or Integrations— goes separately, under Write access to sensitive modules: one switch per module, all off, even if the app asks for it. Turn on only the ones it really needs: writing there can change who gets in, your brand, what your clients receive or your connections. Each module you switch on turns amber.
If the app asks to delete, a separate row shows up, turned off, once you turn on writing in some module: Delete records in…, with the modules it will be able to write in. Turn it on only if you want it to be able to delete; when you do, it turns amber.
If the app asks for it, or doesn't specify which permissions it wants, a separate row shows up, turned off: Connected mailboxes and calendars. Turn it on only if you want the app to read the emails from your own mailbox and the events from your own calendar that are linked to CRM people, companies or deals (never the whole mailbox); when you turn it on, the row turns amber. If the organization you picked doesn't allow it, the row stays disabled with the notice “Your organization does not allow it: an owner enables it in Settings → API & MCP → API keys.”
If you picked an agency workspace, you can turn on Also access Accounts and choose All Accounts or Choose Accounts: the app will also work in them, only in the ones you can see.
Under Advanced you can change the MCP tool mode (what changes is explained below).
At the bottom, next to Cancel and Allow, Claude, Claude Code and ChatGPT show where you return when you finish and a reminder. With Claude: “When you're done, you'll return to Claude at claude.ai. Allow only if you just started this connection from Claude yourself.” Claude Code returns to this computer, so it says “When you're done, you'll return to Claude Code on this computer (localhost:…)”, followed by the same reminder. The bottom also has the notice that it's an external app and the links to MB Suite's Terms and Privacy Notice and to the privacy policy of the app's company. If you didn't start the connection, press Cancel: someone can start it from their own account and send you the link.
If MB Suite doesn't recognize the app and hasn't verified it, the bottom shows, next to Allow, the box “I understand that MB Suite has not verified this app…”: check it only if you just started the connection yourself, from that app; without it, Allow stays disabled.
Press Allow to go back to the app, connected, or Cancel to give it no access.

On that screen you choose the organization, whether the app also writes, writing in each sensitive module, whether it can delete, whether it can read connected mailboxes and calendars, the Accounts and the tool mode. What you don't choose is which modules it reads, one by one: reading is granted together, in every module it asks for, and so is writing in the common modules, only if you turn on Read and write, whatever the app asks for. If the app asks to read more than you want to give it, press Cancel.

If you already connected the app without that permission —because your organization didn't allow it yet or because you didn't turn it on— and now you want to give it, disconnect it under Authorized connections and connect it again from the app, this time with the row turned on. And if an owner later turns it off for the organization, the app stops reading mail and calendar immediately, without you having to disconnect it, and reads again as soon as it's turned back on. Who turns it on and what happens when it's turned off is explained in API keys.

Whatever the app reads from your mail and calendar leaves MB Suite: the app receives that content and keeps it under its own terms, and under the consumer plans of some AI assistants it may be used to train models unless you disable that in the app. Emails include your customers' data: your organization is responsible for that disclosure, and the app may not use it for advertising or resell it. Turn on Connected mailboxes and calendars only for apps you trust that really need it.

If instead of that screen you see This request cannot be authorized, the app sent a request that doesn't match its registration and, for your security, MB Suite doesn't redirect you: close the tab and try again from the app.

What can the assistant do once connected?

In Compact (recommended) mode, the assistant sees five general tools and, if it has access to the CRM, mb_search:

Tool	What it's for
`mb_context`	Tells it who it acts as, in which organization, with which role, plan and daily limits, which Accounts it reaches (a short list and how many there are in total), which integrations are connected, what happened recently in the CRM and which modules it can work in, with the number of operations in each. It's the first thing it uses.
`mb_catalog`	A module's catalog of operations, with their full descriptions. A large module, like the CRM, comes one group at a time.
`mb_search_operations`	Finds an operation by keywords, in English, Spanish or Portuguese. If the change you asked for needs a permission the connection doesn't have —writing, with a connection that only reads—, or is only done in MB Suite's screens, like creating API keys, it says so.
`mb_describe_operation`	An operation's card: what data it needs and what it returns.
`mb_execute_operation`	Runs an operation.
`mb_search`	Searches the CRM for deals, people, companies and prospects by text.

With One tool per operation, it also sees one tool for each operation it can run (for example, crm_deals_create), which some models make better use of. Either way, the assistant only sees what the person can do with those permissions.

If you ask for something the connection can't do —changing records with a connection that only reads, or deleting without that permission—, MB Suite tells the assistant exactly what's missing, so it can tell you. To give it, disconnect the app under Authorized connections and connect it again with that permission turned on; with an API key, an owner or an admin changes it with Edit. And if an answer is too long for one message —a very long list, for example—, it comes shortened and tells the assistant how to ask for the rest, so it can go through it in parts.

Through the MCP, nothing from Google Ads, Business Profile, LinkedIn, TikTok or YouTube is available, because their terms don't allow it: the assistant doesn't see their operations, or gets an error that explains it, and where several platforms mix —a dashboard or the CRM's attribution, for example— it gets the rest without them. In the CRM, it doesn't see the deals, prospects, people or companies that came in or were completed through TikTok or LinkedIn Lead Gen, and it doesn't get the PDFs of dashboards, reports or report deliveries with data from those platforms. In MB Suite's screens everything works as always (which platforms and why, in API, MCP and webhooks).

What about bulk changes, sends and things that can't be undone?

Some things don't run in one go: anything that changes many records at once (moving or deleting deals in bulk, for example), anything irreversible, like deleting, anything that sends something outside MB Suite —a WhatsApp, an email, an SMS, a post on your social networks, a meeting invitation— or changes something on another platform, and anything with a separate cost, like generating with AI or auditing a site. The assistant first requests a preview (dry_run) that says what's going to happen —which and how many records will change, what will go out or whether it has a separate cost— and returns a confirm_token; only with that code, valid for 10 minutes, can it run it. Ask it to show you the preview before confirming.

A few ask for it only when they'd really send something: inviting a member without the invitation email, for example, runs directly. The preview itself tells the assistant whether it needs the code.

Deleting also requires that you allowed it when you authorized the app or created the API key. Most deletions keep a copy for 30 days in the Trash —what's deleted from the CRM, in the CRM Trash—, where the owner or an admin can restore it. If you're an owner or an admin, you can also ask the assistant to restore it: each deletion tells it which copy stayed in the Trash. What lives outside MB Suite doesn't come back, like a WhatsApp template in Meta or an event in your calendar: the assistant sees in each operation whether it can be undone.

If the assistant makes a huge number of calls in a row or in one day, MB Suite asks it to wait and retry: there's a per-minute and a daily limit that depend on your plan. The assistant sees them in mb_context, and so do owners and admins on the Usage tab.

If the assistant can't connect or MB Suite stops answering it, check developers.mb-suite.com/status: it shows the status of the API, the MCP server and the webhooks, with any ongoing incident or scheduled maintenance; also check that the API and the MCP are still turned on and the subscription active. If it's one operation that fails, the assistant receives the reason, the field that was wrong and a request_id: it can often fix the call on its own, and if you write to us about it, include that code.

How do I see and disconnect authorized apps?

Go to Settings > API & MCP and open the MCP tab.
Under Authorized connections you see every app connected through OAuth: the App, who it acts as (Acts as, the person who authorized it), a summary of its Permissions, the Accounts it reaches, when it was Connected and its Last used. Click the row to see, below it, all its permissions grouped by area. If an app can read connected mailboxes and calendars, its permissions show Connected mailboxes and calendars (if the organization turned it off afterwards, it leaves the summary and the detail shows Connected mailboxes and calendars · paused).
In the Actions menu on the app's row (the three dots), choose Disconnect and confirm. The app loses access immediately; to use it again, it will have to ask for permission again.

API keys don't show up there: they're suspended or revoked from the API keys tab. If you're not an owner or admin, in API & MCP you only see the MCP and Documentation tabs; in MCP, the apps you authorized, which you can disconnect on your own; the owner and the admins see the whole organization's apps and can disconnect any of them. In each app's Actions menu, the owner and the admins also have View in request log, which opens the Request log tab filtered by that app. If the person who authorized an app leaves the organization, the app stops working.

An app connected through the MCP reads and changes data in your MB Suite —contacts, companies, deals and activities in the CRM, the metrics of the platforms you connected whose terms allow it (Meta, Google Analytics, Search Console, Facebook and Instagram; the terms of Google Ads, Business Profile, LinkedIn, TikTok and YouTube don't allow using them through the MCP) and, if you allow it, the emails and events linked to the CRM— and processes it with its own AI, under its own terms. Authorize only apps you trust, with the permissions they need, and disconnect the ones you no longer use. The use of the MCP and the handling of that data are governed by our Terms and Conditions, our Privacy Notice 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.

Connect Claude, ChatGPT or Cursor to MB Suite with the MCP