Channekt › AI and MCP
Native MCP supportRun every sales channel from your AI assistant
Connect Channekt to ChatGPT, Claude, Cursor or any MCP-compatible assistant to inspect orders, inventory, listings, sales and sync issues - then safely update stock, prices, listings and fulfilment with permission-based approvals.
Which SKUs have different stock between my shops?
Four listings are advertising a quantity Channekt does not hold. These are the figures each shop was last sent, not a live read.
DEMO-MUG-01 is the one that costs money - the web shop is advertising six of something you have none of. Shall I prepare a correction for you to approve?
Your assistant asks Channekt, not six marketplaces
One secure Channekt connection gives your AI assistant controlled access across every channel you sell on. Ask questions in plain language, compare channel data, prepare changes and approve actions without switching between dashboards.
Already normalised
One status vocabulary, one currency, one shape for an order or a listing, whatever channel it came from. Your assistant does not have to reconcile a different idea of "fulfilled" per channel, because Channekt already did.
No marketplace credentials
Your assistant never holds a channel credential, because it never talks to a channel. It holds one Channekt token, scoped to what you allow, and you can revoke it on its own without signing anybody out.
Bounded answers
Every list is paginated and capped. There is no way for a prompt to become a full catalogue export, and a partial answer says that it is partial rather than being reported as the whole picture.
Everything your assistant can look at
Orders
Orders across every shop, with lines, quantities, normalised statuses, totals and shipment state - plus a summary of what is waiting, bucketed by how long it has been waiting. Customer contact details are never returned.
Products and stock
Search the catalogue by SKU, barcode, brand or what a product is missing. Read stock per warehouse: what can be sold, what is on the shelf, what is promised to orders, what is on its way.
Listings
What each product looks like on each shop: status, the price that shop is charging in its own currency, the quantity it is advertising, and any error it gave.
Channel health
Whether each connection's credential still works, when each kind of sync last ran and how it ended, and what is queued or failed.
Sync issues
Everything Channekt could not do at a shop, newest first, grouped by channel and by cause - each in the words a merchant needs rather than an internal error.
Sales
Orders, units and revenue by period and by shop, with the period before it for comparison. Orders that could not be converted into your reporting currency are counted separately rather than quietly left out.
And what it can change, once you agree
Stock
Corrections across selected SKUs and warehouses, applied through the same ledger the warehouse screens write to - so every movement has a reason and a record.
Prices
Fixed or percentage changes, previewed line by line with each price before and after in its own currency, and refused outright if any of them has moved since.
Listings
Publish products to a shop or withdraw them, after the same preflight the publishing screen runs. Partial results are reported per product, never summarised as success.
Retries
Re-send work a shop refused, for the connections and the kinds you choose. Only work that is actually eligible is included.
Shipments
Create shipments for orders that have been picked, with a check against the ones that already have one so a retry cannot produce a second parcel.
Tracking
Mark shipments as sent and tell each order's original shop the carrier and tracking number, through the same write-back the fulfilment screens use.
Five steps, and you are in every one of them
- Connect Create a connection under Settings, AI connections. Paste the address and the token into ChatGPT, Claude, Cursor or your own client.
- Choose permissions Tick what it may read. Action permissions are a separate list, closed by default, and everything an assistant can do is a subset of what you can do yourself.
- Ask, or prepare a change Questions are answered straight away. A change is prepared and stored - nothing happens yet.
- Approve You see every affected item with its value before and after, plus any warnings, and you approve or reject it in Channekt.
- Audit Every request, allowed or refused, is recorded against the connection that made it. Changes are audited exactly as they are when made by hand.
Things merchants actually ask
“Show unfulfilled orders older than 48 hours across all channels.”
One call. Counts by age bucket and by shop, with the oldest named, rather than a page per marketplace and arithmetic in between.
“Which SKUs have inconsistent stock between my channels?”
The listings advertising a different quantity from the one Channekt holds, with the moment each figure was sent so the answer can say how old it is.
“Prepare a 5% price increase for these products.”
A preview naming every SKU with its price before and after in its own currency. Nothing changes until you approve it.
“Retry today's eligible listing failures.”
The work a shop refused, re-sent through the same queue the Send button uses - reported as started, because that is what it is.
“Create shipments for these orders and write tracking back.”
Each order checked for a shipment it already has, then the carrier and tracking number sent to the shop the order came from.
“Compare sales by channel for the last 30 days.”
Orders, units and revenue by shop and by day, with the previous thirty days beside them.
What an assistant can and cannot reach
One workspace, from the credential
The workspace comes from the token and from nowhere else. No tool accepts a workspace id, so asking about somebody else's shop is not something a prompt can express.
Granular permissions
Thirteen named permissions, each granted deliberately. A read-only connection is not offered an action tool at all, and calling one by name is refused before anything runs.
Approvals you cannot skip
Publishing, withdrawing, shipping, bulk changes and anything above a threshold always wait for a person - whatever the workspace setting says. An assistant cannot approve its own proposal.
Immediate revocation
A revoked connection stops on its very next request. So does one whose owner has left the workspace or had their role changed: the membership is read every time rather than trusted from the token.
A full audit trail
Every call, allowed or refused, recorded against the connection that made it and kept for twelve months. Changes are audited exactly as a change made by hand is, and marked as having come through a connection.
Idempotent actions
An execution is keyed, so a client that retries a timed-out call does not do the work twice. A plan is refused if the state has moved since you saw the preview.
Any MCP client
Channekt is a standard remote MCP server over Streamable HTTP, with protocol versions 2025-06-18, 2025-03-26 and 2024-11-05. We have tested it with ChatGPT, Claude and Cursor; anything else that speaks the protocol connects the same way. Channekt is not affiliated with, endorsed by or certified by any of them.
Frequently asked
Can the assistant change things without asking me?
Not unless you decide it may. New connections are read-only, and the workspace default is that every change waits for a person. If you turn on the permissive setting, only a small single-item change or a retry of work that already failed can run unattended - publishing, withdrawing, shipping and anything larger still wait, whatever the setting.
What does it do with my customers' data?
Orders come back with a customer's name and, on a single order, the town and country it is going to. No street address, no email address, no telephone number. Those stay in Channekt, on the order screen.
Does my assistant get my channel credentials?
No. It holds one Channekt connection token and never talks to a channel. No tool returns a channel credential, and none can be reached through the endpoint.
What happens when somebody leaves the company?
A connection borrows one person's rights and Channekt reads their membership on every single request. Removing them, or changing their role, takes effect on the connection's next call rather than when the token eventually expires.
Can it tell me a listing is live when it is not?
Publishing happens at the marketplace and takes minutes. Channekt returns an operation id and reports it as started; it never describes a queued marketplace operation as finished. Ask for the channel's status to see how it ended.
Is it included in my plan?
Yes, on every plan. Reading works whatever your subscription is doing; making changes needs an active subscription, like every other change in the product.
Connect your assistant
Start a 14-day trial, connect a shop, and ask your own assistant what is happening across it.