AI Connector (MCP)

Availability — The AI connector uses the same access gate as the REST API: it requires a Growth or Business tier. Access is further limited to the modules in your subscription.

Knowledge ERP exposes a Model Context Protocol (MCP) server, so AI assistants that support custom connectors — Claude on the web, Claude Desktop, Claude Code, and MCP-capable IDEs — can work with your account's data directly: looking up stock, drafting sales orders, creating customers, checking rental availability, and more.

Connecting from Claude #

1. In Claude, open Settings → Connectors → Add custom connector.
2. Enter your Knowledge ERP URL followed by /mcp (for example https://app.knowledgeerp.com/mcp).
3. Claude redirects you to Knowledge ERP to sign in (if you aren't already) and shows a consent screen naming the account the connection will act on.
4. Approve, and the connector appears in Claude with the full tool list.

There is nothing to configure per tool — the assistant discovers the available tools automatically, and a built-in guide teaches it the conventions (UUIDs, money in cents, pagination, document workflows, and the product/unit vocabulary — a Product is the catalogue entry; a Unit is one tracked item of it).

What the assistant can do #

The connector mirrors the REST API's coverage: customers and CRM, inventory (products, units, transfers, reorder suggestions), sales documents (orders, quotes, invoices, payments), purchasing, manufacturing, equipment loans and rentals (including lifecycle transitions and availability checks), appointments, surveys, reports, and automation approvals.

What bounds it #

Three limits apply to every tool, and they are the same three that apply to the REST API:

• Your account. The assistant can never see another account's records.
• Your subscription. Tools for a module you don't have return a clear message instead of data.
• Your own permissions. The connector acts as you, not as an administrator: it can do exactly what you could do in the app, and no more. A salesperson's assistant can raise a quote and cannot delete a product, and a role held at one location cannot book stock in at another.

The third is worth being concrete about, because it is what makes connecting an assistant a smaller decision than it sounds. Authorizing the connector does not widen your access — it hands your existing access to a tool that can use it. Narrowing someone's role narrows their assistant at the same moment, with nothing to revoke separately.

When a tool is refused, the assistant is told which permission was missing, so it can tell you what to ask an administrator for rather than guessing.

Rate limits #

Each connected user gets their own allowance — 120 tool calls a minute on Growth, 300 on Business — rather than sharing one account-wide budget. An agent is metered like the person it acts as, so one colleague's long-running task cannot ration everyone else's, and an account that wants more agent throughput adds the seats to run more agents.

Going over returns a standard 429 with a Retry-After header, which well-behaved clients wait out on their own.

Attribution and undo #

Every change the assistant makes is recorded in the change history exactly like a change made in the app — attributed to the user who authorized the connection, marked with an mcp source, and undoable from the UI. If an assistant makes a change you didn't want, open Change History and roll it back.

Disconnecting an assistant #

Account Administration → Integrations → AI Assistants lists what is connected, who approved it, and when — with a Disconnect button. Anyone can see and disconnect the assistants they approved themselves; anyone who can manage API tokens sees the whole account's, which is what you need when somebody leaves.

Use it rather than only removing the connector inside Claude. Removing it there makes that client forget the connection, but the access it was granted is still live — connections refresh themselves for up to 30 days. Disconnecting here stops it immediately and stops it renewing, and reconnecting means approving it again.

A connection stays listed for as long as it can still renew itself, which is what the date beside it means. An assistant nobody has used for a week is still a live connection until that date passes, and is still worth disconnecting.

Signing out of Knowledge ERP does not affect a connection either way.

Notes for other MCP clients #

The server implements streamable HTTP MCP with OAuth 2.1 dynamic client registration at the standard well-known endpoints. Any client that supports remote MCP servers with OAuth can connect using the same /mcp URL.