integrations tools litium

    Litium MCP for your AI agent

    Cogny's Litium integration exposes 23 tools (21 read, 2 write) to an AI agent over MCP. The same tools are available on every plan, from your own AI client or inside the Cogny app.

    • 21readonly reads data.
    • 2writecreates or changes something.
    • 0destructivedeletes, removes or replaces something.

    Over MCP your own AI client asks before it runs a write. To take a tool away from your agent, block it in Settings → Integrations. Plans, approvals and limits

    set it up.

    Add Cogny to your AI client once, then connect Litium in Cogny. Every Litium tool below appears in the client.

    • Claude CodeRun claude mcp add --transport http cogny https://app.cogny.com/mcp, then authorise in the browser.
    • Claude.aiSettings → Connectors → Add custom connector, URL https://app.cogny.com/mcp, then log in and pick your workspace.
    • ChatGPTSettings → Apps → Advanced settings → Developer mode → Create app, URL https://app.cogny.com/mcp, authentication OAuth.
    • CursorIn Cogny, Settings → Data & Integrations → Connect AI Clients shows the block to paste into .mcp.json, with an API key.
    • CodexRun codex mcp add cogny --url https://app.cogny.com/mcp.

    Full setup, and how to undo it

    Notes

    Litium connects with your store URL (the domain that serves the Litium back office, the same host as /Litium/swagger) and a back-office service account, created under Settings → System settings → Service accounts. Works with Litium 7 and Litium 8; Cogny detects which one your store runs.

    Orders, sales summaries, best sellers, products, variants, categories, stock, price lists, CMS pages and customers are read only. The service account needs read permission for Sales, Products, Customers, Globalization and Websites.

    The only writes are SEO text: set_category_seo and set_page_seo set the SEO title and meta description of one product category or one CMS page, in one language (a culture such as sv-SE). Nothing else on the category or page changes, other languages are left alone, and repeating a call with the same text changes nothing. For these, give the service account write permission for Products (categories) and Websites (pages); without it the read tools still work and the SEO tools answer with a permission error. The SEO tools are ask-first until you allow them in Settings.

    A page change goes to the published page straight away and to the page's draft (the version editors work on in the back office), so a later publish from the back office keeps the new text. Cogny never publishes the draft itself, so an editor's unpublished edits stay unpublished.

    get_category and get_page show the current SEO title and description in every language; list_categories and list_pages show them for one language, so you can find categories and pages with missing or weak SEO text before changing them. The tools warn when a title is longer than about 60 characters or a description longer than about 160, where search results usually cut them.

    Known gaps

    • SEO text for products and variants can't be written yet; only categories and CMS pages.
    • No other writes: no orders, prices, stock, product content, URLs or redirects.
    • The SEO tools follow the Litium 8 Admin Web API. Litium 7 stores accept partial updates from version 7.4, but may not expose CMS pages to the API; there the page tools say so. Stores older than 7.4 can't take the SEO writes.
    • A page whose draft can't be updated is still changed live, and the tool says the draft kept the old text: publishing that draft from the back office would bring the old text back.
    • No bulk tool: one category or page and one language per call.
    • No index / follow (_indexThePage, _followLinks) or sitemap settings.

    what each tool does.

    Read 21 · only reads data

    • get_storeReadStore setup: channels, markets, currencies, countries, languages, websites, API generation.
    • list_ordersReadList sales orders, newest first, optionally within a date window.
    • count_ordersReadCount sales orders in a window (and optionally in one state) without listing them.
    • get_orderReadGet one sales order with line items, customer, delivery and payments.
    • get_sales_summaryReadOrders and revenue per period, in the store's base currency.
    • get_top_productsReadBest-selling articles in a window, ranked by revenue, quantity or order count.
    • search_productsReadPage through base products (the catalog's parent articles).
    • get_productReadGet one base product by article number or systemId, with its variants.
    • search_variantsReadPage through variants (the sellable SKUs; article number = `id`).
    • get_variantReadGet one variant by article number or systemId, with stock per inventory and prices per price list.
    • list_categoriesReadList product categories with their URL, SEO title and meta description (all, or the children of one category).
    • get_categoryReadGet one category (fields, product links, parent, SEO text per language) by readable id or systemId.
    • list_inventoriesReadList the store's inventories (warehouses) with their ids and country links.
    • get_inventory_itemsReadStock levels per variant in one inventory.
    • list_price_listsReadList product price lists (id, currency, channels).
    • get_price_list_itemsReadPrices per variant in one product price list.
    • list_pagesReadList the store's CMS pages with their URL, status, SEO title and meta description.
    • get_pageReadGet one CMS page with its SEO title and meta description in every language.
    • search_customersReadPage through customer persons (B2C accounts and B2B contacts).
    • get_customerReadGet one person by customer number (readable id) or systemId, with addresses and organizations.
    • call_admin_apiReadRead any Admin Web API endpoint not covered by a dedicated tool.

    Write 2 · creates or changes something

    • set_category_seoWriteSet the SEO title and/or meta description of one product category in one language.
    • set_page_seoWriteSet the SEO title and/or meta description of one CMS page in one language.

    Exact input schemas come from tools/list once Litium is connected; the free plan is enough to check. Missing something? Your agent can ask for it with request_feature.