Shopify MCP Server

Created By
kimcchqa year ago
Overview

what is Shopify MCP Server?

Shopify MCP Server is a server designed to interact with Shopify's API, enabling users to manage store data through a GraphQL interface. It provides tools for managing products, customers, orders, and more.

how to use Shopify MCP Server?

To use the Shopify MCP Server, clone the repository, install dependencies, configure your Shopify credentials in a .env file, and run the server using npm commands.

key features of Shopify MCP Server?

  • Product Management: Search and retrieve product information.
  • Customer Management: Load and manage customer data.
  • Order Management: Advanced querying and filtering of orders.
  • GraphQL Integration: Direct integration with Shopify's GraphQL Admin API.
  • Comprehensive Error Handling: Clear error messages for API issues.

use cases of Shopify MCP Server?

  1. Managing product inventories efficiently.
  2. Handling customer data and tagging.
  3. Retrieving and filtering orders based on various criteria.

FAQ from Shopify MCP Server?

  • How do I get my Shopify access token?

You need to create a custom app in your Shopify store and configure the necessary API scopes to obtain your access token.

  • Is there a limit to the number of products I can retrieve?

Yes, you can set a limit on the number of products returned in your queries.

  • Can I use this server for multiple Shopify stores?

Yes, you can configure it for different stores by changing the credentials in the .env file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kimcchq
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago