For vendors
Native MCP collaboration notes
How ShopMCP evaluates, builds, and launches native MCP integrations with ecommerce platforms.
Native first, collaboration when approved
ShopMCP first-class integrations are marketed as Native. When a platform helps with API review, coverage validation, logo approval, or launch support, we may add a small collaboration signal such as Built with PlatformName or PlatformName reviewed.
What ShopMCP provides
- Typed MCP tools for the workflows operators and agencies actually run.
- Hosted MCP transport, tool-list changes, usage metering, and client setup guidance.
- Credential handling that keeps upstream secrets server-side.
- Setup docs, example prompts, launch copy, and native integration-page distribution.
- Roadmap feedback based on operator requests and in-app demand signals.
What we need from vendors
- A technical contact who can answer API, auth, and rate-limit questions.
- API documentation, test credentials, sandbox access, or OAuth app review support.
- Approval for public logo usage and claims before any collaboration badge is shown.
- Launch support through a backlink, marketplace listing, newsletter, or social announcement.
Safety model
ShopMCP integrations are not generic call_api wrappers. Each public tool has a named handler, a typed input schema, and an explicit read/write policy.
- Credentials are encrypted at rest and never exposed through MCP responses.
- Write tools can be compiled in but held off globally until reviewed.
- Per-workspace write access remains opt-in where supported.
- Coverage gaps are documented internally before launch and revisited after customer feedback.
Start collaboration intake
Email the partner intake with your product, API docs, preferred use cases, and the technical contact for review: partners@shop-mcp.app.