Explore and build integrations with Etsy’s Open API through AI assistants. Search 90+ endpoints and inspect 50+ data models covering listings, shops, orders, payments, shipping, reviews, and users, with access to request/response schemas, OAuth scopes, authentication guides, and API documentation.
Mistral Vibe (formerly Le Chat) is Mistral's AI assistant. In Work mode it can add any remote MCP server as a custom connector and sign in to it with OAuth.
This guide connects Etsy Dev MCP to Mistral Vibe through MewCP, so Mistral Vibe can use Etsy Dev MCP's 8 tools, like learn_etsy_api, search_etsy_api and get_endpoint.
Etsy Dev MCP needs no credentials, but every call still runs through MewCP: scoped, checked and logged like any other.
More apps
Manage repositories, pull requests, issues, branches and development workflows on GitHub. Automate software delivery and collaborate across engineering projects.
Connect to external APIs, webhooks and internet services through standard HTTP requests. Build integrations with virtually any platform that exposes a web-based interface.
Give AI coding agents access to a curated library of real-world website designs, screenshots, design systems, and reusable UI components. Search visual references, find similar designs, analyze layouts, extract colors and typography, compare websites, and retrieve copy-ready JSX components for building better interfaces
An AI assistant can generate QR codes, update existing ones, retrieve analytics, or manage campaigns without switching apps. A QR-focused MCP server makes these actions available through one interface.
Other clients
Etsy Dev MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Etsy Dev MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
Open the Connectors page, click + Add Connector, then switch to the Custom MCP Connector tab. Only an admin can add connectors; on Free, Pro, and Student plans that is the account owner.
Open Mistral connectorsSet the connector name to mewcp (no spaces), paste this server URL, and click Connect.
Mistral detects the sign-in and opens MewCP's consent screen. Sign in and approve access. No API key needed.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps. To skip approval prompts, open My Connectors → mewcp → Functions and turn on Always allow for read tools.
Get an overview of the Etsy Open API v3 including authentication, available endpoint groups, and a guide on which tools to use. Call this first before using other Etsy API tools. Before calling, generate a unique correlationId for this session (<model-name>-<unix-timestamp-ms>-<4-random-hex-chars>, e.g. claude-1749385200000-9c2e) and pass it here and to every subsequent tool call. After completing all tool calls needed to answer the request, call `submit_feedback`. Do not begin writing your response to the user until that call has been made.
Search the Etsy Open API for endpoints and schemas by keyword. Returns ranked results with operationId, method, path, and description. Pass a `correlationId` (generated once per session) to link this call with others in analytics. Pass an `intent` to help the team understand usage patterns.
Get full details for a specific Etsy API endpoint by operationId. Returns method, path, parameters, request body, responses with resolved schemas, and required auth scopes. Pass a `correlationId` (generated once per session) to link this call with others in analytics. Pass an `intent` to help the team understand usage patterns.
Inspect an Etsy API data model by schema name. Returns properties, types, nested schemas, and which endpoints reference it. Pass a `correlationId` (generated once per session) to link this call with others in analytics. Pass an `intent` to help the team understand usage patterns.
Browse Etsy API endpoints filtered by tag, HTTP method, or tag group. Use `tag` or `group` (not both) to select endpoints, optionally combined with `method`. Returns a Markdown table with method, path, operationId, and description. Pass a `correlationId` (generated once per session) to link this call with others in analytics.
List available developer guides, optionally filtered by category. Returns guide IDs and titles grouped by category. Use a guide ID from the results to call get_guide for full content. Pass a `correlationId` (generated once per session) to link this call with others in analytics.
Get a developer guide by name. Returns the full markdown content of the guide. Pass an exact guide name (e.g. "tutorials/quickstart") or a natural language name (e.g. "quickstart", "Authentication") — the tool matches by ID, title, and content headings. Use `list_guides` or `learn_etsy_api` to discover available guide IDs and categories. Pass a `correlationId` (generated once per session) to link this call with others in analytics. Pass an `intent` to help the team understand usage patterns.
REQUIRED: Call this exactly once as your final tool call in every session — unconditionally, whether the session succeeded or failed, found everything needed or not. Do not skip this call even when the task completed perfectly. Do not begin writing your response to the user until this call has been made. Keep the `feedback` field under 500 characters (schema maximum) — one to three sentences is ideal. Name what worked and any specific gaps (missing endpoint, confusing schema, poor search results) with an impact estimate. MUST NOT contain PII, secrets, or order/customer-specific data — logged to analytics. Pass the same `correlationId`, `intent`, and `intentCategory` used throughout the session. This call always succeeds and never affects tool results.