tiendanube-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-docsA | Search the official Tiendanube / Nuvemshop developer docs (Admin API, apps, NubeSDK, themes, Storefront API, AI and agents), fetched live from nuvemshop.dev. Returns matching pages with URL and, for the top three, the best matching section. Use it first for any "how do I" question; follow up with read-doc. |
| read-docA | Read a page of the official docs, or one section of it, by URL or site path. Fetched live as Markdown from nuvemshop.dev or tiendanube.dev; other hosts are refused. Use it after search-docs, lookup-endpoint or when the user pastes a docs link. |
| lookup-endpointA | Look up Tiendanube / Nuvemshop Admin API endpoints by path, resource or keywords: method, path, full URL with version and store_id, the OAuth scope it needs and the reference page. Works offline from an index of the 2025-03 reference. Use it when writing or reviewing API calls. |
| lookup-scopeA | List the OAuth scopes of Tiendanube / Nuvemshop apps and the resources each one opens, or find the scope for a resource, endpoint path or scope name. Use it when choosing the scopes of an app in the Partners Portal or debugging a 401/403. |
| lookup-webhook-eventA | List the webhook events of Tiendanube / Nuvemshop (orders, products, customers, fulfillment orders, locations, billing, app lifecycle and the required privacy webhooks), or find one, with how to register and verify them. Use it before registering webhooks or writing a receiver. |
| scaffold-webhook-handlerA | Generate an Express (TypeScript) webhook receiver for Tiendanube / Nuvemshop: x-linkedstore-hmac-sha256 verification over the raw body, immediate 200, one case per event and a node:test for the signature. Returns the files for the caller to write; the server never writes to disk. |
| scaffold-oauth-callbackA | Generate the Express (TypeScript) OAuth 2 authorization code flow of a Tiendanube / Nuvemshop app: install redirect with state, callback that exchanges the code with a JSON body and stores the token per app and store. Returns the files for the caller to write. For a full app, it points to the official templates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The search-docs/read-doc pair is clearly delineated as a two-step flow, and the three lookup-* tools target distinct reference domains (endpoints, scopes, webhook events). The only soft overlap is that lookup-endpoint also returns the OAuth scope, which brushes against lookup-scope, but descriptions explicitly state when to use each.
All seven names follow a strict kebab-case verb_noun pattern (search-docs, read-doc, lookup-endpoint, lookup-scope, lookup-webhook-event, scaffold-webhook-handler, scaffold-oauth-callback). The lookup-* and scaffold-* families are internally parallel and predictable.
Seven tools is well-scoped for a documentation/reference assistant: two retrieval tools, three reference lookups, and two code generators. Each tool covers a distinct need with no filler.
The surface covers the core developer workflow: find docs, read docs, look up endpoints, scopes and webhook events, and scaffold webhook and OAuth handlers. Minor gaps remain — endpoint lookup is limited to the 2025-03 Admin API (no Storefront API or theme/NubeSDK lookup), and there is no app-boilerplate scaffold beyond the OAuth flow.