Skip to main content
Glama
Sign In
fedeclavero

tiendanube-mcp

by fedeclavero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to tiendanube-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • Nuvemshop

      mcp-dir
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Nuvemshop e-commerce platform, enabling AI agents to manage products, orders, customers, categories, and coupons via official API with OAuth authentication.
      MIT

    • Shopify MCP

      chatterjeearjun
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that lets AI assistants answer Shopify store operations questions via tools like get_shop, list_products, get_product, and list_orders.
      4
      MIT

    • MCP Shopline

      asgard-ai-platform
      A
      license
      A
      quality
      B
      maintenance
      An open-source MCP server that wraps the Shopline Open API into 143 AI-callable tools for e-commerce data analysis, enabling AI agents to query orders, products, inventory, customer behavior, and promotions from Shopline stores through natural language.
      100
      62 PyPI
      20
      MIT

    • mcp-server-woocommerce

      AmitGurbani
      A
      license
      B
      quality
      C
      maintenance
      MCP server for managing WooCommerce stores through AI assistants like Claude. Provides 101 tools covering products, orders, customers, coupons, shipping, taxes, webhooks, settings, reports, and more.
      100
      169 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 191 tools

    Disambiguation3/5

    Most tools map to a distinct resource+action, but the set has built-in ambiguity: legacy order fulfillments vs modern fulfillment_orders, custom_fields vs custom_field_defs (duplicate unstable/stable surfaces), and several overlapping stock/price update tools (products_batch_stock_price, variants_batch_update, variants_update_stock). Descriptions help, but an agent must carefully choose among near-duplicates, especially across 191 tools.

    Naming Consistency4/5

    Names generally follow tiendanube_<resource>_<verb> in snake_case (e.g., products_list, products_get, products_create), which is predictable. There are minor deviations and awkward singular/plural shifts such as product_images vs products, order_fulfillments vs fulfillment_orders, and custom_field_defs vs custom_fields, plus a few upsert/set verbs.

    Tool Count1/5

    191 tools is an extreme mismatch for any practical MCP surface. Even for a broad e-commerce API, this set exposes nearly every endpoint, including unstable and legacy variants, forcing an agent to navigate a huge, unwieldy tool catalog.

    Completeness4/5

    Coverage is very broad across products, variants, images, orders, draft orders, fulfillment, shipping, payments, customers, discounts, content, webhooks, metafields, custom objects and billing. Some gaps remain, such as full CRUD for blog posts and promotions (no promotion update), plus incomplete lifecycle surfaces for a few content/billing resources.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources