# How to use Claude with Global Shop Solutions

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

## Short answer

To use Claude with Global Shop Solutions, expose read-only data through an MCP server, connect it to Claude, and choose where Claude runs: the Anthropic API, AWS Bedrock or Google Vertex. If the data cannot leave your network, the same tool layer works with an open-weight model hosted on-prem instead.

## System

Global Shop Solutions

## Capability

claude

## Intro

Claude is a good fit for the document-heavy side of a job shop: reading a customer PO, summarising a long engineering change note, or reasoning across a routing and a purchase order. What it lacks, on its own, is any view of your Global Shop Solutions data.

The modern way to give it one is the Model Context Protocol. You run a small server that offers named tools (look up a job, list open PO lines) and Claude calls them when a question needs live data. The ERP stays the system of record; Claude is just another careful reader.

The second decision is where Claude runs, because that determines where your prompts and returned records are processed. That choice, more than the model, is what compliance teams care about.

## Use Cases

### Customer PO review against the ERP

**Description:** Give Claude a PDF PO and let it check part numbers, quantities and prices against the sales order or quote it can look up, listing mismatches for the order entry clerk.

### Engineering change impact

**Description:** Paste an ECN and let Claude look up open jobs, WIP and stock for the affected part so a planner sees what to scrap, rework or let run.

### Long-document summarisation

**Description:** Summarise a 60-page customer quality manual into the checks that matter for receiving and final inspection, with page references.

### Quality escalation drafts

**Description:** From a nonconformance note and the job history it retrieves, draft the containment summary a quality manager reviews.

### Month-end commentary

**Description:** Draft variance commentary from approved report outputs, leaving the numbers to the report and the narrative to Claude.

## System Surface

- Data read path: ODBC views on a database such as Actian Zen in many on-prem installs, or vendor-provided web services if your version offers them. Hosting and version change what is allowed.
- MCP server: a small process you write in Python or TypeScript that wraps those reads as tools and handles authentication.
- Documents: shared folders or a document management system holding POs, certs and drawings, which Claude reads as attachments or through a retrieval tool.
- Reports and exports: scheduled outputs useful as a stable, auditable snapshot when live access is not approved.
- Identity: map each Claude user to a role in your wrapper, because the ERP login is not passed through automatically.

## How It Works

### Decide the hosting path

**Detail:** Options are the Anthropic API or Claude apps with a business plan, Claude via AWS Bedrock in your cloud account, Claude on Google Vertex, or an on-prem open-weight model for controlled data.

### Create a read layer

**Detail:** Build views for jobs, operations, PO lines, inventory and customers. Name columns for humans so the model does not guess at codes.

### Write the MCP server

**Detail:** Implement four or five tools with typed inputs. Return compact JSON with an as-of timestamp and the ERP key for each record.

### Connect it to Claude

**Detail:** Register the server as a connector in the Claude client you use, or call the tools through the API in your own application. Use HTTPS transport with authentication for shared use.

### Add document retrieval

**Detail:** Index the PO and certificate folders so Claude can fetch the right file by number instead of you attaching it each time.

### Pilot and measure

**Detail:** Run it with two or three users on real tasks and record mismatches caught, time saved and any wrong answers.

## Example Flows

### PO versus sales order check

**Trigger:** Order entry receives a customer PO as a PDF.

**Steps:**

- The clerk attaches the PDF in Claude.
- Claude calls get_sales_order and get_quote for the referenced numbers.
- It compares quantity, price, ship date and part revision.
- It lists exact differences and what looks acceptable.

**Result:** The clerk resolves differences before release rather than discovering them at invoicing.

### ECN impact lookup

**Trigger:** Engineering issues a revision change on a part.

**Steps:**

- The planner pastes the ECN text into Claude.
- Claude finds open jobs, material on hand and open POs for that part.
- It proposes which jobs to hold and who to notify.

**Result:** A same-day impact list instead of a week of discovery on the floor.

## On Prem

If contract terms or export controls mean Claude cannot process your data, there are two honest answers. First, check whether a cloud deployment inside your own account (Bedrock or Vertex, in a region you control) satisfies your obligations, because some customers accept that and some do not. Second, keep everything local: reuse the same MCP server and tool design, but point it at an open-weight model served by vLLM or Ollama on your own GPUs. Tool calling quality is lower on smaller models, so test on your own tasks. A hybrid is common: Claude for non-sensitive drafting, a private model for anything touching controlled drawings or customer-restricted data.

## Security

- Run the MCP server with a read-only ERP login and the minimum set of tables exposed through views.
- Authenticate every client to the MCP server and log tool name, arguments and user.
- Strip or mask fields the task does not need, such as cost and margin, unless the role requires them.
- Confirm data retention and training terms for the specific plan or cloud service you use.
- Treat text inside documents as untrusted: a PO could contain instructions meant to manipulate the model, so keep write tools out of reach.

## Options

### Claude app with a custom MCP connector

**Fit:** Good for a handful of power users in planning, purchasing and quality.

**Effort:** Two to four weeks for a hardened first connector.

### Claude via Bedrock or Vertex in your cloud

**Fit:** Good for embedding in an internal tool with enterprise cloud governance.

**Effort:** Longer, depending on your cloud and security review.

### On-prem model with a partner such as Netray

**Fit:** Good when data must remain inside your network.

**Effort:** A pilot of a few weeks plus hardware lead time.

## Pitfalls

- Exposing a general SQL tool. The model will write plausible but wrong queries against columns it cannot interpret.
- Skipping the as-of timestamp, so users cannot tell fresh data from cached.
- Giving Claude write tools in the first release. Prove reads first.
- Attaching controlled drawings without checking the plan's data terms or your contract.
- Assuming the same prompts work on a smaller on-prem model. Re-test tool calling.

## Faq

### Does Claude have a native Global Shop Solutions connector?

**Answer:** We are not aware of one you can assume exists, and availability changes. The dependable route is your own MCP server, which also lets you control exactly what Claude can see. Check the vendor and the connector directory for current options.

### What is MCP in plain terms?

**Answer:** Model Context Protocol is an open standard for connecting AI applications to tools and data. You build one server for your ERP and any MCP-capable client, including Claude, can use it.

### Can we keep data inside our region?

**Answer:** Cloud routes such as Bedrock or Vertex let you choose regions and run inside your own cloud account. Whether that satisfies a customer's flow-down is a contract question, so confirm it rather than assume.

### Is Claude safe for controlled technical data?

**Answer:** That depends on the classification and the deployment. For export-controlled or similarly restricted data, many shops require a private on-prem model. Ask your compliance officer and document the decision.

### Can Claude post transactions?

**Answer:** It can if you build write tools, but we advise starting read-only and adding drafts with human approval before any posting.

## Search terms

global shop solutions claude, claude for global shop, claude mcp erp, claude bedrock manufacturing erp, global shop solutions anthropic, claude job shop erp, connect claude to on-prem erp, global shop erp claude integration

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