Skip to main content
Glama
enesjakozh
GeLi2001

shopify-mcp

by GeLi2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Servidor MCP de Shopify

(¡Deja una estrella si te gusta!)

Servidor MCP para la API de Shopify, que permite la interacción con los datos de la tienda mediante la API GraphQL. Este servidor proporciona herramientas para gestionar productos, clientes, pedidos y más.

Características

  • Gestión de productos : buscar y recuperar información de productos

  • Gestión de clientes : cargar datos de clientes y administrar etiquetas de clientes

  • Gestión de pedidos : consulta y filtrado avanzado de pedidos

  • Integración con GraphQL : integración directa con la API de administración GraphQL de Shopify

  • Manejo integral de errores : mensajes de error claros para problemas de API y autenticación

Related MCP server: Shopify MCP Server

Prerrequisitos

  1. Node.js (versión 16 o superior)

  2. Token de acceso a la aplicación personalizada de Shopify (consulte las instrucciones de configuración a continuación)

Configuración

Token de acceso de Shopify

Para utilizar este servidor MCP, necesitará crear una aplicación personalizada en su tienda Shopify:

  1. Desde tu panel de control de Shopify, ve a Configuración > Aplicaciones y canales de venta

  2. Haga clic en Desarrollar aplicaciones (es posible que primero deba habilitar la vista previa para desarrolladores)

  3. Haga clic en Crear una aplicación

  4. Establezca un nombre para su aplicación (por ejemplo, "Servidor Shopify MCP")

  5. Haga clic en Configurar ámbitos de API de administración

  6. Seleccione los siguientes ámbitos:

    • read_products , write_products

    • read_customers , write_customers

    • read_orders , write_orders

  7. Haga clic en Guardar

  8. Haga clic en Instalar aplicación

  9. Haga clic en Instalar para darle a la aplicación acceso a los datos de su tienda

  10. Después de la instalación, verá su token de acceso a la API de administrador

  11. Copia este token: lo necesitarás para la configuración

Uso con Claude Desktop

Agregue esto a su claude_desktop_config.json :

{
  "mcpServers": {
    "shopify": {
      "command": "npx",
      "args": [
        "shopify-mcp",
        "--accessToken",
        "<YOUR_ACCESS_TOKEN>",
        "--domain",
        "<YOUR_SHOP>.myshopify.com"
      ]
    }
  }
}

Ubicaciones para el archivo de configuración de Claude Desktop:

  • MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Ventanas: %APPDATA%/Claude/claude_desktop_config.json

Alternativa: Ejecutar localmente con variables de entorno

Si prefiere utilizar variables de entorno en lugar de argumentos de la línea de comandos:

  1. Crea un archivo .env con tus credenciales de Shopify:

    SHOPIFY_ACCESS_TOKEN=your_access_token
MYSHOPIFY_DOMAIN=your-store.myshopify.com

  2. Ejecute el servidor con npx:

    npx shopify-mcp-server

Instalación directa (opcional)

Si desea instalar el paquete globalmente:

npm install -g shopify-mcp-server

Luego ejecútalo:

shopify-mcp-server --accessToken=<YOUR_ACCESS_TOKEN> --domain=<YOUR_SHOP>.myshopify.com

Herramientas disponibles

Gestión de productos

  1. get-products

    • Obtenga todos los productos o busque por título

    • Entradas:

      • searchTitle (cadena opcional): Filtrar productos por título

      • limit (número): Número máximo de productos a devolver

  2. get-product-by-id

    • Obtenga un producto específico por ID

    • Entradas:

      • productId (cadena): ID del producto a recuperar

