Cin7 Core and your AI assistant: the verdict, tools, and guardrails
Cin7 Core, wired to your AI assistant through a hosted MCP connector: verdict first, tools second, guardrails throughout.
Every system here gets an honest, affirmative path: verified and instant, buildable and provisioned, human-assisted, or a done-for-you conversation. Zero dead ends.
Where Cin7 Core stands today
Orders, inventory levels, and supplier records answer most operational questions; a connector puts them one question away.
Also searched as cin7, dear systems, dear inventory. The vendor's developer documentation lives at www.cin7.com.
What a Cin7 Core connector would expose
The proposal you review during intake, separated into Read and Write. Nothing writes without asking you first.
Extracted from the vendor's API docs and human-reviewed before going live. Writes start one notch stricter.
- search_orders
Find sales or purchase orders by number or status
- get_inventory_levels
Check stock levels by item and location
- list_suppliers
List supplier records and terms
- get_order
Fetch one order with line items
- update_order_statusconfirm
Change an order's fulfillment status
fields: status, status_note
- adjust_inventoryconfirm
Post a stock adjustment for an item
fields: quantity, reason
- add_order_noteconfirm
Attach a note to an order
fields: body
- void_orderdestructivedry-run
Void an order and release its allocations
fields: id, reason
Every write asks first: it pauses on a preview of the exact change and runs only when you approve it, before anything reaches Cin7 Core. Turn off anything you never want your AI to touch.
From "Cin7 Core" to a working connector URL
Designed for operators, not developers. You never read API docs, manage tokens, or touch a line of code.
- 01
Name it
A 30-second eligibility check confirms your AI client accepts a custom connector URL, then you pick the software. This page pre-fills that step.
- 02
Describe what you need
Plain language, not configuration. What should the assistant be able to look up, and what should it be able to change?
- 03
Review your Connector Blueprint
The exact Read and Write tool list, before you pay anything. Every write ships on in confirm mode and asks before it runs, every tool is individually toggled, and anything destructive carries a distinct warning.
- 04
Deploy and paste the URL
You get a hosted connector URL plus paste-in instructions matched to your AI client, and a live test panel that confirms the connection.
Cin7 Core runs as a one-account connector
Cin7 Core supports a single credential, so the connector runs in Solo mode: it acts as one account and says so in plain language at auth time and in the dashboard. megamcp's own activity log still separates who did what by connection token.
You paste an API key generated in Cin7 Core. It is encrypted at rest, sent only to Cin7 Core's API, and destroyed within 24 hours if you cancel.
Write access to Cin7 Core your IT team will approve
Every write asks first: it pauses on a preview of the exact change and runs only when you approve it. Nothing reaches the upstream system unapproved.
Confirm mode
Enabled writes run through Multi Round-Trip Requests: the tool pauses, shows a human-readable preview of the exact change, and only proceeds with approval. Nothing reaches Cin7 Core on the model's intent alone.
Guardrails
Any tool can be turned off. Field-level constraints restrict what can be touched, per-tool rate limits are enforced at the gateway edge, and destructive operations ship in dry-run, demonstrating what they would do until you graduate them.
Activity log
Every tool call is logged: who, what, when, result. Write actions and confirmations are highlighted, redaction controls decide how much argument data is stored, and the log is append-only, with updates and deletes refused by the database.
Connecting Cin7 Core: the specifics
Can my AI assistant write to Cin7 Core?
Yes, with guardrails. Write tools work out of the box in confirm mode: every write asks first, pausing on a preview of the exact change before anything reaches Cin7 Core. Destructive operations ship in dry-run and never execute until you graduate them, and you can turn off any tool you never want touched.
Is it safe to connect Cin7 Core to an AI assistant?
Safety is the architecture, not a setting. Every write asks first: it pauses on a human confirmation with the exact change previewed before it reaches Cin7 Core. Destructive operations demonstrate in dry-run and never execute until you graduate them, any tool can be turned off, and every call lands in an activity log with redaction controls.
If my team uses a Cin7 Core connector, whose name is on the actions?
Cin7 Core supports a single credential, so the connector runs in Solo mode and discloses it plainly: the connector acts as one account, stated at auth time and in the dashboard. megamcp's own activity log still preserves per-connection traceability, because every connection has its own token.
Which AI clients work with a Cin7 Core connector?
Any client that accepts a remote MCP connector URL: Claude (Free, Pro, Max, Team, and Enterprise), ChatGPT on paid plans with developer mode enabled, Cursor, and other MCP-compatible clients. Team and Enterprise workspaces may need an admin to allow custom connectors first.
How long until a Cin7 Core connector is live?
Typically 24 to 72 hours. The mapping is generated from the Cin7 Core API documentation and human-reviewed before it goes live.
Anything specific to the Cin7 Core API worth knowing?
Yes. From our index notes on Cin7 Core: Account ID plus application key headers; docs subdomain not verified.
More ERP systems
Same category, same connector quality. Every one gets an honest verdict.
Connect Cin7 Core. We take it from there.
Start a 14-day free trial, no card: live reads plus 3 supervised writes, each executed only after you approve it.