Contexto

Who am I, where am I, what can I do

platform.me

The living card of the caller: the actor and how it is calling (session, key, MCP), its role, the organization (name, type, plan, modules, members, created_at, child_org_status and billing_mode; never the subscription: that is platform.orgs.get), the credential's scopes if any, the daily limits (and how many requests without a valid credential one address may send per minute) and, in limits.today, how much of each daily quota was used today and how much is left (calls, reads, writes and each external platform; the day is UTC and goes back to zero at resets_at; an Account that uses its workspace's quota sees its own use, with scope shared and no remaining), the first 50 Accounts it can reach with just what it takes to pick one (id, name, slug, status and child_org_status: platform.orgs.list and platform.orgs.get have their modules, members and the rest; child_orgs_next says so when more exist), child_orgs_total (the active Accounts it reaches, without archived or deleted ones; exact unless child_orgs_total_exact is false, in workspaces of more than 300 Accounts), the connected integrations (only when the caller and the credential can read Integrations; otherwise empty), what is recent in the CRM (open activities, paused sources, leads in the last 7 days; null when the caller or the credential cannot read the CRM, and a seller with restricted scope counts their own and unassigned ones) and, in operations, one line per module it can work in: module, name, operation_count and group_count. With a test key (mbs_test_…) practice says the call works on the workspace's practice organization (example data, its own small limits) and which operations that reach an external platform are simulated there; the others answer 409 sandbox_external_unavailable. Call it first in a session; then call platform.catalog with a module (and, for a large one like crm, a group) to read the operations with their full descriptions, or with ids_only to get every operation id. Module: Organization (organizations), even though the id starts with platform.; any valid credential can read it.

Escopo

organizations:read

Permissão

Ver o módulo

Tool do MCP

platform_meNa superfície completa; na compacta, mb_execute_operation com id: "platform.me".

Custo declarado: até 365 leituras e 0 escritas por chamada (contam na cota diária).

Parâmetros

Sem parâmetros.

Resposta

Erros

Exemplo

curl "https://api.mb-suite.com/v1/me" \
  -H "Authorization: Bearer $MB_API_KEY"

Testar com a sua API key de teste

Com uma API key de teste o pedido vai sempre para a sua organização de prática: dados de exemplo que você pode reiniciar.

curl "https://api.mb-suite.com/v1/me" \
  -H "Authorization: Bearer $MB_TEST_KEY"

The operations this caller can run

platform.catalog

The index of operations, filtered by the caller's role, the org's modules and the credential's scopes, in parts that fit in one response. Without module: one line per module (module, name, operation_count, group_count). With module (for example task_management): every operation of that module with its full description and just-in-time instructions; a module too large for one response (like crm) comes as its groups with how many operations each has, and next says to call again with group. With module and group (group always needs module: group ids repeat across modules): that group's operations in full. With ids_only: just the operation ids, by module. A module or group that is not available comes back empty with next saying where the ids are. Read it before calling an operation you have not used. Module: Organization (organizations), even though the id starts with platform.; any valid credential can read it.

Escopo

organizations:read

Permissão

Ver o módulo

Tool do MCP

platform_catalogNa superfície completa; na compacta, mb_execute_operation com id: "platform.catalog".

Custo declarado: até 0 leituras e 0 escritas por chamada (contam na cota diária).

Parâmetros

Resposta

Erros

Exemplo

curl "https://api.mb-suite.com/v1/catalog" \
  -H "Authorization: Bearer $MB_API_KEY"

Testar com a sua API key de teste

Com uma API key de teste o pedido vai sempre para a sua organização de prática: dados de exemplo que você pode reiniciar.

curl "https://api.mb-suite.com/v1/catalog" \
  -H "Authorization: Bearer $MB_TEST_KEY"