Integration

Afosto integration

Afosto is a commerce platform for retail and wholesale (orders, warehouse, point of sale). Read orders, invoices, contacts, products, parcels with track and trace, warehouses and stock levels, and build an order through a cart: create it, add items, customer, addresses, phone number and a note, then confirm it into an order. Amounts are integers in cents and dates Unix milliseconds. Afosto's API is GraphQL; only these operations are exposed (no order editing, returns, picklists or catalog management). Authentication is an API key created in Afosto (Settings, API), sent as a Bearer token.

Connect Afosto How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Afosto

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.

Cart, 4 operations

confirm_cartConfirm cartPOSTConfirms a cart and turns it into a real order in Afosto (the cart must have no validation errors). Returns the new order's id, number, status, total in cents and date.
create_cartCreate cartPOSTCreates an empty cart, the start of an order: then add items, customer, addresses and phone, and confirm_cart turns it into an order. channel_id is required unless the API key is a storefront token.
get_cartGet cartPOSTReturns one cart: totals in cents, currency, customer, items, delivery method and address, billing address and validation errors (a cart with validation errors cannot be confirmed).
set_cart_noteSet cart notePOSTAdds the customer's note to a cart.

Billing address, 1 operation

add_billing_address_to_cartAdd billing address to cartPOSTSets the billing address of a cart: a new address or an existing one by id. Returns the cart's billing address.

Contact, 1 operation

get_contactGet contactPOSTReturns one contact (personal data): name, email, number, guest, blocked, identified and verified flags, locale, the merchant's internal notes, tags and recent orders.

Customer, 1 operation

add_customer_to_cartAdd customer to cartPOSTAttaches a customer to a cart: an existing contact (contact_id) or a new one, which this call creates in Afosto (email, given and family name, guest flag). Returns the cart's customer.

Inventory, 1 operation

list_inventoryList inventoryPOSTLists stock per SKU and warehouse with cursor paging, optionally for one SKU or one warehouse: quantity on hand, available, reserved, unavailable, committed and expected.

Invoice, 1 operation

get_invoiceGet invoicePOSTReturns one invoice: number, totals in cents, currency, addressee, billing address, lines, payment status and date, the orders it covers and the URL of its PDF.

Items, 1 operation

add_items_to_cartAdd items to cartPOSTAdds items (SKU and quantity) to a cart and returns the cart with its items and totals in cents.

Order, 1 operation

get_orderGet orderPOSTReturns one order: number, status (CONCEPT, OPEN, CLOSED), cancelled flag, totals in cents, currency, dates, customer, phone, delivery method and address, billing address, items, payments, invoices and tags.

Orders, 1 operation

list_ordersList ordersPOSTLists orders with cursor paging (first, after), optionally only those of a customer email, some order numbers or ids, or a creation date range. Each has its id, number, status, total in cents, currency, date and customer.

Parcel, 1 operation

get_parcelGet parcelPOSTReturns one parcel: number, status (OPEN, ANNOUNCED, IN_TRANSIT, DELIVERED, READY_TO_COLLECT), track and trace number and URL, the orders it carries and its dates.

Parcels, 1 operation

list_parcelsList parcelsPOSTLists parcels with cursor paging (first, after), or finds one by its track and trace number: number, status, track and trace number and URL, dates.

Phone number, 1 operation

add_phone_number_to_cartAdd phone number to cartPOSTSets the phone number of a cart: a new number with its country code, or an existing one by id.

Product, 1 operation

get_productGet productPOSTReturns a product by SKU: label, brand, MPN, GTIN, slug, categories, image URLs, HS code, country of origin and its prices per price list (amount and original amount in cents).

Products, 1 operation

get_productsGet productsPOSTReturns several products by SKU: label, brand, MPN, GTIN, slug, categories, image URLs and dates.

Shipping address, 1 operation

add_shipping_address_to_cartAdd shipping address to cartPOSTSets the delivery address of a cart: a new address or an existing one by id. Returns the cart's delivery address.

Warehouses, 1 operation

list_warehousesList warehousesPOSTLists the warehouses with cursor paging: id, label, type (MANAGED or EXTERNAL), number of positions, location and dates.

Use Afosto from Claude Code, Cursor or Codex

Connect Afosto in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Afosto 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 Afosto

Create your workspace
Sign up free. Nothing to install.
Connect Afosto once
Add your Afosto connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.