AI agents

What AI agents can do in SKU.io

52 workflows across ten areas, each checked against four routes: a person in the app, the built-in AI assistant, an MCP client such as Claude or ChatGPT, and the REST API. For each one: can it read, can it write, does it get a dry run, or is it ruled out.

Last checked , against the SKU.io code

What is the SKU.io MCP server?

The SKU.io MCP server is the connection that lets an AI assistant such as Claude, ChatGPT, Cursor, Claude Code or Codex work inside a SKU.io account, at https://mcp.sku.io/mcp. It reads products, stock, orders, purchase orders and reports with what your role can already see. It writes only when you turn on Allow changes for an area when you connect, your role allows the change, and your admin allows AI changes. Writes go through hand-picked tools and a reviewed list of endpoints: it never deletes, voids or cancels, and the only thing it sends outside SKU.io is a purchase order you ask it to submit. Every write accepts a dry run and an idempotency key, and is limited to 30 a minute per connection and 300 an hour per account.

Four routes into the same account

In the app

A person clicking. Everything the role allows, deletes included. The baseline the other three are measured against.

SKU AI assistant

Built into SKU.io, on your own AI provider. It looks things up freely, and stages every change as a Confirm card that you click. It never deletes, voids, cancels, pays or sends outside SKU.io.

MCP

Your own assistant: Claude, ChatGPT, Cursor, Claude Code or Codex. Reads by default; writes per area you allow, through reviewed tools that never delete, void or cancel.

REST API

Your own code or agent, with a personal access token or OAuth app. Reaches every documented endpoint its scopes cover, writes and deletes included, with a dry-run header for most writes.

The matrix

  • Read looks it up, changes nothing
  • Write changes it directly
  • Write, dry run first can check it before saving: MCP's dry_run, or the REST API's X-Dry-Run header
  • Write after you confirm assistant: a person clicks Confirm
  • Not available refused by the code, not by a prompt

G MCP through the REST gateway (api_read / api_write): Claude, Cursor, Claude Code, Codex and ChatGPT custom connectors have it; the ChatGPT app listing does not. A the assistant's general write path: a create or update on its reviewed list of business records, staged as a Confirm card. Notes in small type name the tool or token scope the cell was checked against.

Orders and customers

Orders and customers: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
Look up an order, its lines and its status Read Read get_order_status, get_sales_order_details Read get_order_status; get_orders covers the last 90 days Read orders:read
Create a sales order Write Write after you confirm build_sales_order_payload Write, dry run first create_sales_order, always a draft Write, dry run first orders:write
Change an existing sales order Write Write after you confirm build_update_sales_order_payload; never cancels the order Not available Notes and pins only Write, dry run first orders:write
Add a note to a sales order Write Write after you confirm A Write, dry run first G Write, dry run first orders:write
Void a sales invoice or payment request Write Not available Voids stay with people in the app Not available Void and cancel are never callable Write, dry run first orders:write
Add a customer Write Write after you confirm build_customer_payload Write, dry run first G An existing match is refused Write, dry run first customers:write
Open a return (RMA) Write Write after you confirm build_rma_payload Not available Can edit an open RMA's warehouse, notes and lines Write, dry run first returns:write

Products and pricing

Products and pricing: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
Search products and read their details Read Read search_products, get_product_price Read search_products, find_product, get_products Read products:read
Create a product Write Write after you confirm build_product_payload Write, dry run first create_product Write, dry run first products:write
Update sell prices and supplier costs Write Write after you confirm A Write, dry run first update_product_pricing: prices only, never removes a tier Write, dry run first products:write
Set the components of a kit or bundle Write Write after you confirm A Write, dry run first G Only when it has no components yet Write, dry run first products:write

Inventory

Inventory: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
Stock per warehouse, with units on order Read Read get_inventory_levels Read get_inventory_levels Read inventory:read
What is about to run out Read Read get_stockout_risk Read get_stockout_risk Read Low-stock endpoints, inventory:read
Explain why our count differs from the 3PL's Read Read Reads the 3PL comparison through its API lookup Read explain_inventory_gap Read 3PL inventory endpoints, inventory:read
Adjust stock: a count, damage or found stock Write Write after you confirm build_inventory_adjustment_payload Write, dry run first adjust_inventory, 10 a minute Write, dry run first inventory:write
Start a stock take Write Write after you confirm A Write, dry run first G Always a draft Write, dry run first inventory:write
Read the send plan for FBA, WFS and TikTok FBT Read Read get_send_plan_summary, explain_send_plan_line Read get_send_plan, explain_send, compare_scenarios Read send-plans:read
Override a send plan line or create inbound drafts Write Write after you confirm build_send_plan_override_payload, build_send_plan_drafts_payload Not available Plans are edited in SKU.io Write, dry run first send-plans:write

