Katana MRP MCP connector
The Katana MRP connector brings batches, bin locations, bin transfers, and bills of materials into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so each person works with live stock inside their own Katana MRP access.
- Connects with an API key
- Free 14-day trial
- No credit card
Which batches of steel tubing are in bin A-12?
Working in Katana MRP with Elaichi
-
List all Katana MRP additional costs
-
List all Katana MRP batch stocks
-
List all Katana MRP bin inventories
How to connect Katana MRP to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Katana MRP MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Katana MRP through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Katana MRP is logged.
-
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”
What connecting Katana MRP gets you
6 screens from Elaichi, each doing one job for your Katana MRP account.
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, Cursor or Microsoft Copilot
The agent
Ask about batches and bins in plain language.
Type a question and the Elaichi Agent answers from live Katana MRP records.
Copy the endpoint
AI apps
One endpoint puts Katana MRP in every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
231 Katana MRP tools, no code to write.
Batches, bin locations, bin transfers and BOM rows, covered without building anything.
Toolboxes
Every team gets its own Katana MRP toolbox.
Warehouse, production and finance each see only the tools their work needs.
Shared connections
Teammates work in Katana MRP, never see a key.
One person connects Katana MRP and shares it with teams and members.
Audit log
Every Katana MRP change names who made it.
When, who, what happened, type and resource, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Katana MRP digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Katana MRP
Queued
Workflows
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 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%
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.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Katana MRP
All three can connect Katana MRP to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Katana MRP tools | Allow or restrict single Katana MRP tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Katana MRP call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deletion of bin locations or edits to bill of materials rows. A restricted Katana MRP action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
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, Microsoft Copilot, 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, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Katana MRP?
Yes. Both let Claude, ChatGPT or Cursor use Katana MRP. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Katana MRP call.
How is Elaichi different from Composio for Katana MRP?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Katana MRP: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Katana MRP in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot