# How to connect Claude to Epicor Prophet 21

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

## Short answer

Claude reaches Prophet 21 through a connector, usually an MCP server that wraps read-only SQL views or the P21 APIs. You can run Claude through Anthropic, AWS Bedrock or Google Vertex depending on your data policy, and swap to an on-prem open-weight model if data cannot leave your network.

## System

Epicor Prophet 21

## Capability

claude

## Intro

Teams on Prophet 21 who try Claude usually start the same way: copy a block of data into the chat and ask a question. It works, and it shows quickly where Claude is strong, which is reading long documents, reasoning through messy inputs, and writing careful structured output. The limit is that the data is a snapshot, and copying it by hand does not scale or control who sees what.

The cleaner pattern is to give Claude tools. With a connector based on the Model Context Protocol, Claude can ask a P21 question, receive rows, and reason over them in the same conversation. Staff phrase questions in their own words and the connector decides which query to run, within limits you set.

Where you run Claude also matters for a distributor holding supplier cost and customer pricing. There are several hosting routes with different data handling, and an on-prem alternative for the cases where none of them is acceptable.

## Use Cases

### Long supplier agreement and rebate analysis

**Description:** Load a supplier rebate agreement or contract PDF alongside P21 purchase history and ask whether volume tiers have been met and what is accrued. Claude handles the long document well, and the figures come from your own data.

### Customer account briefings

**Description:** Before a sales call, ask for a summary of an account: sales trend by product line, open quotes, overdue invoices, returns, and notes. The connector gathers the rows, Claude writes the briefing.

### Messy parts list interpretation

**Description:** Paste an emailed list with mixed part numbers, descriptions and typos. Claude proposes item matches using lookup tools and marks the uncertain ones for a person to confirm.

### Month-end and variance explanations

**Description:** Given margin or inventory variance by branch, Claude drafts explanations by tying changes to specific suppliers, cost updates or large orders it finds in the data.

### Drafting P21 customizations and reports

**Description:** Developers use Claude to write SQL views, Crystal formula logic or Business Rule scripts, checked against a copy of the schema in a non-production environment.

## System Surface

Read-only SQL Server views on the P21 database or a replica: the usual base for a Claude connector. Table and column names differ by version, so document the views you expose.

P21 Interactive and Transaction APIs and any OData style data services your version provides: supported reads and controlled writes. Check release and licensing for availability.

Model Context Protocol server: a small service that publishes tools such as get_item, get_order, list_open_pos. Claude Desktop and other MCP clients can call it, locally over stdio or remotely over HTTP.

Crystal Reports output and scheduled exports: useful for batch analysis where Claude reads files, not live data.

Claude hosting options: the Anthropic API, Claude through AWS Bedrock, or through Google Cloud Vertex AI, each with its own contracts, regions and retention terms to verify.

## How It Works

### Choose where Claude runs

**Detail:** Match the route to policy. If you already have an AWS or Google Cloud agreement and security review, Bedrock or Vertex may fit more easily than a new vendor. Confirm region, logging and retention settings.

### Stand up a read-only P21 service

**Detail:** Create SQL views and a database login limited to them, or use the P21 API under a read-focused service user. Keep this separate from the production application server.

### Wrap it as an MCP server

**Detail:** Implement tools with narrow parameters and clear descriptions. Return trimmed JSON and cap row counts. Add a query tool only if you can constrain it to the approved views.

### Authenticate users

**Detail:** For a local stdio server, the user's workstation login governs access. For a shared HTTP server, put OAuth or your identity provider in front and map users to P21 roles.

### Write project instructions

**Detail:** Give Claude your terminology: branch codes, price classes, what on-hand versus available means in your setup, and which fields are authoritative. This reduces plausible but wrong answers.

### Test against known answers

**Detail:** Build a list of questions with answers verified in P21 and run it after every change to tools or instructions.

## Example Flows

### Pre-call account brief

**Trigger:** A sales rep asks: brief me on Northfield Electric before my 2pm call.

**Steps:**

- Claude calls the customer summary tool for trailing twelve month sales by product group.
- It calls open quotes and past due invoices tools.
- It checks recent returns and credit notes.
- It writes a short brief with talking points and any account risk.

**Result:** The rep walks into the call knowing what the customer buys, owes and has complained about.

### Rebate tier check

**Trigger:** A purchasing manager uploads a supplier agreement PDF and asks about tier status.

**Steps:**

- Claude reads the agreement and extracts tier thresholds, periods and eligible product lines.
- It calls a purchase history tool for matching receipts or invoices in the period.
- It computes spend against thresholds and shows the working.

**Result:** A tier status with the gap to the next tier, to be confirmed by the buyer against the supplier statement.

### Resolve an ambiguous part number

**Trigger:** A CSR pastes a customer's list with partial part numbers.

**Steps:**

- Claude calls item search and cross-reference tools for each line.
- It marks exact matches, probable matches and unknowns.
- It presents availability for the confident matches and questions for the rest.

**Result:** A reviewed quote starting point, with every uncertain line left for the CSR.

## On Prem

If supplier cost, contract pricing or customer data must not leave your network, a hosted Claude route may not be acceptable regardless of contract terms. Claude models are not distributed for self-hosting, so the on-prem option is a different model: an open-weight model such as Llama, Qwen, Mistral or gpt-oss served with vLLM or Ollama on your own GPU, speaking the same MCP tools. Because the MCP server is model-agnostic, you can build it once and point either Claude or a local model at it, using Claude for non-sensitive work and the local model for restricted data. Expect the local model to be weaker on very long documents and subtle reasoning, so test your real questions before committing.

## Security

- Keep the connector read-only at first, with database permissions that enforce it rather than relying on prompts.
- Limit tools to what the role needs. A counter user does not need purchase cost, and the tool should not return it for them.
- Review the retention, logging and training terms for the specific route you choose, and record the decision for audit.
- Run the MCP server inside your network and expose it only through authenticated channels, never directly to the internet.
- Log each tool call with user, parameters and row count, and review for unusual bulk reads.

## Options

### Claude with a custom MCP connector

**Fit:** Best general route for live P21 questions where hosted processing is acceptable.

**Effort:** Days to a first working connector, weeks to harden and extend.

### Claude through Bedrock or Vertex

**Fit:** Fits when procurement and security already approve your cloud provider and you want regional and logging controls there.

**Effort:** Similar build, plus cloud account setup and access policy work.

### Local open-weight model on the same connector

**Fit:** For restricted data or air-gapped sites. Netray builds this pattern, as do other integrators.

**Effort:** Weeks for a pilot, plus GPU procurement or hosting.

## Pitfalls

- Exposing a free-form SQL tool with write-capable credentials. Constrain to views and enforce read-only at the database.
- Letting Claude infer meaning from column names. Describe key fields in instructions or it may mix available and on-hand stock.
- Using one shared connection that bypasses P21 role restrictions, so a user sees data their P21 login would never show.
- Pointing analytical queries at the production database during peak counter hours.
- Skipping a regression set. Answers can drift after tool or prompt edits, and no one notices until a wrong number reaches a customer.

## Faq

### Is there an official Claude connector for Prophet 21?

**Answer:** Not one you should assume. Check with Epicor and the connector directories for your plan. In practice most teams build a small MCP server over read-only views or the P21 API, which takes limited effort and gives you control over exactly what Claude can see.

### Can Claude be hosted inside our own data center?

**Answer:** No, Claude models are offered through Anthropic and cloud partners rather than as self-hosted software. For fully on-prem requirements, use an open-weight model behind the same connector. You keep the integration investment and change only the model endpoint.

### Should I use the Anthropic API or Bedrock?

**Answer:** It depends on your existing agreements, regions, logging needs and procurement process. Both give access to Claude models. If your security team already approved AWS or Google Cloud, using their route can shorten reviews. Compare the current data handling terms for each.

### Can Claude change data in Prophet 21?

**Answer:** It can if you give it a write tool, but start read-only. For writes, prefer drafts or holds via the supported P21 API with a human approving release. Direct database writes bypass business rules and should be avoided.

### How accurate are the numbers Claude gives?

**Answer:** Accuracy comes from the tools, not the model. If the connector returns correct rows and Claude is told to quote them, numbers match P21. Errors appear when tools are vague or the model is allowed to estimate, so test with verified questions and require citations of tool output.

## Search terms

epicor prophet 21 claude, claude for prophet 21, connect claude to p21, prophet 21 anthropic, claude mcp prophet 21, claude bedrock erp data, claude for distribution erp, p21 claude desktop, claude vertex ai erp, on-prem alternative to claude for erp

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