M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionShopify MCP ServerMCP server for Shopify Admin GraphQL API for AI assistantsNPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS36 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions5 / 2016 / 20
Maintenance6 / 2018 / 20
Documentation11 / 2018 / 20
Setup experience9 / 2015 / 20
Best for
  • Developers who want to manage Shopify stores using AI assistants
  • Projects requiring programmatic access to the Shopify Admin API from MCP-compatible tools
  • Teams seeking a ready-made, production-grade Shopify MCP server
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Users who don't need to manage a Shopify store or access the Admin API
  • Those seeking a server for the Shopify Storefront API (this server only uses the Admin API)
  • Users looking for an officially maintained MCP server (this one is not officially maintained by Shopify)
  • Projects outside the NPM ecosystem (e.g., pure Python/Go)
  • Environments without network access to deps.dev, OSV.dev, and the npm registry
  • Scenarios requiring maintenance by an official upstream vendor
Required permissions
  • Shopify Admin API access, requiring a custom app with Admin API scopes including `read_products`, `write_products`, `read_customers`, `write_customers`, `read_orders`, `write_orders` (plus scopes for inventory/metafields as needed)
  • Optional Redis connection for OAuth token persistence (if enabled)
  • Credentials via environment variables or CLI arguments (access token or client ID/secret)
  • Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
  • Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
Risks and side effects
  • Credentials may be exposed: store client secrets or access tokens securely
  • Data loss or corruption risk due to write permissions (write operations are allowed)
  • Using a non-official server may introduce security or compatibility issues; review code at your own risk
  • Enabling Redis without proper configuration may cause startup failure or token cache issues
  • Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
  • Depends on availability and accuracy of external services
  • Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
  • Third-party open source project, not officially maintained by NPM or Anthropic
Supported clientsClaude DesktopClaude Desktop, VS Code, Cursor
Tools019