iFood

Lista os pedidos da loja no iFood por período (agrupados por dia, com status, valores e id), via a API interna do Portal do Parceiro.

Detalhe de um pedido específico do iFood (status, datas, distância de entrega, id do parceiro). Bulk support: accepts order_ids for batched execution.

Lista os lançamentos financeiros / repasses da loja no iFood (extrato financeiro do Portal do Parceiro).

無需輸入參數。

Resumo financeiro agregado do período (total de pedidos, faturamento, ticket médio, série diária), pronto para gráfico.

Dados da conta/loja no Portal do Parceiro iFood (perfil, papéis e permissões).

無需輸入參數。

Retorna o catálogo/cardápio da loja no iFood (produtos, categorias e preços).

無需輸入參數。

Status de disponibilidade da loja no iFood (aberta/fechada, pausas e horários).

無需輸入參數。

Show the current MCP platform and adapter versions.

無需輸入參數。

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

無需輸入參數。

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

無需輸入參數。

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.