Connect an AI assistant (MCP)
Use SKUFlow from Claude, ChatGPT, Cursor and other assistants over MCP: connect, choose toolsets and handle approvals.
SKUFlow runs an MCP server, so AI assistants such as Claude, ChatGPT and Cursor can work in SKUFlow for you: look up a customer, draft a quote, invoice an approved quote and send it. The assistant uses the same API as the app, with your permissions, and everything it changes is in the activity log.
MCP server URL: https://app.skuflow.ai/api/mcp (Streamable HTTP). Settings → Developers →
Connect an AI assistant shows the exact URL with copy buttons and ready-made snippets.
Connect an AI assistant in Settings → Developers
Screenshot coming soon
Connect
You connect with an API key (any client) or by signing in with SKUFlow (OAuth, for Claude.ai, Claude Desktop connectors and ChatGPT). Settings → Developers says whether sign-in with SKUFlow is switched on for your account; until it is, use an API key. Make the key in Settings → Developers first (Authentication).
Claude.ai and Claude Desktop (sign in with SKUFlow): open Settings → Connectors → Add custom connector, paste the MCP server URL and sign in with SKUFlow. Choose the business the connector may use and approve it.
Claude Code (API key): run this in a terminal:
claude mcp add --transport http skuflow https://app.skuflow.ai/api/mcp \
--header "Authorization: Bearer skf_…"Claude Desktop with an API key: add this to claude_desktop_config.json, then restart Claude:
{
"mcpServers": {
"skuflow": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://app.skuflow.ai/api/mcp",
"--header",
"Authorization: Bearer skf_…"
]
}
}
}The MCP server accepts only an API key or a SKUFlow sign-in token, never a browser session, so a web page can't drive it on your behalf.
Tools
Every API endpoint your connection may call is an MCP tool, named after the endpoint with dots as
underscores (customers.list → customers_list). Each endpoint in the
API reference shows its tool name. Tools your role, key permissions or
access level don't allow are not listed, and refused if called.
Workflow tools
These do a whole job in one call, the way a person would ask for it:
| Tool | What it does |
|---|---|
quote_from_description | Drafts a quote from a plain description ("150 navy tees, 2-color front print, 1-color back"), matching each item to your pricebook. Lists anything it couldn't match. Sends nothing. |
invoice_quote_and_send | Invoices an approved quote (or reuses the invoice it was already turned into) and sends it to the customer by email or text. |
customer_overview | A customer's record, Customer 360 and open items: open quotes, unpaid invoices with the balance, new requests. |
workflows_storeForCustomer | Creates a draft online store for a customer. In the stores toolset. |
See Workflows for their inputs.
Toolsets
Hundreds of tools are too many for most assistants, so tools come in toolsets. Without ?toolsets=
you get the default set: about 40 everyday tools (customers, requests, quotes, pricebook,
invoices, payments, messages, stock, reports and the workflow tools) plus two search tools,
find_operations (search everything your connection may do, in plain words) and call_operation
(run any operation by name). Together they reach everything.
To list more tools, add toolsets to the URL:
| Toolset | Holds |
|---|---|
customers | Customers, contacts, addresses, notes and files, Customer 360, portal links, consent, feedback |
sales | Requests, quotes (with decorated product lines priced from the decoration matrix) and artwork proofs |
invoices | Invoices, payments, refunds and deposits, invoice links, online payments, the Stripe account |
team | Team members and roles, team chat |
pricebook | Pricebook categories and items, stock by location, vendors, purchase orders |
catalog | Products and variants, supplier connections, browsing and importing supplier styles, supplier stock, pricing rules |
stores | Online stores, their products and prices, access and invites, store orders |
orders | Orders, the production board, presses and their capacity, shipping labels and tracking |
decoration | Decoration methods and the price matrix, the artwork library, designs with mockups and prices, the online designer |
marketing | Campaigns, segments, referrals, automations, message templates, email designs, messages, the website, QR codes, reviews, phone |
ads | Google Ads and Meta ad accounts, campaigns and what ads returned |
reports | Dashboard, every report, call reports, the event log, the activity log |
settings | The business, lead sources, custom fields, the request form, business units, channels, integrations, webhooks, imports, the plan |
Examples:
https://app.skuflow.ai/api/mcp?toolsets=sales,invoices: those toolsets plus the search tools.https://app.skuflow.ai/api/mcp?toolsets=core,orders: the default set plus orders and production.https://app.skuflow.ai/api/mcp?toolsets=all: every tool (several hundred).https://app.skuflow.ai/api/mcp?tools=search: onlyfind_operationsandcall_operation, for clients with a small tool limit.
Any tool your connection may use can be called even when it isn't listed.
What a tool returns
Every result has the answer in result and a url: a link to the matching SKUFlow screen (the
quote, the customer, the invoice), so the assistant can offer "Open in SKUFlow". Tools are marked
read-only or destructive, so assistants know which ones to ask you about.
SKUFlow screens in the chat
In ChatGPT and Claude (web, desktop and mobile), a few tools show an interactive SKUFlow screen in the conversation instead of text: a customer's 360 view, a quote with its options, an invoice, and revenue or money-owed charts. You can edit a quote line, send a quote or invoice, or record a payment right there, each after your OK. Other clients get the same data as text.
Approvals
Tools that move money, delete, contact customers or change access don't just run:
- Assistants that support MCP's built-in confirmation forms ask you in the app.
- Claude.ai, Claude Desktop and ChatGPT don't, so SKUFlow asks you itself: you get a notification, approve the request on the AI assistant approvals page, and tell the assistant. It calls the tool again and it runs once.
- The riskiest actions (deletes, refunds, inviting people, connecting outside systems, payouts, campaigns) always wait for approval in SKUFlow, in every client.
The assistant's own "Allow" button doesn't count as SKUFlow's approval. See Approvals for the details.
One business per connection
- An API key works in the business it was made in.
- A sign-in connection works in the business you chose when you approved it. To use another business, connect again and choose it.
Limits
MCP tool calls count against the same rate limit as REST calls: 600 a minute per key, and per person per connected app.