For Austrian companies and tax advisers running BMD NTCS
A BMD NTCS MCP server gives Claude, ChatGPT or Copilot read-first tools for customers, open invoices, order responses and inventory reports. BMD documents an EDI XML framework in public; its REST interface serves BMD Web and BMD Go without a public reference. BMD ships no MCP server as of 21 September 2026.
Why BMD NTCS is hard for agents
01 · Docs
The REST interface mainly serves BMD Web and the BMD Go app. There is no public endpoint reference, and administrators may disable it in BMD.INI. Whether it can serve an agent on your installation is the first check in the blueprint.
02 · EDI
The documented path for orders, responses and invoices is the BMD EDI XML framework. It is file-based and asynchronous, not a query API. Tools on that path read and prepare XML documents rather than asking NTCS live.
03 · Clients
Tax advisory firms run many clients in one BMD installation, and their data is confidential by profession. Every tool is scoped to one client at a time, and every call is logged for audit.
04 · Hosting
NTCS runs on-premises on Windows and SQL Server or in BMD Cloud. Where the MCP server runs, and how Windows-authenticated accounts are used, has to follow BMD's own hardening guide and your IT team's approval.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | BMD web application REST interface (REST, docs not published): used by BMD Web and the BMD Go app; administrators can switch it off in BMD.INI (HANDLEDREQUESTS); payload format and authentication are not published · BMD EDI XML framework (XSD 2.0) (file/EDI, docs public): public sample files for offer, order, order change, order response, inventory report, dispatch advice, price catalogue and invoice · CSV import and export (accounting) (file, docs not published): partners exchange customer and supplier master data and bookings as CSV files with PDF invoices |
| Authentication | NTCS login uses encrypted standard authentication or Windows authentication; BMD Web supports Windows single sign-on and two-factor authentication. Each NTCS user has its own SQL Server database user, so changes are traceable. Authentication for the REST interface is not documented publicly. |
| Vendor MCP server | No vendor server. No BMD MCP server; BMD ships its own AI tools inside NTCS (the Fox family) and partner integrations such as RechtGPT and Finmatics. |
| Vendor AI assistant | BMD's Fox tools cover a support chatbot, text generation, natural language filters and Dok-Chat, plus an AI analysis function that answers natural-language questions with tables on business data such as offers and fixed assets. |
| Other connectors | ecosio integrates its EDI hub into NTCS for orders, invoices and shipping notices, and Finmatics feeds AI document capture into BMD accounting; neither is an agent connector. |
BMD Systemhaus GmbH (AT). Austrian and DACH companies, tax advisers, auditors, construction firms, municipal utilities and schools using BMD for accounting, payroll, merchandise management, CRM and DMS; BMD states more than 30,000 customers.
What we build
Built on what BMD Systemhaus GmbH documents: offers, orders and order changes, order responses, inventory reports, dispatch advices, price catalogues, invoices, customer and supplier master data. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# bmd-ntcs-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
get_customer: # customer number -> master data
backend: confirmed in blueprint
mode: read
list_open_invoices: # customer, period -> open invoices
backend: confirmed in blueprint
mode: read
parse_order_response: # order response XML -> positions, dates, deviations
backend: BMD EDI XML ordrsp (XSD 2.0)
mode: read
get_inventory_report: # article -> stock from the inventory report
backend: BMD EDI XML invrpt
mode: read
draft_order_xml: # customer, items -> BMD ORDER 2.0 XML draft a person confirms before import
backend: BMD EDI XML order (http://www.bmd.at/xsd/ORDER/2.0/)
mode: propose
audit: every call logged with user, tool, arguments and the BMD NTCS responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
BMD NTCS holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
When this is the wrong page
If the questions are about business data inside BMD, the Fox AI analysis function already answers them in NTCS and BMD maintains it; document capture belongs to Finmatics. A connector is right when the assistant lives in Claude, ChatGPT or Copilot, or combines BMD with another system.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your BMD NTCS owners and checks every backend against your release and licence. Week two tests whether a person's own BMD NTCS permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named BMD NTCS administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Not as of 21 September 2026. BMD ships its own Fox AI tools inside NTCS, including an analysis function for natural-language questions, but no MCP server. An assistant outside BMD has to be connected through the REST interface or the EDI XML framework.
It needs the REST interface enabled in BMD.INI, or access to the EDI XML exchange, on your installation. Licence terms and the REST payload format are not public, so check with BMD; we confirm them in the blueprint.
No. The connector is designed so each call runs as the asking person and is scoped to one client, and BMD's own rights decide the answer. How the REST interface carries that identity is not documented publicly, so it is tested first.
The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Thirty minutes with the engineer who would build the connector, with your BMD NTCS administrator in the room if you like.