Skip to main content
Glama
Sign In
tiendanube-mcp

tiendanube-mcp

by commentemeapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to tiendanube-mcp

No user-submitted related servers found.

    Related Servers

    • tiendanube-mcp

      fedeclavero
      A
      license
      B
      quality
      C
      maintenance
      A free, open-source MCP server that connects AI assistants to the Tiendanube/Nuvemshop API so they can manage products, variants, stock, orders, fulfillment, customers, coupons, shipping, payments, content and webhooks from plain-language requests. It exposes 191 tools across 39 API resources, with a read-only mode, honest tool annotations and rate-limit-aware, context-friendly responses.
      191
      1
      MIT

    • ConvoKit MCP

      ConvoKitApp
      A
      license
      A
      quality
      B
      maintenance
      Enables coding assistants to integrate the platform using official SDK, UI, authentication, and REST documentation guides, and to manage an app's users, scoped tokens, memberships, conversation metadata, and messages through configurable connections.
      5
      MIT

    • MCP Tienda Nube

      ropu
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes all 111 endpoints of the Tienda Nube API as tools for Cursor (or other MCP clients) to code directly with the API.
      15
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources