ssas-mcp-server-by-cdata
Provides a read-only Model Context Protocol (MCP) server that exposes SQL Server Analysis Services data to MCP clients by wrapping the CData JDBC Driver for SQL Server Analysis Services. It supports listing tables/columns and executing SQL SELECT queries over the underlying SSAS data via MCP tools.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Transport security is not explicitly described for the MCP stdio channel or for the JDBC connection in the README. Authentication is handled by the CData JDBC driver; OAuth is mentioned but MCP-side scope granularity is not documented. Connection configuration is placed in a local .prp file, and the README includes example JDBC URL content; it does not describe secret redaction, logging behavior, or safe handling of credentials. Because the MCP server can run user-supplied SELECT SQL, prompt-to-SQL misuse risk exists (e.g., requesting broader-than-expected data) unless the JDBC driver enforces least-privilege at the data source.
⚡ Reliability
Best When
You want local, read-only SSAS data access from an MCP-capable desktop client, using CData’s JDBC driver and configuration files to establish the SSAS connection.
Avoid When
You need a remotely accessible service over HTTP with documented rate limits, retries, and pagination, or you require write access / transactional operations.
Use Cases
- • Answer natural-language questions over live SSAS data (e.g., sales, KPIs, calendar events) without writing SQL
- • Discovery workflows: list available SSAS tables and columns for a chosen dataset
- • Ad-hoc read-only analytics by running SELECT queries through an MCP client (e.g., Claude Desktop)
Not For
- • Writing/updating/deleting data in SSAS (explicitly read-only MCP server)
- • Production deployments requiring networked/remote access (server uses stdio, local-process model)
- • Use cases needing REST/GraphQL-style HTTP APIs or hosted endpoints
Interface
Authentication
Authentication is delegated to the CData JDBC driver via the connection string used in the .prp file. The README mentions OAuth flows may require browser authentication, but does not describe scopes or fine-grained authorization within the MCP server itself.
Pricing
No MCP server pricing details are provided; JDBC driver licensing is required.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio, so it must run on the same machine as the MCP client (e.g., Claude Desktop).
- ⚠ The tool list depends on the configured connection/table visibility in the generated .prp (Tables property).
- ⚠ If the MCP server does not appear in the client, the README suggests fully quitting and reopening the desktop client.
- ⚠ Large SELECT queries may be expensive/slow, but there is no documented guardrail (limits/timeouts) in the README provided.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for ssas-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.