Katana MRP MCP connector
The Katana MRP connector brings batches, bin locations, bin transfers, and bills of materials into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person works with live stock inside their own Katana MRP access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Katana MRP to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Katana MRP once
-
Open Connections, choose Add connection, and pick Katana MRP.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Katana MRP API key. One person generates a token in Katana MRP and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Katana MRP MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Katana MRP MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Katana MRP MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Katana MRP to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Katana MRP through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Warehouse
Move stock between bins without opening a screen
Ask for a bin transfer from receiving to the pick face, and the transfer is created in Katana MRP with each row filled in. Mark a whole set of transfers done at the end of a shift in one go.
-
Production
Check batch stock before the run starts
See which batches of a material are on hand and how much is in each before a shift begins. Adjust a batch stock line when the count on the floor does not match the record.
-
Operations
Keep bin locations matching the building
Add, rename, or remove bin locations when racking moves, so Katana MRP describes the warehouse as it stands today.
-
Engineering
Fix a bill of materials line quickly
Change a quantity or remove a component on a BOM row after a design change, without clicking through every product.
-
Finance
Trace additional costs against stock
List freight, duty, and other additional costs recorded in Katana MRP so landed cost questions are answered from the record rather than a spreadsheet.
-
Quality
Find where a batch sits right now
Pull batch stock and bin inventories for a batch number and see exactly which bins hold it before a hold or recall goes out.
Try asking
- “Which batches of steel tubing are in bin A-12?”
- “Move batch 4471 from receiving to bin B-3”
- “List additional costs recorded on last week's batches”
AI tools
Katana MRP tools for your AI agents
231 tools are ready to call through Elaichi's MCP endpoint the moment you connect Katana MRP, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Katana MRP gets you
6 screens from the product, each doing one job for your Katana MRP account.
The agent
Ask about batches and bins in plain language.
Type a question and the Elaichi Agent answers from live Katana MRP records.
- batches
- bin locations
- bin transfers
- bom rows
Ask Elaichi to work across your apps.
Which batches of steel tubing are in bin A-12?
Move batch 4471 from receiving to bin B-3
List additional costs recorded on last week's batches
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Katana MRP in every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
231 Katana MRP tools, no code to write.
Batches, bin locations, bin transfers and BOM rows, covered without building anything.
- List all Katana MRP additional costs
- Update a Katana MRP batch stock by ID
- List all Katana MRP batch stocks
- Create a Katana MRP batch
Toolboxes
Every team gets its own Katana MRP toolbox.
Warehouse, production and finance each see only the tools their work needs.
- Warehouse
- Production
- Procurement
- Finance
Shared connections
Teammates work in Katana MRP, never see a key.
One person connects Katana MRP and shares it with teams and members.
- Warehouse North
- Production
- Procurement
- Finance
Audit log
Every Katana MRP change names who made it.
When, who, what happened, type and resource, in an append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Schedules run Katana MRP work end to end.
Batches are fetched and grouped, a digest is drafted, approved, then posted back to Katana MRP.
Katana MRP digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch batches
Katana MRP
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Katana MRP
Queued
Collections and dashboards
Katana MRP stock health, computed without a model.
Four metrics, 14 days of batches created and a team breakdown, refreshed on schedule.
Katana MRP health
Refreshed 4 minutes ago · every 15 minutes · from the batches collection
Batches
1,284 ↓ 12%
Bin locations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Batches created
Last 14 days
By team
Share of activity
Warehouse North 34%
Production 27%
Procurement 21%
Finance 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Katana MRP to Claude?
In Elaichi, choose Katana MRP and paste the API key from your Katana MRP settings, then the connection is ready. In Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, so the whole thing takes a few minutes.
Does Katana MRP work with ChatGPT and Cursor as well as Claude?
Yes. Once Katana MRP is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Katana MRP once and every client picks it up.
What can an AI agent actually do with my Katana MRP data?
An agent connected to Katana MRP can look up batches and batch stock, list what sits in each bin, create and update bin transfers, tidy bin locations, edit rows on a bill of materials, and list additional costs. Short, concrete asks such as "move batch 4471 to bin B-3" work better than long paragraphs. It works with the live Katana MRP records, not a copy you have to export.
Does connecting Katana MRP give the AI everything in my inventory?
No. Every call into Katana MRP runs as the person who signed in, so an agent sees only the batches, bins, and bills of materials that person can already reach in Katana MRP. Elaichi can narrow that access further with restrictions, and it can never widen it beyond what Katana MRP itself allows.
Can I stop an agent from deleting or changing things in Katana MRP?
Yes. Restrictions in Elaichi work per action, so you can allow reading batches and bins while blocking deletion of bin locations or edits to bill of materials rows. A restricted Katana MRP action is never advertised to the AI client at all, so no prompt, however worded, can reach it.
What happens to a Katana MRP connection when someone leaves?
Offboarding that person in Elaichi ends their access to Katana MRP through every client at once. A shared Katana MRP connection keeps working for everyone else on the team. If you ever want Katana MRP gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.
Does the Katana MRP MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Katana MRP is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Katana MRP in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.