Litium runs a large share of the Nordic mid-market — fashion and lifestyle brands, B2B wholesalers, retailers with several markets and currencies under one back office. Until today none of that data was reachable from a Cogny agent. Now it is. Litium is a live MCP integration, joining Shopify, WooCommerce, Wix and Abicart as the fifth e-commerce platform in the catalog.

No OAuth dance, no developer app: one service account created in the Litium back office, pasted once into Settings → Cogny Managed MCPs together with your store URL. Works on Litium 7 and Litium 8 — the proxy detects which generation of the Admin Web API your store runs and normalizes orders to one shape, so the same tools and templates work on either.

TL;DR

Litium is live now. Connect it with a service account from your warehouse Settings → Cogny Managed MCPs.
19 tools across store setup, orders, catalog, stock, prices and customers. All of them are reads — this first release writes nothing back to your store, and the call_admin_api escape hatch only permits GET and search/lookup POSTs.
Two aggregation tools do the heavy lifting server-side: get_sales_summary pages through every order in a window and returns orders, revenue ex/inc VAT, shipping, discounts, items and average order value per day, ISO week or month in your base currency — with by-channel, by-country, by-currency and by-status breakdowns; get_top_products ranks best sellers by revenue, quantity or order count.
Multi-currency stores are handled: foreign-currency orders are converted with the currency's exchange rate (Litium 7: the currency table; Litium 8: the rate stored on the order), and native amounts are reported per currency alongside.
The ecommerce scheduled template now recommends itself for Litium stores, same as the other four platforms.
Works from any MCP client on app.cogny.com/mcp, and from Bash via the Cogny CLI.
Included in Cogny Solo ($9/mo); bring your own agent and the standard MCP tools run under fair use.

What you can do with it

Area	What Claude can do
Sales	Sum orders and revenue per day/week/month in the base currency; split by channel, country, currency and order status; count orders by window and state; rank best-selling articles
Orders	List and filter orders by date window, order/payment/delivery state (Litium 7) or free text; read full orders with line items, customer, delivery and payments; look an order up by its order number
Catalog	Page through base products and variants with name, URL, brand and active flag per language; read a product with all its variants; walk the category tree
Stock & prices	List inventories and read stock per variant (filter by article number, in-stock only); list price lists and read prices per variant
Customers	Page through persons, read one with addresses and organizations
Setup	Channels (with their GA4 / GTM ids), markets, currencies with exchange rates, countries with VAT rates, languages, websites

In plain terms: "How did revenue per week trend since August, and how much of it was the Finnish channel?" "Which ten articles sold best in the last 30 days, and are any of them out of stock?" "Which paid orders from this week are still not delivered?" "What does article 104211-001 cost in the EUR price list?" The answers come straight from Litium's Admin Web API, not a CSV export.

Why the aggregation tools matter

Litium's Admin Web API pages orders at a few hundred per call and returns complete orders — rows, deliveries, payments — every time. An agent that tries to compute monthly revenue by listing orders burns its context window on line items it doesn't need. get_sales_summary and get_top_products do that loop inside the proxy instead — up to 20,000 orders per call, with a truncated flag that tells the agent to split a wider window by month — and hand it a few hundred bytes of totals. The ecommerce template is written to reach for them first.

Litium 7 and Litium 8

The two generations differ in exactly one area that matters for analysis: sales orders. Litium 7 serves them at /sales/orders as OrderCarrier objects with integer state codes and a currency id; Litium 8 serves them at /sales/salesOrders as SalesOrder objects with typed rows, a currency code and the exchange rate on the order — and keeps the order state off the object entirely. The proxy probes once per store, caches the answer, and returns the same normalized record either way (order number, date, status name and code, totals, currency, channel, country, customer, delivery, payments, rows). get_store reports which generation it found as api_flavor, so an agent knows whether to expect state codes.

Two ways in: chat or scheduled

Ask interactively from any MCP client, or enable the ecommerce template (E-Commerce Performance Signals) as a scheduled prompt — it now recognizes Litium alongside Shopify, WooCommerce, Wix and Abicart and maps its phases onto the Litium tools automatically.

Prefer the terminal? The Litium CLI page shows every tool as a npx @cogny/cli tools call one-liner an agent can script.

How to connect it

In the Litium back office, open Settings → System settings → Service accounts and create an account (name it e.g. Cogny). Give it read permission for Sales, Products, Customers and Globalization. Copy the username and password — the password is shown once.
In your warehouse Settings → Cogny Managed MCPs, click Connect on the Litium card.
Enter the store URL (the host that serves your back office, e.g. https://www.yourstore.com), the username and the password.

The credentials are stored encrypted and scoped to the single workspace. Each call exchanges them for a short-lived JWT with the OAuth2 client-credentials grant on your own store (/Litium/OAuth/Token, or /connect/token on newer installs) and sends it as a bearer token — the proxy never stores the token beyond its lifetime. Disconnect any time with one click, and revoke the service account in the back office if you ever stop using Cogny. Service accounts cannot log in to the back office or the storefront, which is exactly why Litium recommends them for integrations.

On trust

Every tool carries MCP behavior annotations, so Cogny's UI and Claude.ai connectors know that all of them read and none of them write. There are no order, catalog, price or customer mutations in this release, and the escape hatch refuses anything but GET and /search / /keyLookups POSTs. When we add writes, they will arrive as separately named tools behind Cogny's standard approval gate — the same way the Abicart and Shopify connectors work.

If your store — or your client's — runs on Litium, this is the connector that puts it on the same footing as the Shopify and WooCommerce stores in your portfolio. Connect it from your Cogny dashboard and ask your first question.