Gestión de clientes

  1. get-customers

    • Obtenga clientes o busque por nombre/correo electrónico

    • Entradas:

      • searchQuery (cadena opcional): Filtrar clientes por nombre o correo electrónico

      • limit (número opcional, predeterminado: 10): Número máximo de clientes a devolver

  2. update-customer

    • Actualizar la información de un cliente

    • Entradas:

      • id (cadena, obligatoria): ID de cliente de Shopify (solo ID numérico, como "6276879810626")

      • firstName (cadena, opcional): nombre del cliente

      • lastName (cadena, opcional): apellido del cliente

      • email (cadena, opcional): dirección de correo electrónico del cliente

      • phone (cadena, opcional): número de teléfono del cliente

      • tags (matriz de cadenas, opcional): etiquetas que se aplicarán al cliente

      • note (cadena, opcional): Nota sobre el cliente

      • taxExempt (booleano, opcional): si el cliente está exento de impuestos

      • metafields (matriz de objetos, opcional): metacampos del cliente para almacenar datos adicionales

  3. get-customer-orders

    • Obtener pedidos para un cliente específico

    • Entradas:

      • customerId (cadena, obligatoria): ID de cliente de Shopify (solo ID numérico, como "6276879810626")

      • limit (número opcional, predeterminado: 10): Número máximo de pedidos a devolver

Gestión de pedidos

  1. get-orders

    • Obtener pedidos con filtrado opcional

    • Entradas:

      • status (cadena opcional): Filtrar por estado del pedido

      • limit (número opcional, predeterminado: 10): Número máximo de pedidos a devolver

  2. get-order-by-id

    • Obtener un pedido específico por ID

    • Entradas:

      • orderId (cadena, obligatoria): ID completo del pedido de Shopify (p. ej., "gid://shopify/Order/6090960994370")

  3. update-order

    • Actualizar un pedido existente con nueva información

    • Entradas:

      • id (cadena, obligatoria): ID de pedido de Shopify

      • tags (matriz de cadenas, opcional): nuevas etiquetas para el pedido

      • email (cadena, opcional): Actualizar el correo electrónico del cliente

      • note (cadena, opcional): notas de pedido

      • customAttributes (matriz de objetos, opcional): atributos personalizados para el pedido

      • metafields (matriz de objetos, opcional): Ordenar metacampos

      • shippingAddress (objeto, opcional): Información de la dirección de envío

Depuración

Si encuentra problemas, consulte los registros MCP de Claude Desktop:

tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

Licencia

Instituto Tecnológico de Massachusetts (MIT)

Available Tools

5 tools
get-customersD
ParametersJSON Schema
NameRequiredDescriptionDefault
limitNo
searchQueryNo

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-ordersD
ParametersJSON Schema
NameRequiredDescriptionDefault
limitNo
statusNoany

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-product-by-idD
ParametersJSON Schema
NameRequiredDescriptionDefault
productIdYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-productsD
ParametersJSON Schema
NameRequiredDescriptionDefault
limitNo
searchTitleNo

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update-orderD
ParametersJSON Schema
NameRequiredDescriptionDefault
customAttributesNo
emailNo
idYes
metafieldsNo
noteNo
shippingAddressNo
tagsNo

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 5 tool updatesv1.0.0
    • First observedget-customers
    • First observedget-orders
    • First observedget-product-by-id
    • First observedget-products
    • First observedupdate-order
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

D1.8/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose targeting specific Shopify resources: customers, orders, products, and order updates. There is no overlap in functionality, making it easy for an agent to select the correct tool for each task without confusion.

Naming Consistency4/5

The naming follows a consistent verb-noun pattern with hyphens (e.g., get-customers, update-order), which is predictable and readable. The minor deviation is that 'get-product-by-id' includes a preposition, slightly breaking the pure verb-noun style, but overall the pattern is clear and mostly uniform.

Tool Count3/5

With 5 tools, the count is reasonable for a Shopify integration, but it feels borderline thin for covering the domain comprehensively. While core read operations are present, the scope might benefit from additional tools for full CRUD or lifecycle coverage, such as creating or deleting resources.

Completeness2/5

The tool set has significant gaps for a Shopify server, focusing heavily on read operations (get-customers, get-orders, get-products) with only one update tool (update-order). Missing are create and delete operations for customers, orders, and products, as well as other common actions like inventory management or webhook handling, which limits agent workflows and could lead to failures in broader tasks.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches