# How to use Claude with Microsoft Dynamics NAV

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

## Short answer

Connect Claude to NAV by building a Model Context Protocol server over NAV web services or a read-only SQL replica, then attach it to Claude as a connector. Choose the Anthropic API, AWS Bedrock or Google Vertex depending on your cloud posture, or run an open-weight model on-prem when data cannot leave.

## System

Microsoft Dynamics NAV

## Capability

claude

## Intro

Claude is attractive for NAV shops because it handles long documents and structured tool use well. That fits NAV work: long BOM listings, purchase contracts, and multi-step questions that span item cards, ledgers and orders.

But Claude only knows what it is shown. The standard way to give it live access is MCP: a small server exposes named tools such as get item availability, and Claude calls them when asked. NAV does not ship an MCP server, so someone builds the bridge.

Where Claude runs matters as much as how it connects. Your options are Anthropic's own API, Claude through AWS Bedrock or Google Vertex AI under your cloud agreement, or no Claude at all for data that must stay on-prem.

## Use Cases

### Ask about a BOM across levels

**Description:** A planner asks which finished goods use a shortage component. Claude calls tools that walk Production BOM Lines and returns a where-used list with quantities.

### Review a supplier contract against PO lines

**Description:** Upload a contract PDF plus an exported list of PO lines, and ask Claude to flag price or lead time mismatches.

### Month-end commentary

**Description:** Finance feeds G/L Entry summaries by account and asks for a draft variance memo with questions to investigate.

### Explain legacy C/AL objects

**Description:** A developer pastes an old codeunit and asks for a plain-language explanation and migration notes toward AL.

### Order status for customer service

**Description:** Through a connector, a rep asks where order SO-1043 stands and gets shipments, production status and open purchase dependencies.

## System Surface

- MCP over NAV web services: your MCP server calls published OData or SOAP pages for items, orders and BOMs. Which OData version exists depends on the NAV release.
- Read-only SQL replica: for aggregate questions across Item Ledger Entry or Value Entry where web services are too slow.
- Report export: RDLC or Word report output to PDF as input to document questions.
- Windows-integrated or user-password auth: the MCP server holds a service identity and applies its own per-user permission checks.
- Event subscribers and Job Queue: optionally push NAV changes to an index so Claude can search recent activity.

## How It Works

### Define tools, not tables

**Detail:** List six to ten questions people ask, and make one tool per question: item availability, order status, where-used, open PO lines, vendor performance.

### Build the MCP server

**Detail:** Use an MCP SDK in Python or TypeScript. Each tool calls NAV and returns trimmed JSON with the record IDs included.

### Choose a transport

**Detail:** Use stdio for a single developer on a workstation, or HTTP for a shared server with authentication in front of it.

### Pick the Claude surface

**Detail:** Claude apps with custom connectors, the Anthropic API for your own tools, or Bedrock or Vertex if your enterprise agreement and data residency run through those clouds.

### Scope permissions per user

**Detail:** Map the signed-in person to a NAV user or role so Claude cannot return data they could not open in NAV.

### Log and review

**Detail:** Record each tool call and the answer. Review a sample weekly for wrong or overbroad responses.

## Example Flows

### Where-used for a shortage part

**Trigger:** Planner asks Claude which open production orders consume component 8821.

**Steps:**

- Claude calls the where-used tool with the item number.
- The server reads Prod. Order Component for released orders.
- Results return with order numbers, due dates and remaining quantities.
- Claude ranks them by due date and highlights the earliest at risk.

**Result:** A ranked list that normally takes several NAV filters and a manual sort.

### Contract check against live prices

**Trigger:** Buyer uploads a renewed supplier agreement.

**Steps:**

- Claude extracts price breaks and lead times from the PDF.
- It calls a tool to fetch current Purchase Prices for the vendor.
- It compares them and lists differences.
- The buyer confirms and updates NAV manually.

**Result:** Faster contract onboarding with nothing written to NAV automatically.

## On Prem

Claude models are available through Anthropic's API and through major clouds, not as downloadable weights, so a strictly air-gapped NAV cannot run Claude itself. Options are: keep the MCP server on-prem and let only sanitized question and answer text reach a cloud endpoint, or use an open-weight model served locally with the same MCP tool layer. The good news is that a well-designed MCP server is model-agnostic, so you can start with Claude on non-sensitive questions and swap to a local model for restricted data without rebuilding the NAV bridge.

## Security

- Review Anthropic's current commercial data handling terms, or your Bedrock or Vertex agreement, before sending any company data.
- Run the MCP server with a read-only NAV account and per-user authorization, never a shared super user.
- Redact fields covered by export control or customer NDAs inside the MCP server, before data reaches the model.
- Put HTTP MCP behind TLS and authentication, and do not expose it to the open internet.

## Options

### Build your own MCP server and use Claude via API or apps

**Fit:** You have an engineer comfortable with NAV web services and are allowed to use a hosted model.

**Effort:** About 3 to 8 weeks for a useful read-only toolset.

### Claude through Bedrock or Vertex in your cloud tenant

**Fit:** Enterprises already standardized on AWS or Google Cloud with approved data processing terms.

**Effort:** Similar build effort plus cloud security review.

### Netray builds the tool layer and runs it on your hardware

**Fit:** You want the same tools usable by Claude and by a private on-prem model.

**Effort:** Scoped pilot over several weeks.

## Pitfalls

- Returning raw table rows overwhelms the model. Return summaries with record IDs.
- One shared service account hides who asked what and breaks NAV permissions.
- Assuming a hosted connector is allowed under your customer contracts without checking.
- Letting tool descriptions be vague, so Claude picks the wrong tool.
- Forgetting multiple companies: NAV tables are per company, so tools need a company parameter.

## Faq

### Is there an official Claude connector for Dynamics NAV?

**Answer:** I am not aware of one. Microsoft's focus is on Business Central. For NAV you build a small MCP server over web services or a replica, or buy one from a partner after checking their data handling.

### Can Claude run fully on our servers?

**Answer:** Not as downloadable weights. For fully on-prem, use an open-weight model with the same MCP tools. If cloud use is acceptable, Bedrock or Vertex can keep traffic inside your existing cloud agreement.

### Which NAV versions work?

**Answer:** Any version where you can read data through web services or a SQL replica. Older releases lean more on SQL and SOAP. The MCP layer hides that difference from Claude.

### Can Claude post transactions into NAV?

**Answer:** Possible through a codeunit-backed tool, but begin read-only. If you add writes, make them create a draft or proposal that a person approves.

### How is this different from the ChatGPT route?

**Answer:** The data bridge is the same idea. With MCP the tools work across clients, so you are less tied to one vendor. Choose on data terms, quality on your own questions, and cost.

## Search terms

dynamics nav claude, claude for dynamics nav, claude navision integration, claude mcp dynamics nav, connect claude to dynamics nav, anthropic dynamics nav, claude bedrock dynamics nav, dynamics nav claude on-prem

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