ssas -by-cdata

This MCP server exposes a read-only interface to SQL Server Analysis Services through the CData JDBC Driver, letting LLMs like Claude Desktop query live SSAS data without writing SQL. After starting the server with the provided Java command and .prp file, you’ll connect via Claude Desktop (or any MCP-compatible client) using the configured mcpServers entry. The server exposes a compact set of tools that you can call with JSON-RPC: ssas_get_tables to list available tables, ssas_get_columns to list columns for a table, and ssas_run_query to execute a SELECT query. The tools return data in CSV format for tables/columns and standard results for queries, enabling natural-language questions like “What are my open opportunities?” to be translated into structured data fetches. See the README’s JSON-RPC examples for precise request shapes. Note that this MCP server is read-only by design, focusing on retrieving live SSAS data through the JDBC bridge.

Prerequisites:\n- Java Runtime (JRE) or JDK installed and accessible in PATH.\n- Maven (for building the server) if you’re building from source.\n- CData JDBC Driver for SQL Server Analysis Services installed and licensed, plus a configured .prp file (ssas.prp) and the corresponding JDBC driver JAR available.\n\nInstallation steps:\n1) Build the MCP server (from source):\nbash\ngit clone https://github.com/cdatasoftware/ssas-mcp-server-by-cdata.git\ncd ssas-mcp-server-by-cdata\nmvn clean install\n\nThis creates the JAR file: CDataMCP-jar-with-dependencies.jar.\n2) Obtain and license the CData JDBC Driver for SSAS following the project’s setup guide: download the driver, run the license command from the driver’s lib folder, and test the connection to your SSAS source.\n3) Configure a .prp file (e.g., ssas.prp) with your JDBC connection details as described in the README (Prefix, ServerName, ServerVersion, DriverPath, DriverClass, JdbcUrl, Tables).\n4) Run the MCP server: use the command below (adjust paths to your environment).\nbash\njava -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/ssas.prp\n\n5) If you plan to integrate with Claude Desktop, add the server entry to claude_desktop_config.json as shown in the README, using the same JAR and PRP paths.\n6) Ensure the client and server are on the same machine (the server uses stdio).

Tips and notes: The server is designed to be run locally (stdio). If Claude Desktop doesn’t show the MCP server, fully quit and relaunch Claude Desktop. Ensure your SSAS connection string (in ssas.prp) is correct and tested via the CData JDBC Driver’s connection utility. If you encounter issues, verify that the JDBC Driver is licensed and that the DriverPath, DriverClass, and JdbcUrl in your .prp file are accurate. For OAuth-enabled sources, you may need to complete authentication in a browser during setup. This server exposes the following tools, referenced by the server name you configure (e.g., ssas): ssas_get_tables, ssas_get_columns, ssas_run_query. If you run into environment-specific path issues, adjust the placeholder paths in the mcp_config accordingly and ensure Java can access the .jar and .prp files.