Integration · WooCommerce

Connect Claude to your WooCommerce stores.

WordPress-native commerce as typed tools: orders, refunds through the payment gateway, status and address updates, products and coupons. Claude proposes; nothing changes on a store until you sign it off — per client store, on the record.

Start free

Claude Desktop · Claude Code · ChatGPT connectors · Gemini CLI · any MCP client

Claude Desktop · mcp.datavessel.io
> order #7731 came back damaged — refund it through the gateway
wc_get_order … €62.15, paid via Stripe
wc_create_refund €62.15 → waiting for your sign-off
✓ approved from the inbox · 1 row written to the ledger
The tool catalogue

19 typed tools. 7 of them change the store — every one behind sign-off.

The WooCommerce REST API as one typed catalogue. Reads run free; the 7 writes go through the sign-off inbox, and refunds execute through the store's payment gateway rather than as bookkeeping entries.

01

Read the store

  • Orders, products, customers
  • Sales reports and top sellers
  • Coupons
02

Run the orders

  • Refunds through the payment gateway
  • Order status and shipping-address updates
  • Customer-facing order notes with tracking
03

Keep the catalogue

  • Create products — drafts by default
  • Update names, descriptions, short descriptions
Three ways in

The same tools, wherever the work happens.

One connection; every surface reads and writes through the same typed catalogue, with the same gates.

From Claude, over MCP

Claude Desktop, Claude Code or any MCP client connects to one endpoint and sees the WooCommerce tools for the store you scope it to.

The MCP endpoint

From the terminal

The datavessel CLI runs the same catalogue as commands and ships a Claude Code plugin whose read agents are structurally blocked from writing.

The CLI

In the operations center

Policies subscribe agents to store events and schedules — Order Desk, inventory alerts, product-copy refresh — asking you first, per client store.

The use cases
Why not just an API key

An LLM with your admin credentials is a liability. This is an operations layer.

01

Writes wait for you

Raw REST keys let a model do anything, silently. Here every write pauses in the sign-off inbox — approve from the web or the mobile app — until you trust a job enough to put it on autopilot.

02

Scoped per client store

Tools are scoped to one store at execution time. An agency's clients keep their data and credentials isolated — one store's run cannot touch another's.

03

Every change in the ledger

What changed, on which store, approved by whom, for how much. Reads aren't listed — the ledger is a record of changes — and it compiles into the per-client report.

Already built on these tools

The jobs, ready to deploy.

Each ships as an agent with the policy that runs it — asking you first, per store, with every action in that client's ledger.

Questions

Asked before connecting.

How do I connect Claude to WooCommerce?

Connect the store to datavessel with WooCommerce REST API keys (a few minutes, no plugin to install), then point Claude Desktop, Claude Code or any MCP client at the datavessel MCP endpoint. Claude sees the WooCommerce tools for that store immediately.

Can Claude change my store?

Only through the 7 write tools, and every write waits in the sign-off inbox until a human approves it. Refunds go through the payment gateway, new products are drafts by default, and each approved change is recorded in the ledger.

Does it also handle the WordPress side?

Yes — WordPress is a separate connection for publishing and updating posts, used by the content and SEO agents. The store tools and the publishing tools stay distinct, each behind the same sign-off.

Does it work with ChatGPT or Gemini, not just Claude?

Yes. The endpoint is standard MCP, so any MCP client works — Claude Desktop and Claude Code, ChatGPT via connectors, the Gemini CLI, Cursor and others. Inside the operations center, agents run on whichever key you bring: Anthropic, OpenAI or Google.

What does it cost to run?

You bring your own AI key (Anthropic, OpenAI or Google) and pay the model provider directly — datavessel adds no markup on tokens. Plans are priced by connected stores, free for one store.

Is my store data used for training?

Your data is isolated per customer and scoped per store, and model calls run on your own key under your provider's terms. See the security page for the full commitments.

Every client's WooCommerce store, one sign-off away.

Connect a store, ask Claude for the first sweep, and approve what goes out — every change on the record.

Start freeAll integrations

Free for one store · 14-day trial on paid plans · no card · bring your own AI key