Connect Etsy to Claude Code

Have Claude draft listings and manage orders in Etsy. From the terminal, inside the sessions where you already work.

How do you connect Etsy to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Etsy, you add a Etsy MCP server: a small hosted service that exposes Etsy's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Etsy account. No API keys pasted into config files.

claude mcp add --transport http etsy https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Etsy once connected?

Full read-write Etsy access lets Claude draft and update listings with titles, tags, descriptions, and prices, adjust inventory and variations, and mark orders shipped with tracking, all once you approve. The listing edits and order work that meant tab-switching happen where you already plan them.

Draft a new listing with title, tags, description, and price for your review
Update an existing listing's price, tags, or inventory quantity
Edit variations and stock levels across a set of listings
Batch-update inventory quantities across a set of listings after you review
Mark an order shipped and attach a tracking number after you confirm
Find listings matching a query and propose batched tag or price updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Etsy access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Etsy API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Etsy changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Etsy connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Etsy connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Etsy account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Etsy's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Etsy?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Etsy account it signs in with. Revoking access is one click in Etsy.

More on the Etsy connector

Etsy connector for claude.ai Wix + Claude Code Ecwid + Claude Code Amazon Seller Central + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us