sas-data-sets-mcp-server-by-cdata
Provides a read-only Model Context Protocol (MCP) server that exposes SAS Data Sets via the CData JDBC Driver, letting an MCP-capable client (e.g., Claude Desktop) query live data using MCP tools (get tables, get columns, run SQL SELECT).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses local stdio MCP (reduces network exposure) but requires embedding JDBC connection details in a local .prp file. TLS usage for the underlying JDBC connection is not documented in the README. The MCP layer does not document per-tool authorization, fine-grained scopes, or protections against overbroad SQL reads beyond what the JDBC driver and underlying SAS permissions enforce. Dependency/Vulnerability hygiene is not verifiable from the provided content.
⚡ Reliability
Best When
You want local, read-only data exploration of SAS Data Sets from an MCP-capable desktop client on the same machine as the server process.
Avoid When
You need an internet-reachable API endpoint, fine-grained per-query access controls, or robust, documented pagination/rate limiting semantics.
Use Cases
- • Natural-language-to-data queries over SAS Data Sets using an MCP client
- • Schema discovery (list tables/columns) for SAS Data Sets
- • Executing read-only SQL SELECT queries against SAS Data Sets and returning results to an LLM client
Not For
- • Write/update/delete operations (server is explicitly read-only)
- • Remote/public deployment expecting HTTP REST endpoints (uses stdio and is local to the client machine)
- • Environments needing strict query safety/SQL governance beyond JDBC driver behavior
Interface
Authentication
README indicates that if the underlying data source uses OAuth, authentication happens in a browser as part of configuring the JDBC connection string. It does not document fine-grained scopes at the MCP layer.
Pricing
No pricing details are provided in the README for this repository; licensing pertains to the CData JDBC Driver.
Agent Metadata
Known Gotchas
- ⚠ The server uses stdio, so it must run on the same machine as the MCP client.
- ⚠ Tool discovery/schema retrieval is via CSV outputs; agents should handle CSV parsing robustly.
- ⚠ Only SELECT queries are described; attempting non-SELECT or write operations may not work (read-only MCP server).
- ⚠ Large result sets may be problematic; the README does not describe limits, streaming, or pagination.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for sas-data-sets-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.