dynamics-365-business-central-mcp-server-by-cdata
Provides a local, read-only MCP server (stdio-based) that exposes Dynamics 365 Business Central data through tools that wrap the CData JDBC Driver as relational SQL models. It supports discovering tables/columns and executing SELECT queries via MCP JSON-RPC tools.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses HTTPS/TLS is implied for the JDBC driver connection, but MCP-level transport details are not specified beyond stdio. Authentication is delegated to the underlying CData JDBC driver; no MCP-layer auth, scopes, or per-tool authorization controls are described. The provided configuration requires storing/using JDBC connection information (including OAuth/credentials) in a local .prp file, with no guidance on secret redaction or secure storage. Read-only limitation reduces risk of data modification, but run_query still enables arbitrary SELECT access that can expose sensitive fields if the underlying account has broad permissions.
⚡ Reliability
Best When
You need local, tool-based read access to Business Central for an MCP-capable desktop client on the same machine, and you can authenticate the underlying CData JDBC driver connection.
Avoid When
You need robust operational controls (rate limits, audit logs, fine-grained authorization) beyond what the JDBC driver/Data source provides, or you require safe idempotent writes with clear retry semantics.
Use Cases
- • Ask an AI client to retrieve live Business Central data without writing SQL
- • Build conversational analytics over Business Central entities (e.g., accounts, tickets, calendar events)
- • Quick local integration of Business Central read access into Claude Desktop via MCP
Not For
- • Untrusted remote use (server is local/stdio and not described for remote hosting)
- • High-safety/least-privilege environments where write/delete/update are required
- • Applications needing a REST/HTTP API, webhooks, or server-side auth policies
Interface
Authentication
README indicates that if the data source uses OAuth, authentication happens in a browser during connection-string setup. No explicit MCP-level auth or scope model is described.
Pricing
README discusses licensing the CData JDBC driver (trial or license key). No MCP pricing details are provided in the supplied content.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio, so it must run on the same machine as the MCP client (e.g., Claude Desktop).
- ⚠ For OAuth-backed connections, an interactive browser auth step may be required when building the JDBC connection string.
- ⚠ Tool outputs are returned in CSV format for get_columns/get_tables, which agents may need to parse carefully.
- ⚠ Because the server runs a SQL SELECT via run_query, the client may generate expensive or broad queries; no cost/limit controls are documented.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for dynamics-365-business-central-mcp-server-by-cdata.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.