Documentation

626Labs Agentic Sales Connector · read-focused MCP connector for Etsy shop analytics

Connect your Etsy shop once, and your AI assistant can answer questions about how the shop is actually doing — what moved, what sold, what people said — without you opening a dashboard or leaving a browser running.

What makes it different

Etsy's API reports lifetime counters: total views, total favorites. It cannot tell you what changed since yesterday. This connector takes a daily server-side snapshot of your shop and computes the difference, so day-over-day movement exists as data for the first time.

Because snapshots run on a schedule in the cloud, your computer does not need to be on. A shop that was quiet at 3am still has correct numbers in the morning.

Getting started

Add the connector to your MCP client using the server URL https://etsy-agentic-connector.web.app/mcp.
Sign in when your client prompts you.
Visit the connect page and approve read access on Etsy's own consent screen.
Ask your assistant a question. The first daily snapshot begins that night; movement data appears once two snapshots exist.

Example prompts

Shape of the shop

"How is my Etsy shop doing right now? Give me active listings, favorites, and anything that stands out."

What moved

"What are my top 5 listings by views gained in the last day, and how many views did each actually pick up?"

Sales in a window

"Show me every Etsy order from the last week with the total revenue, and tell me if any day was unusually good."

Reputation

"Read my recent Etsy reviews and summarize what buyers keep mentioning, good and bad."

A specific listing

"Pull the details for these three listing ids and tell me whether any of them have gone expired."

Take the data with you

"Export my full Etsy snapshot history as CSV so I can keep my own copy."

Available tools

Tool	What it does	Touches your shop?
`getShopSnapshot`	Wide view of the shop: listings, counts, recent orders and revenue	Read only
`getTopMovers`	Biggest changes between snapshots, by views or favorites, over a window you choose	Read only
`getListingDetail`	Detail for up to 10 listing ids. Expired listings come back as data, not errors	Read only
`getOrders`	Orders in a date range. An empty range is an empty list, not a failure	Read only
`getReviews`	Reviews and ratings	Read only
`getTrafficSources`	Traffic breakdown from an imported dashboard CSV, clearly labeled as supplemental	Read only
`exportSnapshotHistory`	Your entire stored history as CSV, gaps included	Read only
`importSupplementCsv`	Parses an Etsy stats CSV you export yourself. Writes to this connector's store only — never to Etsy	Writes here, not Etsy
`deleteMyData`	Immediate, irreversible purge of everything stored for your shop	Destructive, here only

On honesty of numbers. Every response carries data_as_of and a source stamp, so you always know whether you are looking at a live pull, a cached value, or snapshot-derived data. A number that cannot be read is reported as unknown with a reason — never as a zero. If the connection breaks, tools say so and hand back a reconnect link instead of serving stale figures.

What it deliberately does not do

No writes to Etsy. No creating, editing, renewing, or deleting listings. No replying to reviews.
No scraping. Dashboard-only metrics arrive through a CSV you export yourself, not by driving a browser against Etsy.
No per-listing hammering. Bulk endpoints only, with a rate budget tracked per day.

Limits and known gaps

Movement data needs two snapshots. Before that, tools say insufficient_history rather than guessing.
Visits, conversion rate, and traffic sources are not in Etsy's API at all. They come only from an imported CSV, and are always labeled as supplemental. Where the API and a CSV disagree, the API is the number of record.
Orders and revenue movement is computed at shop level, not per listing, in this version.
One shop per connection currently.