Skip to content

Connectors · Category

Commerce MCP servers for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to BigCommerce, Extensiv 3PL Warehouse Manager, Linnworks and Flipdish and more: 40 Commerce connectors and 9,781 actions behind one endpoint, 4,690 read, 3,825 write and 1,266 that wait for a confirmation. 17 ready-made plans sit in the store.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

  • 40connectorsevery one a signed file
  • 9,781actions4,690 of them read
  • 1,266wait for a yesdestructive, confirmed first
  • 17ready-made plansinstallable by name

Commerce

Every Commerce connector.

Each page lists every action, what you provide to connect it, the prompts to try and the plans ready to install.

Counts are the number of actions in each connector's service file. Names are the vendors' own; no endorsement is implied.

One name across them

Learn it once. Ask every Commerce system.

The same job has the same name in each of these connectors. An agent learns commerce.order.list once, and actionlake maps it to whichever Commerce systems you connected.

one read, every system
do {
  action: "commerce.order.list", limit: 50,
  intent: "one list across every connected Commerce system"
}
# a read fans out to every connected system
# with that name and merges the results;
# a write always names one service

One name · how many Commerce connectors answer

commerce.order.list30 of 40
commerce.order.get29 of 40
commerce.product.list26 of 40
commerce.product.get24 of 40
commerce.product.update22 of 40
commerce.product.create22 of 40

Entities they share, so ask can line them up

  • commerce.orderA confirmed purchase by a customer33
  • commerce.productSomething the tenant sells — a good, a plan or a service32
  • commerce.customerThe buyer side of a transaction, which may be a person rather than a company17
  • commerce.warehousePlace stock is held and shipped from13
  • commerce.storeOne shop, channel or sales site12
  • identity.userA person who works for the tenant and can be assigned work8
  • asset.supplierParty an asset was bought from6
  • crm.companyA business the tenant works with6

Across your systems

Commerce, joined to everything else.

One ask fetches from two systems, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

ask
ask {  intent: "which Extensiv 3PL Warehouse Manager companies have invoices in ConnectWise PSA, and how many each",  steps: [    { action: "extensiv_3pl_warehouse_manager.customers.customers.list", as: "co", input: {}, limit: 100, max_pages: 5 },    { action: "connectwise_manage.invoices.list", as: "inv", input: {}, limit: 100, max_pages: 5 },    { join: {        left: "co",        right: "inv",        on: "crm.company",        group_by: "co.name",        select: ["co.name", "count(inv.id) as invoices"]    } }  ]}
Example. Run it through check first: it validates the steps and prices them, and it is free.

Give your agent every Commerce system.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.