bc-webclient

BC WebClient MCP exposes a Model Context Protocol (MCP) server that bridges Claude-like AI assistants with Microsoft Dynamics 365 Business Central through WebUI/WebSocket interactions. The server exposes a set of MCP tools that let the client discover BC schema, read and write page data, run guided prompts, and manage complex document pages with line items. Typical workflows include discovering available BC pages, performing real-time data reads, filtering and updating records, and executing page actions. By using the MCP layer, AI assistants can drive BC operations in a natural language style while the underlying communication remains aligned with BC's WebUI protocol.

To use it, run the MCP server via npx (no local installation required) and configure Claude Desktop (or any MCP-compatible client) to connect to the provided BC_BASE_URL and credentials. Once configured, you can ask the agent to search pages, read sales orders with their line items, update customer records, or initiate guided workflows with prompts. Examples include: reading a Sales Order with all its line items, finding pages related to inventory management, or creating a new BC customer via a guided prompt. The server also supports document pages, line-item operations, and workflow tracking, enabling richer automation scenarios across BC modules.

Prerequisites

• Node.js v18+ installed on the host
• Access to a Business Central v27 environment (or compatible) with web client enabled
• Claude Desktop or another MCP-compatible client

Install steps

1. Check Node.js is installed
   • node --version
2. Install or run the MCP server via npx (no permanent installation required)
   • This approach downloads the latest bc-webclient-mcp package on demand
3. Start configuring Claude Desktop to point to the MCP server using the provided BC_BASE_URL and credentials

Alternative: Install from source (for development)

# Clone the repository
git clone https://github.com/SShadowS/bc-webclient-mcp-server.git
cd bc-webclient-mcp-server

# Install dependencies
npm install

# Build the TypeScript project
npm run build

Then in Claude Desktop config, reference the built dist/index.js with an absolute path, for example:

{
  "mcpServers": {
    "business-central": {
      "command": "node",
      "args": ["C:\\path\\to\\bc-webclient-mcp-server\\dist\\index.js"],
      "env": {
        "BC_BASE_URL": "http://your-bc-server/BC/",
        "BC_USERNAME": "your-username",
        "BC_PASSWORD": "your-password",
        "BC_TENANT_ID": "default"
      }
    }
  }
}

Notes:

• The config file for Claude Desktop should be valid JSON. Ensure the BC_BASE_URL ends with /BC/.
• When using Windows paths in JSON, escape backslashes (\).
• If you prefer no-install, use the npx-based command from the Quick Start instructions.

Environment variables to consider:

• BC_BASE_URL: Base URL to the BC web client, including the /BC/ path (e.g., http://bc-server/BC/)
• BC_USERNAME: BC login username (no domain prefix, just the user name)
• BC_PASSWORD: BC user password
• BC_TENANT_ID: Tenant identifier, commonly default for on-prem; may vary in cloud deployments Common issues to watch for:
• Ensure BC_BASE_URL is reachable and the BC UI is accessible from the MCP host
• WebSocket connections must be allowed through any firewall
• When applying updates, restart Claude/Desktop to reload tools
• If you encounter TypeScript errors, run npx tsc --noEmit to surface type issues
• For troubleshooting, consult CLAUDE.md as referenced in the README