# How to use Claude with Katana

> Source: https://netray.co/integrations/katana-claude
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Integrations

## Short answer

Claude connects to Katana most cleanly through an MCP server that wraps the Katana REST API, which lets Claude read stock and orders on demand. You can reach Claude through Anthropic directly, AWS Bedrock or Google Vertex AI depending on where your data governance sits.

## System

Katana

## Capability

claude

## Intro

Katana teams who try Claude usually start by dropping a spreadsheet into a chat. It is a fine start, but the value shows up when Claude can ask Katana questions itself and carry the result into a longer piece of work, like a supplier review or a build plan for next week.

That is what the Model Context Protocol is for. It gives Claude a standard way to call tools, and Katana's REST API is easy to wrap. This page is about the Claude side of the decision: which route to reach Claude, what it should be allowed to do with Katana, and how that differs from using another assistant.

## Use Cases

### Weekly planning memo

**Description:** Claude reads open sales orders, manufacturing orders and stock, then writes a plan memo that states assumptions and lists decisions needed from the owner.

### Recipe and cost review

**Description:** Given recipe rows and current material costs, it checks which products have drifted in margin and why.

### Supplier performance summary

**Description:** Compares expected and received dates across purchase orders per supplier and writes a short scorecard.

### Long document grounding

**Description:** Combine Katana order data with a customer's specification PDF to confirm that ordered variants match required options.

### Data cleanup assistant

**Description:** Scans variants and materials for duplicate SKUs, missing units or inconsistent naming, and proposes a cleanup sheet for a human to apply.

## System Surface

- Katana REST API with bearer key authentication, wrapped by a local or hosted MCP server so Claude Desktop or other MCP clients can call it.
- Claude can also call tools defined directly through the Anthropic Messages API for your own applications, using the same wrapper functions.
- Katana exports (CSV and similar) for a no-engineering route, uploaded to a Claude conversation or project.
- Webhooks, if you want a Claude-powered backend job triggered by Katana events rather than a person asking.
- Rate limits on the API key apply, so MCP tools should cache catalogue data and return trimmed results.

## How It Works

### Choose how Claude is reached

**Detail:** Direct Anthropic access is simplest. If your company already governs AI through AWS or Google Cloud, Claude on Bedrock or Vertex AI keeps usage inside that contract and region setup.

### Pick the interface

**Detail:** People using chat can connect an MCP server. Backend jobs use the API with tool definitions. Start with chat to learn which questions matter.

### Build the Katana tool wrapper

**Detail:** Implement read-only tools for stock, orders, manufacturing orders, purchase orders and recipes. Keep descriptions precise.

### Write a project or system prompt

**Detail:** Define your terms: which location is the main warehouse, how you treat safety stock, and when Claude must ask instead of assuming.

### Review outputs with a checklist

**Detail:** For the first month, a planner checks the numbers against Katana before acting, and misses become prompt or tool fixes.

### Add controlled writes later

**Detail:** If needed, add a draft-only write tool and a human confirmation step before the real API call.

## Example Flows

### Friday build plan

**Trigger:** Owner asks Claude to plan next week's builds

**Steps:**

- Claude pulls open sales orders due within two weeks.
- It reads recipes and stock for each required variant.
- It identifies materials that must be purchased and lead times from supplier notes.
- It writes a plan with a build sequence, risks and questions.

**Result:** A plan memo in minutes, with every figure traceable to a tool call.

### Margin drift check

**Trigger:** Month end close

**Steps:**

- Claude reads sales order rows and current material costs.
- It recomputes expected margin per variant.
- It lists products whose margin fell and the material that moved.

**Result:** A short list of pricing or sourcing decisions for the owner.

## On Prem

Katana is cloud only, so there is no on-prem Katana to connect to privately. If you need Claude-grade reasoning without leaving a cloud boundary, use Claude through a cloud provider region you control, such as Bedrock or Vertex AI. If you need the model itself on your own hardware, Claude is not a self-hosted option, so use an open-weight model behind the same MCP or tool layer. Netray builds that layer so you can swap the model without rewriting the Katana tools.

## Security

- Review Anthropic's current commercial terms for retention and training; commercial and API usage has different defaults than consumer chat, but confirm in writing for your plan.
- Use a dedicated read-only Katana key for the MCP server.
- Run the MCP server locally for personal use, or behind authentication if shared.
- Remove or mask customer personal data from tool outputs unless required.
- Log tool calls so you can reconstruct what Claude saw for any answer.

## Options

### Upload exports to Claude

**Fit:** One-off analysis with no setup.

**Effort:** Minutes

### MCP server over the Katana API

**Fit:** Live questions from planners using Claude Desktop or another MCP client.

**Effort:** Days to a couple of weeks

### Claude on Bedrock or Vertex with Netray

**Fit:** Company governance requires a specific cloud account, region, logging and approvals.

**Effort:** A scoped build

## Pitfalls

- Giving Claude too many tools so it picks the wrong one; keep the set small and descriptive.
- Skipping the system prompt, which leaves Claude guessing at your location and safety stock conventions.
- Returning full API payloads and wasting context on fields nobody needs.
- Assuming a working chat demo equals a safe write path.
- Ignoring API rate limits during long multi-step analysis.

## Faq

### Does Katana have an official Claude connector?

**Answer:** Check the Claude connector directory and Katana's integrations list for the current status. If none exists, an MCP server you run over the REST API is a straightforward alternative, and the same tools work with other MCP clients too.

### Should I use Anthropic directly, Bedrock or Vertex?

**Answer:** Use Anthropic directly if you want the newest features and simple billing. Use Bedrock or Vertex AI if your organisation already centralises security, billing and regions on those clouds. The Katana tool layer stays the same either way.

### Can Claude run on-prem for Katana data?

**Answer:** Claude is a hosted model, so not on your own servers. Katana is also cloud only. If you need a private model, use an open-weight one behind the same tools. Netray can set that up and keep prompts and logs in your environment.

### Can Claude change inventory in Katana?

**Answer:** Only if you build and enable a write tool. We suggest starting read-only, then adding draft proposals such as a suggested purchase order, with a human approving before the API write is executed.

### Is this better than Katana's own reports?

**Answer:** Katana's reports are better for standard views and are always consistent. Claude is useful for open questions, narrative explanations and combining Katana with other documents. Use both and let Katana remain the source of truth.

## Search terms

katana claude, claude for katana mrp, katana mcp claude, connect claude to katana, claude katana cloud inventory, claude bedrock manufacturing erp, anthropic katana integration, claude desktop katana

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json