Microsoft Planner by CData

What it is

A local MCP server built on the CData JDBC Driver for Microsoft Planner, which exposes Planner as relational SQL models. A model gets table discovery, column discovery and one read-only query tool. It runs over stdio, so the client has to be on the same machine.

What you get

• The Microsoft Planner tables the driver exposes, returned as CSV with a header row — msplanner_get_tables
• The columns of a chosen table, so queries reference real field names — msplanner_get_columns
• A SQL SELECT against live Planner data — msplanner_run_query
• A Tables setting that only picks which tables also get a ready-made description (blank means none); it does not limit what the tools can list or query, so limit the connection or the account it signs in with

Requirements

A Microsoft Planner account and a licensed CData JDBC Driver for Microsoft Planner — a trial licence works, applied with java -jar cdata.jdbc.msplanner.jar --license. Java to run the server, Maven to build it (mvn clean install produces CDataMCP-jar-with-dependencies.jar). The .prp connection file names DriverClass as cdata.jdbc.msplanner.MSPlannerDriver, the driver jar path, a tool Prefix such as msplanner, and the JDBC connection string generated by the driver's Connection String utility — since Planner uses OAuth, that step sends you through a browser sign-in. MIT licensed.

Setup effort

Build from source — git clone https://github.com/cdatasoftware/microsoft-planner-mcp-server-by-cdata.git

Tools you get

3 tools named in the project's documentation. Tool names start with the Prefix in the .prp file, so the README's Prefix=msplanner gives msplanner_get_tables, msplanner_get_columns and msplanner_run_query. All three only read: run_query executes SELECT; write access is in CData's separate MCP Server product.

Where it runs

The documented client runs the server on your machine.