AI_SYNC MCP Server
Related Servers
Alternatives to AI_SYNC MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to access and manage Shopify store data including products, orders, inventory, and analytics through the Model Context Protocol. It allows users to query store performance and customer details using natural language.-
- AlicenseNot gradedqualityCmaintenanceConnects Claude, ChatGPT, Cursor, or any MCP client to a Shopify store, enabling read-only access to themes, Liquid files, catalogue data, and store configuration through 122 tools.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants such as Claude Desktop, Cursor, Claude Code, Gemini CLI, Zed and Cline to a NovaCRM store through the public v1 API, exposing 27 tools for clients, products, inventory, orders, coupons, webhooks, store settings and metrics, plus ready-made prompts. Access is authenticated with a store API key whose scopes, plan limits and rate limits determine what the AI may read or write.MIT

TailorKit MCPofficial
AlicenseBqualityDmaintenanceConnects AI assistants to the TailorKit API, enabling them to manage customizable product templates for e-commerce platforms through natural language conversations.44 npm6MIT- AlicenseNot gradedqualityAmaintenanceConnects AI assistants to WordPress/WooCommerce sites through the WordPress REST API, allowing management of products, orders, customers, shipping, taxes, discounts, reports, and store configuration via JSON-RPC 2.0.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Haravan e-commerce platforms via MCP protocol for natural language management of stores. Provides 7 smart analytics tools for insights and 63 base tools for CRUD operations on products, orders, customers, and inventory.20Apache 2.0
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: addNewStore creates a new store, findAllStores retrieves all stores for a merchant, and findStore searches stores with a natural language query. There is no overlap in functionality, and the descriptions make the distinctions explicit.
The naming is inconsistent: addNewStore uses camelCase with a verb-noun pattern, findAllStores uses camelCase with a verb-noun pattern, and findStore uses camelCase but lacks a noun (it should be findStores or similar). While all are camelCase, the lack of a consistent noun in findStore and the mix of 'New' in addNewStore versus no qualifiers in others shows poor pattern adherence.
With only 3 tools, the count feels thin for a store management domain, as it lacks update and delete operations. However, it covers basic create, list, and search functions, which is borderline but workable for minimal CRUD.
The tool set is significantly incomplete for store management. It includes add, find all, and search, but misses essential operations like update_store, delete_store, and get_store_by_id. This creates gaps that could lead to agent failures when full lifecycle management is needed.