A
licenseNot graded
qualityD
maintenanceA Model Context Protocol server designed to integrate with Claude Desktop, allowing users to interact with Prestashop e-commerce platforms through natural language interfaces.
9 npm
2
ISC
Printify MCP Server
by TSavo
Related Servers
Alternatives to Printify MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables seamless integration between Claude AI and development tools like VSCode, Augment, Vercel, Airtable, and Square.7MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server that integrates InvokeAI with Claude Code, enabling AI-powered image generation, transformation, and upscaling directly from your AI assistant.5MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables Claude to automate Twitter posting with AI-generated images and thread support.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude AI to interact with Paybyrd's payment processing API, allowing for creating payment links, processing refunds, and retrieving order information.11 npmMIT
- -licenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol (MCP) server that enables Claude to create and manipulate designs in Figma through either a Figma plugin or directly via the Figma API.-
TDQS
D1.8/5.0
Scored across 19 tools
Disambiguation3/5
Most tools are distinct in purpose (e.g., list_products vs get_product), but there is some overlap between get_blueprint and get_blueprints, and generate_image vs generate_and_upload_image could confuse agents. The lack of descriptions increases ambiguity, but names are mostly clear.
Naming Consistency4/5
Tool names generally follow a verb_noun pattern (e.g., list_products, get_product, create_product). Some deviations like how_to_use and set_default are acceptable, but overall the pattern is consistent. Mixing get_blueprint (singular) and get_blueprints (plural) is a minor inconsistency.
Tool Count4/5
With 19 tools, the count is on the higher end but still reasonable for a Printify integration that covers products, images, shops, defaults, and blueprints. It approaches the heavy range but each tool seems to serve a specific function, so it's acceptable.
Completeness4/5
The tool surface covers product CRUD (create, get, update, delete, publish), image generation/upload, shop management, and blueprint/provider retrieval. Missing operations might include order management or mockup generation, but for the apparent scope, it's fairly complete. Some related functions like get_defaults/set_default are included.
Maintenance
ActivityInactive
ResponsivenessUnresponsive