Your Etsy shop has a to-do list. Claude can work through it with you.
Every Etsy seller knows the list. Descriptions written at midnight in your first month. Tags you picked before you understood tags. Prices set before your linen supplier put theirs up. A “Gifts” section that now holds half the shop.
None of it is urgent. All of it quietly costs you.
Claude is good at exactly this kind of work. Reading a lot of listings carefully. Spotting what is missing or inconsistent. Drafting fixes in your voice. Doing the dull arithmetic on margins. It does not get bored at listing 47.
If you read our guide to connecting Claude to your Shopify store, you will recognise the approach. But Etsy is a different place, with different rules and a different set of tools. The honest version of the setup looks different too.
This guide covers:
- The two routes: a Claude Project fed with your shop data, and an optional live connection.
- How to set each one up, step by step, with the settings that matter.
- How to check it is working before anything gets changed.
- Deep, practical use cases: descriptions, tags, pricing, sections, sales, new drafts, shipping checks and marketing.
We will use one fictional shop throughout: Willow & Thread Studio, a small maker selling handmade linen gifts, pouches and aprons. Every listing, price and conversation from Willow & Thread is made up to show the method. None of it is a real shop or a client result.
Claude reads, drafts and checks. You approve, and Etsy stays the source of truth.
First, get the three pieces straight
Most confusion about “Claude and Etsy” comes from mixing up three different things. They sound similar. They do very different jobs.
A Claude Project
Your voice, product facts, costs, policies and a dated listing export. Claude works from what you saved. It cannot see your live shop or change anything on Etsy.
Etsy Dev MCP server
Etsy's official documentation helper. Claude can search the Etsy API docs and specs. It does not call the Etsy API and cannot read or edit your shop.
An authorised shop MCP server
A server built on the Etsy Open API v3 that you approve through Etsy. Depending on its tools and your permissions, it can read and change live listings.
A note on the middle one, because it trips people up. Etsy publishes a Dev MCP server at https://mcp.api.etsycloud.com/mcp. It is real, official and free to use without an API key. Its tools search Etsy’s API documentation and look up endpoints. Etsy’s own page says plainly that it does not call the Etsy API directly. So it is brilliant for a developer asking “how do shop sections work in the API?” and useless for “update my apron listings”.
At the time of writing, we have not verified an Etsy-operated connector for managing a shop from Claude. That may change. If you see one, check who publishes it and what it can do before you trust it.
Which route should you take?
Start with the Project route. It covers a lot of the value in this guide and cannot change Etsy directly. Claude drafts. You review and paste approved changes into Shop Manager.
Add a live connection later if copying changes by hand is genuinely slowing you down, and you have a provider or developer you trust. It saves time on repetitive edits. It also adds setup, credentials and the risk that a batch goes wrong on your real listings.
There is no prize for connecting everything on day one.
Route 1: Set up a Claude Project for your shop
A Claude Project is a workspace with its own instructions and saved files. Every chat inside it starts with your shop brief already on the desk. No re-explaining your voice each time.
Step 1: Create the Project
In Claude, open Projects, choose + New Project, and give it a clear name, for example “Willow & Thread, Etsy listings”. If you are offered a sharing choice, keep it private unless a colleague genuinely needs it.
The name and description help you find it. They are not instructions. Claude follows what you put in the instructions box and the files.
Step 2: Write the Project instructions
Open Set project instructions, paste your rules and choose Save instructions. Here is a starter you can adapt:
“You help run Willow & Thread Studio, a fictional Etsy shop selling handmade linen gifts, pouches and aprons. Use the files in this Project for approved product facts and policies. Never invent materials, sizes, care instructions, certifications, stock levels, shipping times or prices. If a fact is missing or sources conflict, say ‘needs checking’. Write in the voice guide: warm, plain, specific, no hype. Etsy limits: up to 13 tags, each 20 characters or fewer including spaces; section names 24 characters or fewer. Show proposed changes with listing ID, current value and proposed value. Without an enabled, authorised shop connector, you cannot read or edit live Etsy data. Treat exports as dated snapshots and name the source and date you use. If a shop connector is enabled later, verify it before treating its reads as current. Never make changes without my explicit approval. Do not ask for or accept passwords, API keys or tokens.”
That last line matters. Nothing secret belongs in a Project, a file or a chat.
Step 3: Add your knowledge files
In the Project’s knowledge panel, use + to upload the files Claude should use as context. Good ones for an Etsy shop:
- Voice guide. Five to ten listings you are proud of, plus a short list of words you use and words you never use. Real examples beat adjectives.
- Product facts sheet. Verified materials, measurements, finishes, care instructions and lead times, per product. This is what stops invented details.
- Current policies. Processing times, returns, personalisation rules, as they are today.
- Cost sheet. Materials, packaging, your time, and the fees you actually see on your statements.
- A dated listing export. See the next step.
Before uploading sales files, remove buyer names, email addresses and delivery addresses. Keep only the anonymous order references and figures needed for the job.
Step 4: Download your listing data
In Etsy, go to Shop Manager > Settings > Options > Download Data and choose Download CSV for listings. Rename the file with today’s date, for example listings-2026-10-23.csv, and add it to the Project.
Know what you have got. The file covers active listings only, with columns such as title, description, price, currency code, quantity, tags, materials, image URLs and SKU if you added one. It does not automatically include listing IDs, variation details, or drafts and inactive listings. Sold orders and monthly statements are separate downloads.
Two habits follow from that:
- Add your own identifiers. Add a column with each listing’s URL or ID from your own records, so every proposal points at the right listing. Do not rely on matching by title. Two “Linen Apron” listings is all it takes.
- Treat it as a snapshot. It is a record of one moment, for analysis. It is not a full backup and it is not something to edit and upload back to Etsy. Approved changes go in through Shop Manager.
When the shop changes, download a fresh copy and replace the old file. A stale export produces confident, wrong advice.
- New ProjectClear name, private
- InstructionsRules, limits, no invented facts
- KnowledgeVoice, facts, policies, costs
- Dated exportActive listings plus your own IDs
- You applyApproved edits in Shop Manager
Step 5: Run a first test
Start a chat in the Project and ask:
“Using the listing export in this Project, tell me the file date, how many listings it contains, and list five with their ID, title, price and tag count. Flag any listing with fewer than 13 tags or no materials.”
If the count does not match your active listings in Shop Manager, find out why before you go further.
Route 2: Connect a live Etsy MCP server
This is the optional, more technical route. It is followable, but there is no single official “install Etsy” button to point you at, and no universal command that works for everyone. What you are actually doing is choosing a server, authorising it with Etsy, then adding it to Claude.
Step 1: Choose the server carefully
You need an MCP server built on the Etsy Open API v3 that exposes the tools you want, such as reading listings, updating listings or managing sections. Your options:
- A hosted provider. Someone else runs the server. Pick one that is maintained, explains its security, and documents its Etsy tools clearly.
- A professional self-hosted build. A developer you hire runs a server on infrastructure you control.
As one example, AnythingMCP publishes a guide to connecting Etsy to Claude. It is a third-party option. We have not tested or audited it and do not endorse it; it is here so the steps below are concrete. Its current guide has you go to Connectors > Etsy in its dashboard, enter the provider-specific app details, then copy the remote MCP URL from MCP Servers, picking your server. Follow the provider’s current docs, not our summary, because those screens will change.
A third-party listing in Claude’s directory, or a server with “Etsy” in its name, is not an endorsement by Etsy.
Read the provider’s privacy and retention terms, as well as the terms for your Claude account. Shop data passes through that provider to Claude; connecting does not automatically make it private or guarantee it will never be retained.
There are also community projects on GitHub. Some list useful tools. Unless someone qualified has reviewed the code, do not run it against your real shop. And do not copy setup code from older READMEs: Etsy’s app and authentication rules have changed, and some defaults are now stale.
Step 2: Sort out Etsy app access, if the provider needs it
Some hosted providers use their own approved Etsy app. Others ask you to bring your own. Only register an app if your provider actually requires it.
Etsy’s current developer docs describe two paths:
- Seller App. Recommended for connecting your own active shop in good standing, if you are eligible and do not already have an active app. Register at etsy.com/developers/register-seller-app. It is for your own shop only, and there is an eligibility check, so do not count on instant approval.
- Personal App, then Commercial Access. For tools that access other sellers’ shops. If you run a service for several shops, this is the path, and it is the provider’s job to hold the right approval. You cannot reuse your own Seller App to manage every client’s shop.
The app gives you a keystring and a shared secret. These are entered in the provider’s protected credential settings, on the server side. Never in a Claude chat. Never in a Project file. Never in an email to a “helpful” stranger.
Your provider supplies a callback URL for Etsy’s authorisation flow. If you are bringing your own app, add it to the app’s registered redirect/callback URLs in Etsy’s developer settings and save. It must be HTTPS and match exactly, including any trailing slash. Copy the live callback from your provider’s current dashboard or docs, not from memory or an old blog post.
Step 3: Approve only the scopes you need
When you authorise the server through Etsy’s sign-in, Etsy asks you to approve scopes, which are named permissions. Start small:
| Scope | What it allows | When |
|---|---|---|
| listings_r | Read listings, including non-public ones | Start here |
| shops_r | Read shop details and sections | Start here |
| transactions_r | Read sales and orders | Only for sales work |
| listings_w | Create and edit listings | When ready to edit |
| shops_w | Edit shop details, including sections | For section work |
| listings_d, transactions_w and unrelated profile or address scopes | Deleting listings, changing sales data or accessing extra personal data not needed for this job | Leave out |
Behind the scenes, a well-built server handles Etsy’s sign-in flow (OAuth with PKCE, for the technically curious) and refreshes the access token automatically, roughly every hour. If refresh fails, you sign in again. If you are briefing a developer, those are the checks to ask about.
Step 4: Add the server to Claude
In Claude on the web, go to Customize > Connectors, choose + Add, then Add custom connector. Then:
- Give it a name you will recognise, such as “Etsy shop (provider name)”.
- Paste the remote MCP server URL from your provider. It must be reachable from the internet. A
localhostaddress on your laptop will not work here. - Choose Continue and review the authentication Claude detects.
- For Authentication, choose Sign in now or when needed. If the provider supports it, leave the OAuth client on Use Claude’s published identity (Recommended). Follow any provider-specific settings exactly.
- Choose Add, then Connect, and sign in to the provider.
Never leave tools that can reach your private shop data publicly accessible. For a provider using OAuth, do not switch to No sign in to get past an error. If it instead requires a fixed credential, follow its protected connector-settings instructions, never put that credential in a chat. Etsy app credentials and Claude-to-server authentication are different settings.
On a Team or Enterprise plan, an owner usually adds the connector first under Organization settings > Connectors > Add > Custom > Web, then members connect their own accounts.
Claude Desktop can also run local MCP servers. That is a separate setup with its own instructions. It is not interchangeable with the web steps above.
Etsy keystring, shared secret and tokens live in the server's protected credential store. Never in a chat, Project file or prompt.
Step 5: Set tool permissions before you use it
Go to Customize > Connectors, select your Etsy connector and open Tool permissions. Each tool can be Always allow, Needs approval or Blocked.
- For your first week, block every write tool. Audit only.
- When you are ready to edit, set write tools to Needs approval, so each change shows up for you to confirm.
- Keep anything you never want used blocked.
Writing “do not change prices” in a prompt is a good habit. It is not a security boundary. Real limits are the scopes you approved on Etsy, the tools the server exposes, and the permissions you set in Claude.
Turning the connector off for a conversation (via + > Connectors) and revoking the app’s access in your Etsy account are separate controls. If you want it gone, do both.
Optional: add Etsy’s Dev MCP for API questions
If you or a developer are building or debugging, you can add Etsy’s documentation server the same way: Add custom connector, paste https://mcp.api.etsycloud.com/mcp, and connect. It is a developer reference only. It answers questions about endpoints and fields. It will not read your listings, confirm your shop or change anything.
Verify before anything changes
Turn the connector on for a fresh conversation and run this read-only check:
“Using the Etsy connector only, first list every tool you have and say which ones read documentation and which read or change my shop data. Then tell me the connected shop name, shop ID and currency. Fetch five of my actual listings with listing ID, state, price and full tag list, and count the tags on each. Do not fetch any buyer names, addresses or emails. Make zero changes.”
- Linen Apron, Cross-back, 13 tags
- Drawstring Linen Pouch Set, 9 tags
- Embroidered Tea Towel, 13 tags
- Linen Napkins, Set of 4, 11 tags
- Zip Pouch, Botanical Print, 6 tags
Now open Shop Manager and compare. Same shop? Same prices? Same tag counts? Do the IDs match the listing URLs? If anything is off, stop and fix the connection before you touch a write tool.
The safe batch rule
Here is the paragraph to remember.
Each edit on Etsy is a separate update. A batch can stop partway. There is no universal undo.
If Claude updates 30 descriptions and listing 19 fails, you may have 18 new, 12 old and no rollback button. So every bulk job climbs the same ladder.
Why read back from Etsy rather than trust the tool? Because a tool can report success while a value was trimmed, ignored or rejected. Ask Claude to fetch the listing again and compare it with the proposal, field by field. Then glance at the live listing yourself.
Etsy also limits how many API requests an app can make. Check your app’s assigned limits rather than assuming a universal number. Your provider should slow down and retry safely when Etsy returns a rate-limit error; small batches help, but do not guarantee you will stay below the limit.
Once you have approved a proposal, make the first live edit deliberately:
“Apply only the approved description changes for these three listing IDs. Leave titles, tags, prices, quantities, shipping and listing status unchanged. Show me the write actions for approval. After each update, fetch the listing again and compare the saved description with the proposal. Log success or failure by ID and stop if anything unexpected changes.”
Use case 1: Audit and rewrite descriptions in your exact voice
Start with an audit. It is read-only and always revealing.
“Review every listing in the export (or every active listing via the connector, paging through all of them and telling me the total). For each, flag: description under 80 words, missing materials, missing dimensions, missing care instructions, and any claim not supported by the product facts sheet. Show listing ID, title and flags. Sort by the listings I mark as best sellers first. Do not draft anything yet.”
Missing and unverified are different problems. An empty “care” line is a writing job once you have the facts. A description that says “organic” with no evidence on your facts sheet is a checking job. Claude should never fill a gap by guessing.
Then rewrite, one listing at a time at first:
“Rewrite the description for listing [ID] using the voice guide. Open with what it is and who it is for in one or two plain sentences. Then a short paragraph on how it feels and is used. Then a scannable details block: materials, size, care, processing time, personalisation, all from the facts sheet only. Keep any facts already in the current description that the facts sheet supports. Show current and proposed side by side.”
Current
- Title
- apron linen apron kitchen apron gift for her gift for mum handmade apron
- Opening
- Beautiful high quality apron perfect for any occasion!!
- Details
- Not stated
Proposed
- Title
- Cross-Back Linen Apron, Handmade Kitchen Apron with Pocket, Washed Linen
- Opening
- A soft, washed-linen apron that crosses at the back, so there is nothing to tie and nothing pulling at your neck.
- Details
- Materials, size, care and processing time pulled from the facts sheet, with "needs checking" where it is silent.
On titles: Etsy’s guidance favours clear, readable titles over keyword soup. Lead with what the item is, in the words a buyer would use, grounded in the real product. No invented certifications, no materials you do not use. And remember Etsy has no separate SEO meta description field like Shopify; your title, tags and description do that work together.
Use case 2: Fix your tags without losing the good ones
Etsy allows up to 13 tags per listing, each 20 characters or fewer, including spaces. Use accurate, relevant multi-word phrases a shopper might type. Aim to use all 13 without padding the list with unrelated terms or misleading brand names.
The catch with editing tags through a tool: an update usually sends the full list of tags you want, not “add these two”. Get it wrong and the good tags quietly vanish. So the job is a deliberate swap, not a pile-on.
“For listing [ID], show the current tags with character counts. Mark each as keep, weak or unnecessarily repetitive. A phrase is not weak just because its words also appear in the title. Propose replacements for irrelevant tags or near-identical phrases that add no useful meaning. Each must describe the real product in 20 characters or fewer. Show the full final list, no more than 13 tags. Do not claim search volumes or rankings.”
After the update, read the tags back from Etsy and count them. If a tag was too long or not accepted, it may simply be missing. Check that “pottery apron” is honest too: only use it if the apron genuinely suits potters, per your facts sheet.
Use case 3: Check prices against real margins
Pricing is where Claude earns its keep as a patient calculator, not as an oracle. It cannot know what your time is worth or what buyers will pay. It can make your own numbers visible.
Give it a cost sheet with, per product: materials, packaging, your making time and the hourly rate you want, and the fees you actually see on your Etsy statements, such as transaction, payment processing and, where it applies to you, Offsite Ads. Add any shipping you subsidise, returns or remakes, and how you handle tax and currency. Then:
“For each listing in the cost sheet, calculate the cost per unit including my labour, and the margin at the current price, showing each fee as a separate line using the rates in my cost sheet. Flag any listing below my target margin. For variations, use each variation’s own price, not the ‘from’ price. Show the working. Suggest a price range only where the margin is short, and do not apply anything.”
Here is how that might read for one fictional listing. These numbers are invented to show the layout, not real Etsy fees or a recommendation.
| Line | Amount | Source |
|---|---|---|
| Price | 18.00 | Listing |
| Linen, zip, thread | 3.40 | Cost sheet |
| Packaging | 0.85 | Cost sheet |
| Labour, 25 minutes | 6.25 | Your target rate |
| Etsy and payment fees | Per your statements | Check current Etsy fees |
| Left before fees, shipping, returns and tax | 7.50 | 18.00 − 3.40 − 0.85 − 6.25; not final profit |
Three warnings worth a moment:
- Variations have their own prices. A pouch set may have a different price per size or print. Make sure Claude reads the variation prices, not just the headline “from” price.
- Money comes with structure. Through the API, prices arrive as an amount, a divisor and a currency. A good server converts them, but sanity-check the first few: a price that suddenly looks 100 times too big is a units problem, not a pricing insight.
- Comparisons use public information only. You can look at similar listings yourself or through permitted API tools. Do not scrape Etsy. Your connector cannot read a competitor’s private costs, sales breakdown or analytics, so “they charge less” is a weak argument on its own.
If you decide to change a price, and the listing has variations, read the inventory checks in use case 7 first.
Use case 4: Plan shop sections that make sense
If you come from Shopify, reset your expectations. Etsy shop sections are not smart collections. Per Etsy’s help centre:
- You get up to 20 custom sections, plus “All items”.
- Section names are up to 24 characters.
- Each listing sits in one section. Moving it removes it from the old one.
- Empty sections are not shown to shoppers.
- There are no automatic, rule-based sections and no draft status for sections.
So the work is a mapping exercise. Claude is good at it.
“Using the listings and my sales notes, propose a set of shop sections of 24 characters or fewer, no more than 12 to start. Map every listing from its current section to its proposed section in a table with listing ID. Flag listings that could fit two sections and tell me your reason for the choice. Base groupings on what the products are and how buyers use them, not on trends you cannot see.”
To do it by hand in Shop Manager: go to Listings, then Sections. For your first one, choose Organize your listings, type a name and Save. For more, use Manage > Add section. To move listings, tick them, choose Editing options > Change section, pick the section and Apply.
Through a live connection, creating a section needs an API action and the shops_w scope. Assigning a listing uses the listing’s shop_section_id field (older tutorials mention a different field name). But the server has to expose those tools. AnythingMCP’s current guide, for example, lists reading shop sections and assigning listings to a section, but no tool for creating a section. With that kind of setup, create the sections in Shop Manager, then let Claude handle assignments after your approval. Always check your own server’s tool list.
Seasonal ideas are fair game for brainstorming: a “Christmas Table” section in November, say. Base them on your own sales history and calendar, and empty or retire them when the season ends.
Use case 5: Make sense of your sales
Sales data comes from two places: your sold orders CSV download, or a live server’s order tools using the transactions_r scope. Either way, a few rules keep the numbers honest:
- Minimise buyer information before it reaches Claude. Redact exports first. For live tools, ask whether the server can remove personal fields before returning results to the model. “Do not show addresses in your answer” is not the same as preventing the tool from sending them.
- Cover the whole period. Order lists come in pages. Ask Claude to page through the full date range and report the count, then compare with Shop Manager.
- Fix the date range, timezone and currency before you ask anything.
- Separate paid, cancelled and refunded orders. And keep units, orders, revenue and profit apart. They are four different numbers.
- Revenue is not profit. Receipts are not a set of accounts. For fees and refunds, use your Etsy payment and ledger statements.
Sold orders or transactions_r
What sold, when, at what price, and what was cancelled or refunded.
Statements and ledger
Fees, refunds and payouts. The basis for margin, not the order list.
Etsy Stats, by hand
Visits, search terms and ad results. Not automatically in the API; share a redacted summary.
A good first sales prompt:
“Read the whole sold orders file for 1 July to 30 September, UK time, GBP, and confirm the count. If using live order tools instead, fetch every page in that date range. Exclude cancelled orders, account for refunds using the statement data, and flag missing information. By listing, show units sold, distinct orders and revenue, clearly stating how refunds are treated. Join this to the full catalogue so you can identify listings with no sales. Which ten drove most revenue, and which best sellers have the weakest descriptions or fewest tags from the audit? Do not display buyer names or addresses.”
That last step is the useful one: it turns sales into a fix list. The best sellers with thin listings go to the top.
Use case 6: Draft new listings, photos and digital files
Claude can turn your notes into a complete listing draft. Through a live connection, creating a listing and publishing it are separate steps: a new listing can start as a draft, and making it active is a deliberate change of state. Publishing and renewing may involve Etsy fees, so check Etsy’s current fees before you do it in bulk.
“Draft a new listing for a linen bread bag from my notes below. Give title, description in my voice, 13 tags of 20 characters or fewer, materials, and a checklist of what Etsy will need before it can go live: photos, category and attributes, processing time, shipping profile, and whether it is physical or a digital download. Mark anything my notes do not cover as needs checking. Do not create or publish anything.”
Photos are yours to take. Claude can help with a shot list (“flat lay with loaf, hanging on a hook, close-up of the drawstring, scale shot in hand”) and alt text that describes what is really in each photo. For digital products such as a printable sewing pattern, files and file details differ from physical shipping, so make sure the draft reflects what you are really selling.
Use case 7: Catch shipping and stock mistakes
These are dull, quiet errors that annoy buyers. Ask for a read-only check first:
“Check listings and variation inventory for zero or suspiciously high quantities, processing times that conflict with my policies, and variation combinations that are switched off. For physical products, also flag missing shipping profiles; do not apply that check to digital downloads. Report the listing states and IDs included in your check. Flag missing tool access rather than inventing results. Do not change anything or guess real stock levels.”
A crucial warning for listings with variations. On Etsy’s API, updating inventory means sending the full set of products and variations, not just the one you want to change. Leave something out and it can be removed. So for any price or quantity change on a listing with variations:
- Have Claude read the current inventory first: every combination, its SKU, price, quantity and whether it is enabled.
- Change only the value you mean to, and keep every other combination exactly as it was.
- Pilot one listing, then read it back and check every variation, not just the one you edited.
Claude does not know how many aprons are on your shelf. Stock numbers come from you.
Use case 8: Content, marketing and knowing when to get help
With your listings and sales in the Project, Claude becomes a decent marketing partner. Realistic jobs:
- Social posts drawn from your actual listings and voice, for you to review and post yourself.
- A seasonal plan built on your own past sales by month.
- Product stories for your own website or newsletter, if you have one.
- A checklist for Etsy Ads, based on the ad figures you share from Stats.
Check whether a paid channel can even work
Before spending on ads anywhere, share your margins, your current conversion figures from Stats and any ad costs you know. Then ask:
“Using my margins and conversion figures, work out the most I could pay for a click on each of my top five products before I lose money on the sale. Compare paid search and paid social where we have channel-specific evidence. If you only have the shop’s average conversion rate, label it an assumption and show several scenarios, not a channel forecast. Include agency costs and our target profit. Flag missing information and do not change campaigns.”
The basic check is money available for advertising per order × purchase conversion rate = maximum cost per click. If you have £8 available and 2% of those visitors buy, that is £0.16 per click just to cover advertising. Your target profit needs its own allowance, and the real conversion rate from new paid visitors may be very different from your shop average.
For many handmade items, the honest answer is that some paid channels do not add up at current prices. That is useful to know before you spend, not after.
If a channel does look viable, a specialist agency or freelancer can often get you there faster. They bring account access, platform experience and judgement Claude does not have. Claude is a good way to prepare a sharp brief for them, not a replacement.
Stay inside Etsy’s rules
A live connection does not change what you are allowed to do. Two lines not to cross:
- Buyer data is not a marketing list. Etsy limits how sellers can use buyer information, and email or WhatsApp marketing needs proper consent. Grow your own audience through permitted, opt-in routes, such as a sign-up on your own website.
- Do not route Etsy sales around Etsy. Using Claude to nudge Etsy buyers to buy elsewhere to avoid fees breaks Etsy’s rules.
And just because an MCP server is installed does not mean anything should run on its own. No unattended schedules. No automatic messages to buyers. You start the work, and you approve the changes.
Where ChitChatBot fits
Claude helps with the work behind your shop. ChitChatBot can help with customer conversations on your own website and social channels. That is a separate setup from the Etsy MCP connection described here, not a claim of a native Etsy connector or an Etsy Messages integration.
If you also sell from your own website or social accounts, a customer-facing chat on your website can answer questions using the product and order information you have configured, with consent-based follow-up. Our ecommerce page has more on that. Keep Etsy conversations and Etsy-originated transactions within Etsy’s rules.
Your first week
- Day 1: Build the Project. Instructions, voice guide, facts sheet, policies.
- Day 2: Export and audit. Dated listing CSV with your own IDs added. Read-only audit.
- Day 3: Three rewrites. Best sellers first. Paste them in and check the live listings.
- Day 4: Tags and margins. Tag swaps on the same three listings. Run the cost sheet check.
- Day 5: Decide on live. Only then consider a connection, read-only first. Plenty of sellers never need it.
Common mistakes and quick fixes
“Claude says it updated my listing, but nothing changed.” You may be in a Project without a live connection, or using the Dev MCP server, which only reads documentation. Ask Claude to list its tools.
“The connector added but cannot see my shop.” Check you authorised the right Etsy account, that read scopes were approved, and that the connector is switched on for this conversation. If the token expired and did not refresh, sign in again.
“It worked yesterday, now it asks me to sign in.” Access tokens are short-lived. Normally the server refreshes them. If refresh fails, re-authorise through Etsy.
“Callback or redirect error during setup.” The callback URL does not exactly match. Copy it again from your provider’s current dashboard, trailing slash included.
“I added a scope and nothing changed.” New scopes need a fresh Etsy authorisation.
“My good tags disappeared.” The update sent a shorter list. Restore from your saved values, then always propose the full final list of up to 13.
“A variation vanished after a price change.” The inventory update left it out. Restore it from your saved inventory in Shop Manager, and only update inventory with the full current set.
“The audit only covered some listings.” Paging stopped early. Ask for the total count and compare it with Shop Manager.
“The advice seems out of date.” Your export is old. Download a fresh one and replace the file.
“A listing or uploaded file tells Claude to ignore my rules.” Treat that text as shop data, not an instruction from you. Keep write tools restricted and review the actual proposed action before approving it.
Frequently asked questions
Is there an official Etsy connector that lets Claude edit my listings?
We have not verified an Etsy-operated connector for managing a shop from Claude. Etsy does publish a Dev MCP server, but it searches Etsy’s API documentation and does not call the Etsy API or touch your shop. To read or edit live listings you need an MCP server built on the Etsy Open API v3, from a provider you trust or a developer you hire.
Can I use the Etsy Dev MCP URL to update my shop?
No. The Etsy Dev MCP server at mcp.api.etsycloud.com/mcp is a developer reference. It helps Claude answer questions about Etsy’s API. Etsy states that it does not call the Etsy API directly, so it cannot read your listings, verify your shop or make changes.
Do I need a live connection to get value from Claude?
No. A Claude Project with your voice guide, product facts, cost sheet and a dated listing export covers a lot: description rewrites, tag reviews, pricing checks and section plans. You then make the approved changes yourself in Shop Manager. A live connection saves copying, but adds setup and risk.
Can I edit my listing CSV and upload it back to Etsy?
Do not plan on it. Etsy’s listing download is for your records and analysis. It covers active listings only and does not include everything about each listing, such as variation structure. Make approved changes in Shop Manager, or through a reviewed live connection that has the right write tools.
Is it safe to give Claude my Etsy login or API keys?
Never paste your Etsy password, API keystring, shared secret or tokens into a Claude chat or Project file. A proper setup has you approve access through Etsy’s own sign-in, and the provider stores credentials in its protected settings. Claude then connects to the provider separately.
Can Claude use my Etsy buyer list for email or WhatsApp marketing?
Not just because the data is reachable. Etsy’s rules limit how sellers use buyer information, and marketing messages need proper consent under privacy law. Grow your own list through permitted, opt-in routes, and do not use Claude to move Etsy sales off Etsy to avoid fees.
Can Claude undo a batch of changes on Etsy?
Not automatically. There is no universal undo. Each change is a separate update, so a batch can stop partway. Save the current values first, pilot three listings, work in small batches, read results back from Etsy and keep a log so you only retry the failures.
Sources
All sources checked 23 October 2026. Product screens and policies change; follow the current official pages.
- Etsy: Dev MCP server
- Etsy: Developer documentation and app access
- Etsy: Authentication and scopes
- Etsy: Shop management tutorial
- Etsy: Listings tutorial
- Etsy: Open API v3 reference
- Etsy: Register a Seller App
- Etsy Help: How to download your listing information
- Etsy Help: How to use tags to get found in search
- Etsy Help: How to create and manage shop sections
- Etsy: Seller policy, buyer information and off-platform transactions
- Claude Help: Creating and managing Projects
- Claude Help: Custom connectors using remote MCP
- Claude Help: Connector tool permissions
- AnythingMCP (third party, not endorsed or tested): Connect Etsy to Claude