Microsoft Business Central Connector

Microsoft Dynamics 365 Business Central is an all-in-one business management solution (ERP) designed to streamline business processes.

Start for free View documentation

4.8 on G2

Weld · Data Sources

Microsoft Business CentralYour warehouseLive

company10 columnsSynced

customer31 columnsSynced

account11 columnsSynced

item19 columnsSyncing

currency9 columnsQueued

Lands in

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

Microsoft Business Central

Data source

Authenticating...

Ready to connect

Overview

Microsoft Business Central in your warehouse.
Ready for your agents.

Microsoft Dynamics 365 Business Central is an all-in-one business management solution (ERP) designed to streamline business processes. Weld's Microsoft Business Central connector is fully managed: it extracts data from Microsoft Business Central, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

Agent context

Microsoft Business Central data schema.
The map your agents read.

Every table, field and relationship Weld syncs from Microsoft Business Central is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables: 92
fields: 1,475

92 tables

Open the schema explorer Open the full schema explorer

Weld MCP server

Ask your agent.
It already knows Microsoft Business Central.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Microsoft Business Central context, finds the tables it needs and queries your warehouse.

Agent contextMicrosoft Business Central tables, fields and joins
QuerySQL against your warehouse
OperateCheck, rerun and refresh syncs

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextMicrosoft Business Centraltables92fields1,475

How many customer rows do we have per tax_area? Use our Microsoft Business Central data.

Reading the Microsoft Business Central context first, so the query uses the right tables and keys.

●weld·search_available_references

⎿raw.business_central.customer

raw.business_central.tax_area

+ 90 more Microsoft Business Central tables

●weld·get_reference_schema

⎿customer · 31 columns

joins tax_area on tax_area_id

●weld·run_query

⎿select t.id, count(*) from {{raw.business_central.customer}} c

join {{raw.business_central.tax_area}} t on c.tax_area_id = t.id

group by 1

submitted

●weld·get_query_status

⎿DONE

●weld·get_query_result

⎿rows returned

✓Answered from Microsoft Business Central data in your warehouse

>Ask about your Microsoft Business Central dataMCP

Destinations

Load Microsoft Business Central into any warehouse.
Set up in minutes, no code.

Resources

Everything you need.
To get started.

Documentation

Microsoft Business Central setup guide

Step-by-step instructions to configure and start syncing.

MCP server

Connect your agents

Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.

Weld Connect API

Build custom connectors

Use the Weld Connect API to build and publish your own connector.

FAQ

Common questions

Answers to frequently asked questions about Weld connectors.

Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create Microsoft Business Central connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

Explore Weld Connect API reference

POST/elt_syncs

# Create a Microsoft Business Central ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "business-central",
    "destination_schema_name": "business-central_data",
    "sync_interval": "0 * * * *"
  }'
▌