
Nuvemshop
Nuvemshop (Tiendanube) e-commerce platform, your store's products, orders, customers, categories and
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Nuvemshop (Tiendanube) e-commerce platform, your store's products, orders, customers, categories and
How to connect
How to connect Nuvemshop to Claude
The server address to paste into Claude settings:
https://api.mcp.ai/p_nuvemshop
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Nuvemshop to ChatGPT
The server address to paste into ChatGPT settings:
https://api.mcp.ai/p_nuvemshop
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Nuvemshop to Cursor
The server address to paste into Cursor settings:
https://api.mcp.ai/p_nuvemshop
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (24)
Raw names from tools/list. Only developers need these.
| nuvemshop_list_accounts | Lista lojas Nuvemshop vinculadas a este install — store_id, label e apelido. |
| nuvemshop_products_list | Leitura de produtos da loja Nuvemshop. Ações: - list: produtos paginados (params: page, per_page, q busca textual, category_id, published, created_at_min, updated_at_min). - get: produto por id (requer product_id). [Flattened action: list] Bulk support: accepts product_ids, category_ids for batched execution. |
| nuvemshop_products_get | Leitura de produtos da loja Nuvemshop. Ações: - list: produtos paginados (params: page, per_page, q busca textual, category_id, published, created_at_min, updated_at_min). - get: produto por id (requer product_id). [Flattened action: get] Bulk support: accepts product_ids, category_ids for batched execution. |
| nuvemshop_products_write_create | Cria ou edita produtos na Nuvemshop. Ações: - create: cria produto (data = JSON com name, variants[], etc.). - update: edita produto (requer product_id; data = JSON só com os campos a mudar). [Flattened action: create] Bulk support: accepts product_ids for batched execution. |
| nuvemshop_products_write_update | Cria ou edita produtos na Nuvemshop. Ações: - create: cria produto (data = JSON com name, variants[], etc.). - update: edita produto (requer product_id; data = JSON só com os campos a mudar). [Flattened action: update] Bulk support: accepts product_ids for batched execution. |
| nuvemshop_orders_list | Leitura de pedidos da loja Nuvemshop. Ações: - list: pedidos paginados (params: page, per_page, status, payment_status, shipping_status, created_at_min, updated_at_min, q). - get: pedido por id (requer order_id). [Flattened action: list] Bulk support: accepts order_ids for batched execution. |
| nuvemshop_orders_get | Leitura de pedidos da loja Nuvemshop. Ações: - list: pedidos paginados (params: page, per_page, status, payment_status, shipping_status, created_at_min, updated_at_min, q). - get: pedido por id (requer order_id). [Flattened action: get] Bulk support: accepts order_ids for batched execution. |
| nuvemshop_orders_write_update | Mutações em pedidos Nuvemshop. Ações: - update: PUT no pedido (requer order_id; data = JSON com campos editáveis, ex. owner_note). - close | open | cancel | pack | fulfill: transição de status (requer order_id; data opcional, ex. cancel aceita { reason }). [Flattened action: update] Bulk support: accepts order_ids for batched execution. |
| nuvemshop_orders_write_close | Mutações em pedidos Nuvemshop. Ações: - update: PUT no pedido (requer order_id; data = JSON com campos editáveis, ex. owner_note). - close | open | cancel | pack | fulfill: transição de status (requer order_id; data opcional, ex. cancel aceita { reason }). [Flattened action: close] Bulk support: accepts order_ids for batched execution. |
| nuvemshop_orders_write_open | Mutações em pedidos Nuvemshop. Ações: - update: PUT no pedido (requer order_id; data = JSON com campos editáveis, ex. owner_note). - close | open | cancel | pack | fulfill: transição de status (requer order_id; data opcional, ex. cancel aceita { reason }). [Flattened action: open] Bulk support: accepts order_ids for batched execution. |
| nuvemshop_orders_write_cancel | Mutações em pedidos Nuvemshop. Ações: - update: PUT no pedido (requer order_id; data = JSON com campos editáveis, ex. owner_note). - close | open | cancel | pack | fulfill: transição de status (requer order_id; data opcional, ex. cancel aceita { reason }). [Flattened action: cancel] Bulk support: accepts order_ids for batched execution. |
| nuvemshop_orders_write_pack | Mutações em pedidos Nuvemshop. Ações: - update: PUT no pedido (requer order_id; data = JSON com campos editáveis, ex. owner_note). - close | open | cancel | pack | fulfill: transição de status (requer order_id; data opcional, ex. cancel aceita { reason }). [Flattened action: pack] Bulk support: accepts order_ids for batched execution. |
| nuvemshop_orders_write_fulfill | Mutações em pedidos Nuvemshop. Ações: - update: PUT no pedido (requer order_id; data = JSON com campos editáveis, ex. owner_note). - close | open | cancel | pack | fulfill: transição de status (requer order_id; data opcional, ex. cancel aceita { reason }). [Flattened action: fulfill] Bulk support: accepts order_ids for batched execution. |
| nuvemshop_customers_list | Leitura de clientes da loja Nuvemshop. Ações: - list: clientes paginados (params: page, per_page, q, created_at_min, updated_at_min). - get: cliente por id (requer customer_id). [Flattened action: list] Bulk support: accepts customer_ids for batched execution. |
| nuvemshop_customers_get | Leitura de clientes da loja Nuvemshop. Ações: - list: clientes paginados (params: page, per_page, q, created_at_min, updated_at_min). - get: cliente por id (requer customer_id). [Flattened action: get] Bulk support: accepts customer_ids for batched execution. |
| nuvemshop_categories | Lista categorias da loja Nuvemshop (params opcionais: page, per_page, parent). |
| nuvemshop_coupons | Lista cupons de desconto da loja Nuvemshop (params opcionais: page, per_page). |
| nuvemshop_coupons_write_create | Cria cupom de desconto na Nuvemshop. action: create. data = JSON com code, type (percentage|absolute|shipping), value, etc. [Flattened action: create] |
| 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 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. |
| 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>" } after the user pastes, or with no args to get the link. |