The answer to “can I connect Etsy to Claude” is yes, and there are four ways to do it. They are not interchangeable. They split on whether the connection can write, and on where your Etsy credentials end up. All four then stop at the same door, which the setup guides tend to pass over in a sentence.
The four routes
Claude's connector directory. Nothing to connect. Etsy is not in it, and Etsy has not shipped an MCP server of its own, so this is not a route yet.
A community MCP server. Several exist on GitHub, built on Etsy's Open API v3. You run the server on your own machine and register it with your client, and you supply the API credentials yourself.
A hosted MCP or an integration platform. Services in this shape sit between Claude and Etsy, and the setup is the shortest of the four. Two things come with that: your Etsy credentials live on their infrastructure, and several of them are read-only by design.
A desktop client with the connector built in. Orkas is this shape. It calls https://openapi.etsy.com/v3/application directly from your machine, so there is no MCP server to run and nothing sitting in the middle.
The door all four stop at
Etsy's Open API v3 is not open in the sense of “get a key and start calling”. Reading or writing your own shop requires an app that has been approved for Seller API Access. Individual sellers can apply for one under Etsy Developers → Your Apps; you do not need a company to do it.
You come away with three values, and one of them costs people an afternoon:
Keystring and Shared Secret come straight off your app's detail page. Shop ID is the numeric identifier, not your shop's name — and your public shop URL contains the name, not the ID. The documented way to resolve it is the findShops endpoint, which searches by shop name and returns shop_id in the result. That call has to be authenticated with the Keystring and Shared Secret you just received, so the order matters: app first, credentials second, then look up your own shop ID using them.
One step is easier than it reads. Etsy asks you to register a callback address for the app, which sounds like you need to stand up a server. You do not — you register whichever address your client uses. Orkas uses https://orkas.ai/api/connectors/oauth/dcr-callback; you paste it into the Redirect URI field and that is the whole step.
We are not going to publish an approval time. Etsy does not commit to one, and the numbers quoted in forums are anecdotes rather than a schedule. Treat it as a step rather than a formality, and start it before you start evaluating clients. Etsy's official authentication documentation is the thing worth reading while you wait.
Reading is not writing
Once credentials exist, the routes stop being equivalent. Asking how many orders came in last week is a read. Changing a price, renewing a listing, updating stock or switching a shipping profile is a write, and it needs the matching scopes.
This is the distinction most “connect Etsy to Claude” write-ups skip. A hosted connector that answers plain-English questions about your shop data is genuinely useful and genuinely read-only; ask it to fix twelve listings and nothing happens. Check the write side before you choose, because the application effort in front of it is identical either way.
The Orkas connector covers the shop, listings, inventory, order fulfilment, shipping profiles and shop sections — both sides. Credentials are encrypted on your own device rather than living in a config file or on someone else's servers, and anything that writes to a live shop goes through a permission prompt in the client instead of relying on the model to be careful.
When not to use this
Four cases where something else is the better answer. You only want to ask questions: a hosted connector is less work and there is nothing to install. You want it running unattended on a schedule: Orkas is a desktop application, so closing the window stops it; a scheduled job on a server is the right shape. You want Etsy to trigger workflows across dozens of other services: integration platforms are built for that and this is not. You want to bulk-change titles, prices or tags: Etsy's own bulk edit tool in Shop Manager already does that, with no API application at all. Do not install anything for that one.
What the desktop route replaces is not Etsy's own tooling. It is the pile of small services you would otherwise place between your shop and a model, each holding its own copy of your credentials. The same catalogue covers eBay, Walmart Marketplace, Amazon Seller Central, Shopify, WooCommerce and the Chinese platforms, so that pile does not reappear once per storefront.