Integration

AmeriCommerce integration

AmeriCommerce (the Cart.com Online Store platform) runs B2B and B2C online stores. Read and manage orders with their lines, payments, shipments and addresses, change an order status the way the admin does (status emails included), and read quotes; set the stock of a product or variant; manage customers and their address book; manage products, categories, variant stock and coupon codes, gift certificates and subscriptions; and read order statuses, customer types, manufacturers, warehouses, stores and reviews. Lists page with page and count, sort with sort, and take filters with operators (eq, not, like, startwith, gt, gte, lt, lte) on the fields each list offers. Writes expose the commonly used fields of each record. Content (blogs, pages), marketing rules, carts, price calculators, shipping configuration, payment processing, theme import and users are not offered. Authentication is an access token generated in the store admin (Tools, Apps and Addons, API Apps and Integrations), sent in the X-AC-Auth-Token header, whose scopes decide what it can read and change (for example read_orders and orders); store_domain is your store's SSL domain.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in AmeriCommerce.Built from the 55 AmeriCommerce tools below, on the connection you add once.

What you can do with AmeriCommerce

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Address, 4 operations

  • create_addressCreate addressPOSTAdds an address to a customer's address book. customer_id and country are required.
  • delete_addressDelete addressDELETEDeletes a customer address by its id.
  • list_addressesList addressesGETLists customer address book entries, 100 per page by default (page, count), sorted with sort; the filters (customer_id) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).
  • update_addressUpdate addressPUTUpdates only the fields you send on a customer address.

Coupon code, 4 operations

  • create_coupon_codeCreate coupon codePOSTCreates a coupon code within a campaign; campaign_code and coupon_code are required.
  • delete_coupon_codeDelete coupon codeDELETEDeletes a coupon code by its id.
  • list_coupon_codesList coupon codesGETLists coupon codes, 100 per page by default (page, count), sorted with sort.
  • update_coupon_codeUpdate coupon codePUTUpdates only the fields you send on a coupon code.

Customer, 4 operations

  • create_customerCreate customerPOSTCreates a customer (or updates the one whose id is sent). email and store_id are required.
  • delete_customerDelete customerDELETEDeletes a customer by its id.
  • list_customersList customersGETLists customers, 100 per page by default (page, count), sorted with sort; the filters (email, last_name, updated_at) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).
  • update_customerUpdate customerPUTUpdates only the fields you send on a customer.

Order, 4 operations

  • create_orderCreate orderPOSTCreates an order (or updates the one whose id is sent). customer_id, order_status_id and the two order address ids are required; add lines with create_order_item.
  • delete_orderDelete orderDELETEDeletes an order by its id.
  • list_ordersList ordersGETLists orders, 100 per page by default (page, count), sorted with sort; the filters (customer_id, order_status_id, ordered_at, updated_at) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).
  • update_orderUpdate orderPUTUpdates only the fields you send on an order. To change the status with its status events (customer emails), use update_order_status instead.

Order item, 4 operations

  • create_order_itemCreate order itemPOSTAdds a line (product, quantity, price) to an order.
  • delete_order_itemDelete order itemDELETEDeletes an order line by its id.
  • list_order_itemsList order itemsGETLists order lines, 100 per page by default (page, count), sorted with sort; the filters (order_id) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).
  • update_order_itemUpdate order itemPUTUpdates only the fields you send on an order line.

Product, 4 operations

  • create_productCreate productPOSTCreates a product (or updates the one whose id is sent) with its item number, name, category, status, prices and stock.
  • delete_productDelete productDELETEDeletes a product by its id.
  • list_productsList productsGETLists products, 100 per page by default (page, count), sorted with sort; the filters (item_number, item_name, updated_at) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).
  • update_productUpdate productPUTUpdates only the fields you send on a product, such as price or quantity_on_hand.

Category, 3 operations

  • create_categoryCreate categoryPOSTCreates a category; name is required.
  • list_categoriesList categoriesGETLists categories, 100 per page by default (page, count), sorted with sort.
  • update_categoryUpdate categoryPUTUpdates only the fields you send on a category.

Gift certificate, 3 operations

  • create_gift_certificateCreate gift certificatePOSTCreates a gift certificate with its code, amounts and recipient.
  • list_gift_certificatesList gift certificatesGETLists gift certificates, 100 per page by default (page, count), sorted with sort.
  • update_gift_certificateUpdate gift certificatePUTUpdates only the fields you send on a gift certificate, such as its balance (current_amount).

Order shipment, 3 operations

  • create_order_shipmentCreate order shipmentPOSTRecords a shipment on an order with its carrier, tracking numbers and tracking URL.
  • list_order_shipmentsList order shipmentsGETLists order shipments, 100 per page by default (page, count), sorted with sort; the filters (order_id) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).
  • update_order_shipmentUpdate order shipmentPUTUpdates only the fields you send on an order shipment, such as tracking numbers.

Inventory, 2 operations

  • list_inventoryList inventoryGETReturns the quantity in stock of one product or variant combination, found by one of product_id, variant_inventory_id, item_number, gtin or item_name.
  • set_inventorySet inventoryPOSTSets the stock of one product or variant combination to an exact quantity, identified by one of product_id, variant_inventory_id, item_number, gtin or item_name; returns the new quantity.

Order address, 2 operations

  • list_order_addressesList order addressesGETLists order addresses (the billing and shipping addresses saved on orders), 100 per page by default (page, count), sorted with sort; the filters (customer_id) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).
  • update_order_addressUpdate order addressPUTUpdates only the fields you send on an order address.

Order payment, 2 operations

  • create_order_paymentCreate order paymentPOSTRecords a payment on an order (it records the payment, it does not charge a card).
  • list_order_paymentsList order paymentsGETLists order payments, 100 per page by default (page, count), sorted with sort; the filters (order_id) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).

Order status, 2 operations

  • list_order_statusesList order statusesGETLists order statuses, 100 per page by default (page, count), sorted with sort.
  • update_order_statusUpdate order statusPUTChanges an order's status the way the admin does, triggering the order-status-changed events such as the customer notification email.

Subscription, 2 operations

  • list_subscriptionsList subscriptionsGETLists subscriptions (recurring orders), 100 per page by default (page, count), sorted with sort; the filters (customer_id) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).
  • update_subscriptionUpdate subscriptionPUTUpdates only the fields you send on a subscription: next renewal date, interval, shipping method, addresses, notices, or is_enabled to pause it.

Variant inventory, 2 operations

  • list_variant_inventoryList variant inventoryGETLists variant inventory records (stock per combination of variants), 100 per page by default (page, count), sorted with sort; the filters (product_id) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).
  • update_variant_inventoryUpdate variant inventoryPUTUpdates only the fields you send on a variant inventory record, such as its stock (inventory).

Customer type, 1 operation

  • list_customer_typesList customer typesGETLists customer types (price levels), 100 per page by default (page, count), sorted with sort.

Customers, 1 operation

  • get_customerGet customerGETReturns one customer by id; expand fills nested collections and fields limits the fields returned.

Manufacturer, 1 operation

  • list_manufacturersList manufacturersGETLists manufacturers, 100 per page by default (page, count), sorted with sort.

Orders, 1 operation

  • get_orderGet orderGETReturns one order by id; expand fills nested collections and fields limits the fields returned.

Product review, 1 operation

  • list_product_reviewsList product reviewsGETLists product reviews, 100 per page by default (page, count), sorted with sort; the filters (product_id) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).

Product variant, 1 operation

  • list_product_variantsList product variantsGETLists product variants (options such as size or color), 100 per page by default (page, count), sorted with sort; the filters (product_id) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).

Products, 1 operation

  • get_productGet productGETReturns one product by id: item number, name, prices, stock and status.

Quote, 1 operation

  • list_quotesList quotesGETLists quotes, 100 per page by default (page, count), sorted with sort; the filters (customer_id) take an optional operator prefix (eq, not, like, startwith, gt, gte, lt, lte).

Store, 1 operation

  • list_storesList storesGETLists stores of the account, 100 per page by default (page, count), sorted with sort.

Warehouse, 1 operation

  • list_warehousesList warehousesGETLists warehouses, 100 per page by default (page, count), sorted with sort.

Use AmeriCommerce from Claude Code, Cursor or Codex

Connect AmeriCommerce in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its AmeriCommerce operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect AmeriCommerce

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect AmeriCommerce once

    Add your AmeriCommerce connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

AmeriCommerce integration FAQ

What can you do with the AmeriCommerce integration?

LiveContext exposes 55 operations on AmeriCommerce, covering address, coupon code, customer and order.

Popular integrations

Browse the whole catalog