Shopify Admin GraphQL MCP Server

Created By
mattcoatswortha year ago
Overview

what is Shopify Admin GraphQL MCP Server?

Shopify Admin GraphQL MCP Server is a comprehensive Model Context Protocol (MCP) server designed for interacting with Shopify's Admin GraphQL API, enabling users to manage various aspects of their Shopify store.

how to use Shopify Admin GraphQL MCP Server?

To use the server, clone the repository, install the necessary dependencies, create a .env file with your Shopify credentials, and start the server using the provided commands.

key features of Shopify Admin GraphQL MCP Server?

  • Complete coverage of key Shopify Admin API functionality
  • Structured tools for managing products, orders, customers, inventory, discounts, and metafields
  • Documentation resources for each API section
  • Compatibility with any MCP-compatible client

use cases of Shopify Admin GraphQL MCP Server?

  1. Managing product listings and inventory levels
  2. Handling customer orders and cancellations
  3. Creating and managing discounts for promotions
  4. Accessing shop information and updating settings

FAQ from Shopify Admin GraphQL MCP Server?

  • What is required to run the server?

You need a Shopify Admin API access token and the necessary dependencies installed.

  • Can I use this server with any Shopify store?

Yes, as long as you have the correct access token and permissions.

  • Is there documentation available for the API?

Yes, documentation can be accessed via the shopify://docs/{section} resource.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago