You already use an AI tool on your computer: Claude Desktop, Cursor or Codex. Until now it could reach a small part of your NETICS workspace: answers, customers, orders, bookings and a few more. From today it can work across the rest of it, with the access you give it and nothing else.
Set it up in three steps
Open Settings, then Integrations and API Connections, then API & Webhooks, and choose the AI tools (MCP) tab. Press Create MCP connection.
- AI tool. Pick Claude Desktop, Cursor, Codex or any other MCP client.
- Permissions. Name the connection and choose what it can do.
- Save connection key. Copy the key and the setup text, and paste the setup into your AI tool. The key is shown once.
The computer needs Node.js, which starts the NETICS tools.
Choose what it can see and change
Step 2 starts with three presets. Read only looks and changes nothing. Front desk can also take orders and bookings and add customers. Full access gives the most each area allows.
Under the presets is a new section, Everything else in NETICS. It lists the same areas as your Roles page: Conversations, CRM, Sales and orders, Ads and social media, Inventory and buying, Operations and approvals, Team and branches, My Enterprise and the rest. Each area is set to None, Read or Update, and you can open an area to choose for each item in it.
A few rules hold whatever you choose:
- Finance and payroll can be read, never changed. An AI tool cannot record a payment, raise an invoice, give a refund or change anybody's pay.
- Nobody's access can be changed through a tool. Roles, members, invitations, API keys, connectors and your payout bank account are out of its reach.
- Confidential items are given one by one. What was said on a call, a customer's spending and staff pay stay hidden unless you choose them or pick Full access, even when you can see them yourself.
The tool works as you. If you cannot do something in NETICS, neither can it, and if you leave the workspace or lose the right to create API keys, the connection stops.
Changes wait for your OK
Reading happens at once. So do small internal things: a note, a team task, an empty tag or list, a draft.
Every other change waits. Ask your AI tool to add a customer, update an order or publish a post, and it prepares the change and tells you it is waiting. Open the AI tools (MCP) tab and you will see it under Waiting for your OK, with what it will do and the details. Press Confirm and it is done, or Decline and nothing happens.
Three things keep this safe:
- Only the person the tool works for can confirm. The tool cannot say yes to itself.
- If the record changed after the tool asked, the confirmation is refused and you look again.
- A request nobody answers ends after 24 hours.
You also get a notification each time something is waiting.
For developers
The same reach is in the public API under /platform, and in the JavaScript packages from version 0.6.0: @netics/api has platformReach, platformOperations, platformDo and platformRequest, and @netics/mcp has four matching tools. See the developer platform for the rest of the API.
Two more changes make checkout on your own website safer:
- An order sent again after a failed network request or a page refresh no longer becomes a second order. If the order names its customer and is identical to one sent in the last two minutes that is still unpaid, NETICS returns the first one.
- From version 0.6.1,
createOrdertakes anidempotencyKey(one per bag) andcheckoutOrdertakes the pages your customer returns to after paying or cancelling.
A customer is never charged twice for one order: asking for a payment link again returns the same link, and an order that is already paid refuses a new one. Read more about orders and payments.
What it costs
MCP connections come with API & Webhooks, which is included from the Starter plan. See pricing.