Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Faire to Claude Code

Let Claude update listings and move orders along in Faire. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Faire to Claude Code?

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

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

Full read-write Faire access lets Claude update product titles, wholesale prices, and descriptions, adjust inventory and case-pack quantities, accept or update orders, and mark shipments with tracking, all once you approve. The catalog and order work that meant clicking through the Faire dashboard happens where you already plan it.

  • Update a product's title, description, wholesale price, or minimum order quantity
  • Adjust inventory and case-pack quantities across a set of products
  • Accept a new wholesale order or update its status after you confirm
  • Mark an order shipped and attach a tracking number once you approve
  • Backfill tracking on an existing shipment so retailers see fulfillment status
  • Find products or orders matching a query and propose batched 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 Faire 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 Faire API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Faire 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 Faire 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 Faire 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 Faire 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 Faire'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 Faire?
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 Faire account it signs in with. Revoking access is one click in Faire.

More on the Faire connector

Faire connector for claude.aiWix + Claude CodeEcwid + Claude CodeEtsy + 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 connectorTalk to us