printful-mcp
Related Servers
Alternatives to printful-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables secure, read-only access to WooCommerce store data through MCP-compatible assistants, letting users query products, orders, sales summaries, and inventory alerts without exposing store credentials.-
- FlicenseBqualityDmaintenanceProvides read-only EspoCRM access for AI assistants, enabling record retrieval and preparation of signed change sets without direct modification or deletion.7-
- AlicenseNot gradedqualityCmaintenanceProvides safe, read-only CRM access for AI assistants with per-key scopes, field masking, rate limits, and a full audit log of allowed and blocked actions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to safely inspect Stripe billing data such as subscriptions, invoices, failed payments, and churn, with read-only access, per-tool permissions, and a tamper-evident audit log.2 npmMIT
- AlicenseAqualityCmaintenanceGives AI assistants read-only access to your Patreon creator data, including campaigns, members, posts, and tiers.625 PyPI7MIT
- AlicenseNot gradedqualityCmaintenanceRead-only access to Stripe data including customers, charges, subscriptions, balance, and invoices.2 npmMIT
TDQS
Scored across 7 tools
Each tool targets a distinct resource (auth, store product, catalog product, orders), and printful_get is explicitly described as an escape hatch for paths without a dedicated tool. However, the allowlist still includes paths like /orders and /store/products that also have dedicated tools, creating minor overlap.
All tools share a clear printful_ prefix, and most follow a get_/list_ verb pattern. Printful_whoami and the generic printful_get deviate from the noun+verb convention, but the pattern remains predictable overall.
Seven tools is a well-scoped set for a read-only Printful integration, covering auth, products, and orders without unnecessary bloat. Each tool has a clear role, and the count feels appropriate for the server's purpose.
The server covers the core read workflows: authentication/store id, catalog and store product details, and order listing/retrieval, with the escape hatch filling gaps for tax/countries and other allowed endpoints. It is intentionally read-only, so missing create/update operations are not a gap, though a dedicated list-catalog-products tool would round out the surface.