sage-200-mcp-server-by-cdata
Provides a local, read-only MCP server that exposes Sage 200 data via CData’s JDBC Driver. It wraps the JDBC driver and exposes MCP tools to list tables/columns and run SQL SELECT queries (JSON-RPC tool calls) for use by local MCP-capable clients (e.g., Claude Desktop).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Local stdio reduces network exposure, but security is still driven by the JDBC connection string and the environment (.prp file). The README includes an example .prp that contains DriverPath and JdbcUrl (which may embed credentials or OAuth parameters), but provides no guidance on secret storage, redaction, or least-privilege scoping. No explicit TLS, scope granularity, or rate-limit/audit controls are documented. SQL execution tool could lead to data over-exfiltration if used injudiciously, and the repo documentation does not describe query/result limits or defensive filtering.
⚡ Reliability
Best When
You have Sage 200 access via the CData JDBC Driver and want a local MCP integration to query current operational data without crafting SQL manually.
Avoid When
You need secure remote exposure over the network, strong API-level governance (rate limits, audit trails), or robust operational guarantees (SLA, retries, structured error codes).
Use Cases
- • Ask natural-language questions to retrieve live Sage 200 data through an MCP client
- • Explore available Sage 200 tables and columns via MCP tools
- • Run read-only SQL SELECT queries against Sage 200 using CData JDBC under the hood
Not For
- • Write/update/delete operations (described as read-only locally)
- • Use from remote machines (stdio-based local-only connectivity)
- • Production-grade automation requiring explicit pagination/rate-limit handling via an HTTP API
Interface
Authentication
Authentication is handled by the underlying CData JDBC Driver via the provided JDBC connection string; OAuth may be used depending on the data source configuration. The MCP server itself is local and relies on the client running on the same machine via stdio.
Pricing
README does not describe pricing for the MCP server itself. It references licensing the CData JDBC Driver.
Agent Metadata
Known Gotchas
- ⚠ Uses stdio, so it can only be used by clients running on the same machine as the server.
- ⚠ Local-only setup requires restarting/refreshing the client to discover MCP servers.
- ⚠ Only read-only behavior is described locally; agents should avoid assuming write capabilities.
- ⚠ run_query accepts arbitrary SQL SELECT; agents may generate expensive queries or unintentionally query too much data without guidance/limits.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for sage-200-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.