sage-300-mcp-server-by-cdata
Provides a read-only Model Context Protocol (MCP) server that exposes Sage 300 data as SQL-like tables/columns via CData JDBC. Intended for LLM clients (e.g., Claude Desktop) to query live Sage 300 data through MCP tools (get_tables, get_columns, run_query).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses local stdio MCP transport (no network exposure implied), but the README does not document MCP-level authentication/authorization, scope enforcement, query allowlisting, or secret handling/logging behavior. Connection credentials are supplied via a local .prp/JdbcUrl string and JDBC driver licensing/auth; the README does not describe how those secrets are protected from logs or process inspection. TLS enforcement is not described for the MCP layer or JDBC connection (depends on JDBC URL/driver configuration).
⚡ Reliability
Best When
You have local access to a Sage 300 environment, want an MCP-compatible local bridge to query live data with an LLM desktop client, and only need read operations.
Avoid When
You need robust, documented error/retry/rate-limit behavior for production automation, you need fine-grained row/column authorization enforced at the MCP layer, or you require a network-accessible API with standard security controls.
Use Cases
- • Ask natural-language questions about Sage 300 data (e.g., counts, correlations, status metrics).
- • Retrieve schemas (tables/columns) to discover available Sage 300 datasets for analysis.
- • Run controlled read-only SQL SELECT queries against Sage 300 through an MCP tool interface.
Not For
- • Writing/creating/updating/deleting Sage 300 data (explicitly read-only in this repo).
- • Use as a remote network API (it uses stdio and is intended for co-located clients).
- • High-security or multi-tenant deployments without additional controls (secrets and access control are not described at the MCP layer).
Interface
Authentication
The README indicates authentication is handled by the underlying CData JDBC driver/connection string (it mentions OAuth in the generic JDBC connection string setup note). The MCP layer itself does not document authentication/authorization controls.
Pricing
CData JDBC driver licensing is required (README instructs to license the JDBC driver). MCP server itself is MIT-licensed, but runtime depends on the commercial JDBC driver license.
Agent Metadata
Known Gotchas
- ⚠ The server uses stdio, so it can only be used by clients running on the same machine as the MCP server process.
- ⚠ Tools operate by passing SQL to run_query; agents may generate expensive queries unless constrained.
- ⚠ The repo is read-only; attempts to perform write/update/delete actions are not supported by this server.
- ⚠ Claude Desktop may need a full restart/quit to detect new MCP servers.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for sage-300-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.