Connect via MCP
Use Media Ops inside Claude, ChatGPT, Cursor, Claude Code or n8n.
The MCP server exposes Media Ops operations as tools for AI assistants. Address:
https://media.ops.infotrafego.com.br/api/mcpStreamable HTTP transport (stateless, JSON responses). Authentication with OAuth 2.1 — the assistant opens the Media Ops sign-in screen and you approve — or with an API key in the header, for clients without OAuth.
Connect your client
- Settings → Connectors → Add custom connector.
- Name:
Media Ops; URL: the address above. - Click Connect, sign in to Media Ops and click Aprovar acesso (Approve access).
claude mcp add --transport http media-ops https://media.ops.infotrafego.com.br/api/mcpOn first use, run /mcp and complete the sign-in. For use without a browser (CI), use a key:
claude mcp add --transport http media-ops https://media.ops.infotrafego.com.br/api/mcp \
--header "Authorization: Bearer $MEDIA_OPS_API_KEY"Any MCP client that supports OAuth and Streamable HTTP works with the same address: it discovers the authorization server on its own.
In the MCP Client Tool node: endpoint = the address above, HTTP Streamable transport, Header Auth authentication with Authorization = Bearer mops_… (a key created in Integrações with the permissions you need).
Tools
Tool names are in Portuguese; they are stable identifiers. Input fields, types and the REST equivalent of every tool are in the MCP tools reference.
| Tool | What it does | Permission |
|---|---|---|
quem_sou_eu | User, role, channel and permissions | — |
listar_clientes | Active clients | clients:read |
listar_bms | A client's Business Managers and assets (business_manager_id, ad accounts, pages, Instagram, pixels) | clients:read |
buscar_publicos | Custom audiences, interests, suggestions, locations; audience validation | meta:read |
buscar_formularios | The page's lead forms | meta:read |
buscar_publicacoes | Instagram posts | meta:read |
buscar_campanhas / buscar_conjuntos | Existing campaigns and ad sets | meta:read |
escanear_pasta_drive | Media in a Google Drive folder | meta:read |
validar_campanha | Simulates the campaign with the web app's rules, creating nothing | campaigns:write |
criar_campanha | Creates (or extends) the campaign — asynchronous | campaigns:write |
status_execucao / detalhar_execucao / listar_execucoes / logs_execucao | Tracking | campaigns:read |
reexecutar_execucao / reexecutar_log | Smart retry / retry of a single call | campaigns:write |
criar_publicos_engajamento / status_publicos / listar_execucoes_publicos | Engagement audiences | audiences:* |
listar_modelos_segmentacao / criar_… / renomear_… / remover_… | Targeting templates | templates:* |
listar_saldos / atualizar_saldos | Ad account balances | balances:* |
cadastrar_cliente / sincronizar_ativos_bm / ativar_desativar_conta / arquivar_cliente | Clients and Business Managers | clients:write |
listar_notificacoes | Notifications | — |
listar_usuarios / criar_usuario / atualizar_usuario / remover_usuario | Users (administrators) | admin:users |
On MCP, the assistant only sees the tools your permissions allow.
Sample conversation
"In client Acme, main ad account, create a traffic campaign for https://acme.com.br with R$ 80/day, using the creatives from Drive folder X, audience in São Paulo aged 25–45."
The assistant follows the flow: listar_clientes → listar_bms → buscar_publicos (location) → validar_campanha → criar_campanha → status_execucao. Errors come back per field, in Brazilian Portuguese, so the assistant can fix them itself.
Updated about 24 hours ago