Connect Ecwid to Claude Code

Have Claude edit products and move orders along in Ecwid. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Ecwid to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Ecwid, you add a Ecwid MCP server: a small hosted service that exposes Ecwid'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 Ecwid account. No API keys pasted into config files.

claude mcp add --transport http ecwid 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 Ecwid once connected?

Full read-write Ecwid access lets Claude update product details and pricing, adjust inventory counts after a stock change, apply or edit discounts, and move an order to fulfilled or shipped once you approve. The catalog and order edits that used to mean hopping into the admin happen from where you are already working.

Update a product's title, description, or price
Adjust inventory quantities after a stock count
Create or edit a discount coupon
Change an order's fulfillment status to shipped or delivered
Add a new product to a store category
Update a customer's contact details on file

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 Ecwid 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 Ecwid API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Ecwid 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 Ecwid 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 Ecwid 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 Ecwid 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 Ecwid'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 Ecwid?

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 Ecwid account it signs in with. Revoking access is one click in Ecwid.

More on the Ecwid connector

Ecwid connector for claude.ai Wix + Claude Code Etsy + 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