# Mercos Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Mercos

Manage sales orders, customers, products and pricing in Mercos ERP

- Record: https://musedirectory.ai/connector/mercos
- Category: Productivity
- Developer: mcp.ai
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 158ms, checked 2026-09-28T07:31:11Z
- Endpoint: https://api.mcp.ai/p_mercos
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-25T10:51:42Z)
- Source: Found in the official MCP Registry (io.github.mcp-dir/mercos-mcp) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.mcp-dir%2Fmercos-mcp

Connects to Mercos sales force and rep ERP via official API. List and manage orders, customers, products, price tables, categories, payment terms, carriers, commissions and financial records. Create and update customers, products and orders in bulk.

Example request: "Show me all orders from this month and update their payment status"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Mercos to help me. It is a free service with an MCP server at https://api.mcp.ai/p_mercos. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- mercos_list_accounts: Lista as empresas (CompanyToken) Mercos conectadas a este install, com id e label.
- mercos_list_produtos: Lista produtos cadastrados (GET /v1/produtos). Use `alterado_apos` pra incremental.
- mercos_list_clientes: Lista clientes (GET /v1/clientes). Use `alterado_apos` pra incremental.
- mercos_list_pedidos: Lista pedidos (GET /v2/pedidos). Use `alterado_apos` pra incremental. (Pedidos vivem na v2.)
- mercos_list_tabelas_preco: Lista tabelas de preço (GET /v1/tabelas_preco).
- mercos_list_categorias: Lista categorias de produtos (GET /v1/categorias).
- mercos_list_condicoes_pagamento: Lista condições de pagamento (GET /v1/condicoes_pagamento).
- mercos_list_transportadoras: Lista transportadoras (GET /v1/transportadoras).
- mercos_list_usuarios: Lista vendedores/usuários (GET /v1/usuarios).
- mercos_list_comissoes: Lista comissões (GET /v1/comissoes). Filtre por colaborador_id ou pedido_id via `filters`.
- mercos_list_titulos: Lista títulos financeiros (GET /v1/titulos).
- mercos_create_cliente: Inclui cliente(s) (POST /v1/clientes). `data` = objeto ou array de clientes.
- mercos_update_cliente: Altera um cliente (PUT /v1/clientes/{id}). `id` + `data` com os campos a alterar. Bulk support: accepts ids for batched execution.
- mercos_create_produto: Inclui produto(s) (POST /v1/produtos). `data` = objeto ou array de produtos.
- mercos_update_produto: Altera um produto (PUT /v1/produtos/{id}). `id` + `data` com os campos a alterar. Bulk support: accepts ids for batched execution.
- mercos_create_pedido: Inclui um pedido (POST /v2/pedidos). `data` com cliente, itens, condição de pagamento etc.
- mercos_update_pedido: Altera um pedido (PUT /v2/pedidos/{id}). `id` + `data` com os campos a alterar. Bulk support: accepts ids for batched execution.
- mercos_ajustar_estoque: Ajusta o estoque de produtos em lote (POST /v1/ajustar_estoque_em_lote). `data` = array de ajustes.
- mercos_create_tabela_preco: Inclui uma tabela de preço (POST /v1/tabelas_preco). `data` com os campos da tabela.
- show_version: Show the current MCP platform and adapter versions.
- report_bug: Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
- connect: 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.
- toolkit_info: Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
- marketplace: 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 MC
- authenticate: 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>" } a

Screening checks:
- MCP handshake: pass (Answered in 1138ms)
- Domain against threat feeds (Cloudflare security DNS): pass (api.mcp.ai not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (25 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)