In the AI tool you already use
Claude Code, Claude Desktop or any other MCP client can look up sale orders, stock and reference data in your own ERP.
The Tathven MCP server lets AI tools outside the ERP, such as Claude Code, Claude Desktop or any MCP client, read your organisation’s records through read-only tools. Nothing is reachable until an administrator switches it on, chooses the user the tools act as, and chooses which tools they see.
An add-on · off until an administrator switches it on
For teams that already work in Claude or another AI tool, and want it to look things up in the ERP’s own records.
Claude Code, Claude Desktop or any other MCP client can look up sale orders, stock and reference data in your own ERP.
It works on its own. It does not need the ERP’s built-in AI assistant, and the assistant does not need it.
MoreA large result comes back as a link to a saved file instead of inline text.
An administrator controls it on one page: Admin › Settings › AI Assistant › MCP Server.
An organisation is open to MCP clients only once an administrator turns it on. Turn it off and every client is cut off.
Clients act as one IAM user you choose, best a dedicated one. Only that user’s access keys are accepted, and every look-up runs as that user.
Choose which groups clients may see: reference data, sales, stock. A client sees only the tools of the groups that are on. A group switched on for a user without its rights is not offered, and the page says so.
Issue one access key per client from the same page. The secret is shown once. Revoke a key to cut that one client off.
Switching off, changing the groups or revoking a key takes effect within about a minute, with no restart.
All 21 tools only read. None of them can change a record.
A tool group is offered only when the chosen user holds its rights: Sales needs Sale Orders, Stock needs Items and Stock Balance. Stock documents also follow that user’s own document rights.
Before it serves anything, the server asks the ERP whether your organisation is open to MCP, whether the key belongs to the chosen user, and which tool groups are on.
One server serves every organisation and holds no customer passwords. Each client brings its own organisation key and access key.
Two keys can be active per user at a time, so you can issue a new key, move the client over and revoke the old one without a gap.
The credential travels in a header. A credential put in the address is ignored.
21 read-only tools in three groups.
Units and branches, countries, currencies, departments and their roles, units of measure and dispatch modes.
Sale orders by code, customer, item, unit, date or status; an order with its lines; order statuses, what has shipped and what remains; order totals for a date range; subscriptions and coupons.
MoreThe item catalogue and each item’s record; balances by unit and department; purchase orders, goods receipts, goods issues and other stock documents, with their lines.
MoreAn owner or administrator does all four.
Create a dedicated IAM user and grant it Read on what the tools should see: Sale Orders for sales; Items and Stock Balance for stock (plus Purchase Orders, Goods Receipts and Goods Issues for stock documents). A group whose rights the user lacks is not offered.
Under Admin › Settings › AI Assistant › MCP Server, open the organisation to MCP clients, choose that user and the tool groups, and save.
Name the key after the client, issue it and copy the secret. It is shown only once.
Paste the ready-made configuration from the page: a Claude Code command or a JSON config. The client sends one header, Authorization: Bearer <org-key>.<access-key-id>.<secret>.
Tell us what you run today. We will show Tathven Agentic ERP working on a sample of your own data, then send a written scope and quotation — not a brochure.