Purchasing

Purchasing: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
Find a purchase order and when it arrives Read Read search_purchase_orders, get_purchase_order_details Read search_purchase_orders, get_purchase_order_details Read purchase-orders:read
Create a purchase order Write Write after you confirm build_purchase_order_payload Write, dry run first create_purchase_order, always a draft Write, dry run first purchase-orders:write
Send a purchase order to the supplier Write Not available Nothing is sent to the supplier Write, dry run first submit_purchase_order; your approval rules still apply Write purchase-orders:write; a dry run is refused if the send calls an outside service
Edit an existing purchase order Write Not available Refused: edit it in the app Not available Notes, pins and copies only Write, dry run first purchase-orders:write
Receive stock against a purchase order Write Write after you confirm A No negative quantities, so no un-receiving Write, dry run first G No negative quantities, so no un-receiving Write, dry run first purchase-orders:write
Record a supplier invoice Write Write after you confirm A Write, dry run first record_purchase_invoice Write, dry run first purchase-orders:write
Add a landed-cost bill and allocate it Write Write after you confirm A Write, dry run first G Refused in a locked period Write, dry run first purchase-orders:write
Add or edit a supplier Write Write after you confirm A No bank or payment details Write, dry run first G No bank details, PO email or automatic sending Write, dry run first suppliers:write

Fulfillment

Fulfillment: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
Change a fulfillment's status or lines Write Not available Status and line changes are refused Not available Status and line changes are refused Write, dry run first orders:write
Buy or void a shipping label Write Not available Label purchases and voids are refused Not available Label purchases and voids are refused Write orders:write; no dry run, it calls the carrier
Move stock between warehouses Write Write after you confirm build_warehouse_transfer_payload Write, dry run first G Create, open, ship and receive a transfer Write, dry run first warehouses:write

Accounting

Accounting: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
COGS, profitability and inventory value Read Read get_cogs_analysis, get_profitability_report, get_report Read G Read accounting:read, reports:read
Record a vendor credit Write Write after you confirm A Write, dry run first record_vendor_credit, always a draft Write, dry run first accounting:write
Record a supplier deposit Write Write after you confirm A Write, dry run first G A draft, never approved or paid Write, dry run first accounting:write
Approve or pay a supplier deposit Write Not available Payments and approvals stay with people Not available Payments stay with people Write, dry run first accounting:write
Map products and costs to GL accounts Write Not available Settings are changed in the app Write, dry run first G Points future postings; posts and syncs nothing Write, dry run first accounting:write, settings:write

Sales channels

Sales channels: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
Connected channels, channel orders and listings Read Read list_sales_channels, list_integration_instances Read G Read integrations:read
Find what is wrong with a TikTok Shop listing Read Read Through its API lookup Read diagnose_tiktok_listing Read integrations:read
Amazon reimbursement cases Write Read Through its API lookup Read get_reimbursement_cases Write recovery:read, recovery:write; no dry run, it calls Amazon

Advertising

Advertising: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
Spend, ACoS, TACoS, POAS and ad health Read Read When Advertising is switched on Read get_ad_performance, get_ad_health, get_ad_recommendations Read advertising:read
Propose a bid, budget or pause change Write Not available Use the MCP server or the app Write, dry run first propose_ad_changes; a person approves it in SKU.io Write advertising:write; no dry run, it reaches the ad platform
Approve and apply an ad change Write Not available Approvals stay with people Not available Write advertising:write, where your role allows; no dry run

B2B and wholesale

B2B and wholesale: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
Create or edit a quote Write Write after you confirm A Write, dry run first G A new quote is always a draft Write, dry run first orders:write
Send a quote to the customer Write Not available Nothing is sent to an outside party Not available Nothing is sent to an outside party Write, dry run first orders:write
Map a customer's SKUs to yours Write Write after you confirm A Write, dry run first G Write, dry run first customers:write
Add a pricing tier Write Write after you confirm A Write, dry run first G Not mapped to any channel yet Write, dry run first products:write

Warehouse

Warehouse: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
Warehouses and locations Read Read list_warehouses Read list_warehouses Read warehouses:read
Create a license plate (LPN) Write Write after you confirm A Write, dry run first G A new, empty LPN Write, dry run first warehouses:write
Put-away and location moves Write Not available Moving stock between locations is done in the app Not available Write, dry run first warehouses:write

Reports and automation

Reports and automation: what each route can do
Workflow In the app A person, by hand SKU AI assistant Built into SKU.io MCP Claude, ChatGPT, Claude Code, Codex REST API Your own code, with a token
Run a report: sales, margin, inventory value Read Read get_report, get_dashboard_kpis Read G get_orders and get_products for bulk lists Read reports:read
Read Support Insights reports Read Read Through its API lookup Read list_support_insights_reports, get_support_insights_report Read support:read
Save a view on a list Write Not available Saved views are made in the app Write, dry run first create_saved_view Write, dry run first settings:write
Draft an automation workflow Write Not available Workflows are built in the app Write, dry run first create_workflow_draft, never published Write, dry run first settings:write
Publish, switch on or run a workflow Write Not available Refused Not available Refused Write, dry run first settings:write

Ruled out on purpose

These are refused by the code on every call, whatever the agent is told and whatever you approve when you connect.

Through MCP

  • Deletes. A DELETE request is never sent, not even by a hand-picked tool.
  • Voids, cancels, archives and list replacements. Any endpoint whose path says void, cancel, archive, delete, remove, replace, reverse or unlink is refused, and so is a body that asks for the same thing on an allowed endpoint, such as a sales order update carrying canceled_at.
  • Sending anything outside SKU.io, apart from submit_purchase_order: no supplier emails, EDI, channel or 3PL pushes, label purchases, payments, or pushes to an accounting system or bank.
  • Credentials and access. Users, roles, billing, tokens, API keys and integration logins.
  • Running automations. A workflow can be drafted, never published, switched on or run.
  • Approving ad changes. An agent can propose bid, budget and pause changes; a person approves them.
  • Any endpoint nobody reviewed. api_write calls only an allowlist of reviewed POST, PUT and PATCH endpoints. A write endpoint added to the API later is refused until it is reviewed and listed.

Through the SKU AI assistant

  • Changes without you. Its API tool sends GET requests only. Every create or update waits for your Confirm, and runs as you, within your role.
  • Anything but a business record. A write must be a plain create or update, or an archive, on a reviewed list of records such as orders, quotes, products, suppliers and stock. Settings, integrations and their logins, users, billing and editing a role are refused, and so is any endpoint added to the API later.
  • Deletes, voids and cancels. Cancelling a sales order included.
  • Money and approvals. No payments, refunds or payment requests, and no approving or rejecting.
  • Sending outside SKU.io. No submitting or emailing a purchase order, quote or invoice, no channel or 3PL pushes, and no label purchases.
  • Editing an existing purchase order. Refused; edit it in the app.
  • Areas your admin switched off. Writes for sales orders, purchase orders, inventory adjustments, transfers, products, returns and customers can each be turned off for the assistant, on the generic path as well as the dedicated tool.

The safety rails

Three gates on every MCP write
The connection must hold the area's write scope (you tick it when you connect), your role must allow the change, and your admin's Allow AI assistants to make changes switch must be on. A connection with only mcp:access is read-only.
Dry runs
Every MCP write tool saves nothing with dry_run: true. On the REST API, the X-Dry-Run: true header runs a write and rolls it back, with emails, webhooks and jobs recorded but never sent. A write that would reach an outside service is refused as a dry run instead.
Idempotency keys
Up to 128 characters. Repeating a call with the same key returns the first result instead of writing twice.
Rate limits
MCP writes: 30 a minute per connection and 300 an hour per account. Inventory adjustments: 10 a minute per connection, on top. All MCP calls: 120 a minute per user. REST API: a ceiling of 1,000 requests a minute, and an optional per-token limit you set. The assistant: a per-person hourly limit your admin sets.
OAuth and token scopes
Scopes are resource:action pairs, such as orders:read or purchase-orders:write. A read-only token cannot write. A config-file MCP connection token is read-only and is refused by the regular REST API.
A record of every call
The MCP Server Activity tab lists each call with the user, the app, the tool, the result and a link to anything it created, kept for 180 days.

Questions, each with its own limits

Can an AI agent delete records in SKU.io?

Not through the MCP server or the built-in AI assistant. The MCP server never sends a DELETE request, and it refuses any endpoint whose path says void, cancel, archive, remove or replace. The assistant refuses deletes, voids and cancels, orders included. A person can still delete in the app, and your own code can delete through the REST API with a token that holds the matching write scope.

Can Claude or ChatGPT send a purchase order to my supplier?

Yes, through one tool: submit_purchase_order. It works only when you allowed Purchasing changes when you connected, your SKU.io role can submit purchase orders, and your admin allows AI assistants to make changes. Your approval rules still apply, so a PO that needs someone else’s approval comes back as approval required. Every other MCP write stays inside SKU.io.

How many changes can an AI agent make through MCP?

Up to 30 writes a minute per connection and 300 writes an hour per account. Inventory adjustments have a tighter limit of 10 a minute per connection, and they count toward the other two. All MCP calls, reads included, are capped at 120 a minute per user. A refused write costs nothing and says how many seconds to wait.

What does dry_run do?

Every MCP write tool accepts dry_run: true and saves nothing. Through api_write, SKU.io runs the change and rolls it back, returning the would-be result and the emails, webhooks and jobs it would have triggered; the named tools validate the request and return what would be sent. On the REST API, the X-Dry-Run: true header does the same run-and-roll-back on any write, except writes that reach an outside service during the call, such as ad platforms, Amazon and carriers, which are refused rather than run. The in-app assistant shows a Confirm card instead.

What happens if an agent retries the same change?

If the agent sends an idempotency_key, up to 128 characters, a repeat of the same call with the same key returns the first result instead of writing twice. It shows as Replayed on the Activity tab. Without a key, a retry is a new request, so a well-behaved agent sends one on every write.

Does ChatGPT get the same tools as Claude?

Not in the ChatGPT app listing. That profile serves only the named tools, such as create_purchase_order and adjust_inventory, and leaves out the REST gateway (search_api, describe_endpoint, api_read, api_write), because OpenAI’s review rules refuse a general-purpose executor. Claude, Cursor, Claude Code and a ChatGPT custom connector at https://mcp.sku.io/mcp get the full server, gateway included.

Can Claude Code or Codex make changes in SKU.io?

Yes, when they connect with the connector URL and sign in through the browser: SKU.io accepts the local sign-in callback that command-line clients use, and you choose which areas may change. A connection token pasted into a config file is read-only. For scheduled or bulk work, a personal access token on the REST API with the open-source agentic skills is usually the better fit.

Does the built-in AI assistant change data without asking?

No. Its own API tool sends only GET requests. Every create or update is staged as a Confirm card that shows what will be written, and nothing reaches your data until you click Confirm, as you and within your role. It only creates and updates business records. It cannot delete, void or cancel anything (orders included), approve or reject, record or refund a payment, send anything to a supplier, customer, channel, carrier or 3PL, or change settings, integrations or users. It also refuses to edit an existing purchase order.

Which token scopes does an agent need?

Scopes are resource:action pairs, such as orders:read or purchase-orders:write. A token with only :read scopes cannot write, whatever the agent tries. When you connect an MCP client, the Allow changes areas map to write scopes: Orders, Purchasing, Inventory, Products, Manufacturing, Accounting, Settings & automations, and Advertising (propose changes only). Your role permissions apply on top.

How this page is checked

Each cell was read off the SKU.io application code (commit 9f29387, checked ): the MCP server's tool list and its ChatGPT profile, the gateway's write allowlist and deny rules, the write rate limiter, the assistant's tool set and its write allowlist, and the token scope registry. Where a route has no tool for a job, the cell says so rather than guessing.

The product moves weekly, so this page carries the date it was last checked rather than a promise. For the setup steps, read Connect an AI assistant and Ask the AI Assistant. For the API, see the API reference and the open-source agentic skills. For how I run my own business through an agent, read run inventory and purchasing with AI agents.

Want to watch an agent work in SKU.io?

Bring the questions you would hand an agent first, and we'll run them live in a demo account.

Book a Demo

Founder-led demo · 2-day onboarding · no onboarding fees