How to connect Claude to proALPHA
Short answer
Claude reaches proALPHA through tools: usually an MCP server that wraps read-only queries against the OpenEdge database or exposed services. Choose the hosting by data policy: Anthropic's API, a Bedrock or Vertex region, or an open-weight model on-prem if nothing may leave.
Claude is attractive for ERP work because it handles long documents, careful reasoning over tables and structured tool use well. For a proALPHA site that means questions such as comparing a supplier contract with receipts, or reasoning across a production order, its BOM and open supply, rather than just fetching one row.
Claude does not know your proALPHA data. It needs a tool layer. The current standard way to give any Claude client controlled access to a system is the Model Context Protocol: you expose a few named tools, and the client calls them with the user's approval. There is no proALPHA-branded Claude connector that we can point to, so the MCP server is yours or your partner's to build.
Hosting is the second decision. For many European manufacturers, GDPR, customer NDAs and export-control concerns shape whether ERP content may go to a hosted model at all. The options below cover that range, including the case where the answer is no.
What teams use it for
Contract versus receipts review
Claude reads a supplier framework agreement PDF and compares agreed prices and lead times with receipts pulled by a tool, listing deviations.
Production order root cause
With tools for order, BOM and stock, Claude explains why an order cannot start and writes the planner a concise summary.
Engineering change impact
Given an item revision, Claude uses a where-used tool to list affected BOMs and open orders, and drafts the impact note.
Cost variance narrative
Finance exports standard versus actual cost by product group. Claude writes the explanation text for the month-end pack and flags the largest drivers.
Claude Code for OpenEdge maintenance
Developers use Claude Code to read and refactor ABL customisations and write tests, with no ERP data involved at all.
proALPHA integration surface
- OpenEdge database via read-only SQL (ODBC or JDBC) is the common basis for an MCP tool server. Schema details vary by proALPHA version and customisation.
- Application services through the OpenEdge application server, where exposed in your release, let tools reuse proALPHA business logic and authorisation instead of reimplementing it.
- Documents: contracts, certificates and drawings sit in proALPHA's document handling or in file shares. Tools can fetch them by reference for Claude to read.
- Standard exports and scheduled report outputs support a lower-trust path when no live connection is allowed.
- Source code: ABL customisation source is useful for Claude Code, and is separate from runtime data.
How it works
- 1
Define the tools
Write five to eight read-only tools: item_lookup, order_status, stock_by_item, open_po_lines, bom_explode, where_used.
- 2
Build the MCP server
Implement it with an official SDK. Use stdio for a single user on a workstation, or Streamable HTTP behind your gateway for shared use.
- 3
Connect to proALPHA safely
Use a dedicated read-only account against a replica, or your exposed services. Keep credentials out of the model's reach.
- 4
Choose the Claude hosting
Anthropic API or a Claude app with enterprise terms, Claude on AWS Bedrock in an EU region, or Google Vertex. Compare retention terms and region guarantees with your legal team.
- 5
Register the server with the client
Add it to Claude Desktop, Claude Code or your own agent. Users see each tool call and can approve it.
- 6
Validate with real questions
Run a fixed set of questions with known answers from proALPHA screens before widening access.
- 7
Add the on-prem fallback
Keep the same MCP tools so you can swap the model for a local one on restricted data without rebuilding the integration.
Example flows
Supplier deviation review
Trigger: Buyer uploads a framework agreement and asks for deviations
- Claude reads the PDF and extracts price and lead-time clauses.
- It calls open_po_lines and receipts tools for the supplier.
- It compares and lists lines outside agreed terms.
Result: A reviewed deviation list the buyer can use in the next supplier meeting.
Engineering change impact
Trigger: Engineer asks what a revision change touches
- Claude calls where_used for the component.
- It checks open production orders using those BOMs.
- It drafts an impact summary with order numbers.
Result: A change note with real order numbers, ready for the change board.
Keeping data on-prem
If proALPHA data cannot go to any hosted model, the MCP server and your tools remain exactly the same, and the model behind them changes to an open-weight one such as a Qwen, Llama or Mistral class model served inside your network. MCP is client-agnostic, so a local chat client or agent can use the same tools. Expect lower quality on long, multi-document reasoning than a frontier hosted model, so test your actual workflows. Some customers use a hybrid: hosted Claude for non-sensitive engineering and code work, and a private model for anything that reads ERP rows.
Security checklist
- Expose read-only tools first and keep write-back out of the MCP server until approval flows exist.
- Scope by company and plant inside the tool, not in the prompt.
- Review the provider's retention, training and regional terms in writing; do not assume defaults.
- Treat document text as untrusted: a contract or email can contain instructions aimed at the model.
- Keep an audit log of tool calls with user, parameters and row counts.
Ways to get it done
Claude Desktop with a community-style MCP server
Effort: Days, and you own the quality and security of the server.
Individual experiments on non-sensitive data.
Governed MCP server with enterprise Claude hosting
Effort: A few weeks including legal review.
Teams whose policy allows a contracted hosted model in a chosen region.
Private model with the same tool layer (Netray)
Effort: A few weeks for a pilot, depending on GPU availability.
Sites where ERP content may not leave the network.
Pitfalls
- !Giving Claude a generic SQL tool, which invites guesses about customised fields.
- !Running the MCP server under a powerful ERP account.
- !Forgetting document language: German contracts and English specs in one question need testing.
- !Assuming a chat answer equals a posted transaction; keep a clear line between advice and action.
- !No version pinning of the tool schema, so client behaviour changes unnoticed.
Frequently asked questions
Is there a Claude connector for proALPHA?
We are not aware of an official one. The practical route is an MCP server that wraps read-only queries or exposed services. Verify with your proALPHA partner whether a vendor offering has appeared for your release.
Which Claude hosting is right for a European manufacturer?
It depends on your data policy. Anthropic's API, Claude on AWS Bedrock or Google Vertex offer different regional and contractual options. Have legal review the terms, and keep an on-prem option for restricted data.
Can Claude change data in proALPHA?
It can if you build write tools, but start read-only. For writes, require human approval and call proALPHA's own services so validation, number ranges and audit still apply.
Does Claude Code help with proALPHA customisations?
It can help read and refactor ABL source and generate tests. This uses your code rather than your ERP data, so it is often an easier first step. Review all generated code like any other contribution.
What if we are air-gapped?
Then hosted Claude is not an option. Keep the MCP tool layer and use a local open-weight model on your own GPUs. Updates are delivered through controlled transfer.
Want Claude working on your proALPHA?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment