Python Shopify MCP Server for Claude

Created By
abhi-mahulea year ago
Shopify MCP server
Overview

What is Shopify MCP Server?

The Shopify MCP Server is a Python implementation of the Model Context Protocol (MCP) server that allows Claude AI to interact with Shopify store data, enabling intelligent assistance for e-commerce tasks.

How to use Shopify MCP Server?

To use the Shopify MCP Server, clone the repository, set up a Python environment, install dependencies, configure your Shopify credentials, and integrate it with Claude Desktop.

Key features of Shopify MCP Server?

  • Seamless integration with Claude for direct access to Shopify data.
  • Complete product access including detailed information and inventory.
  • Customer insights such as profiles and purchase history.
  • Order management capabilities including order details and fulfillment status.
  • Access to store metadata like currency and locale settings.

Use cases of Shopify MCP Server?

  1. Retrieve product details and inventory status.
  2. Analyze customer spending patterns.
  3. Manage and track orders efficiently.
  4. Provide contextual assistance in e-commerce conversations.

FAQ from Shopify MCP Server?

  • What are the prerequisites?

Python 3.10 or higher, a Shopify store with Admin API access, and Claude Desktop installed.

  • Is the server secure?

Yes, it runs locally and follows best practices for credential protection and minimal access.

  • Can I contribute to the project?

Yes, contributions are welcome through pull requests on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
abhi-mahule
Star
0
Language
Python
License
MIT 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
Crevio

2 days ago