microsoft-teams -by-cdata

This MCP server exposes Microsoft Teams data through a read-only MCP interface by wrapping the CData JDBC Driver for Microsoft Teams. Once running, you can query live Teams data using the built-in MCP tools (e.g., microsoft_teams_get_tables, microsoft_teams_get_columns, microsoft_teams_run_query) via a JSON-RPC style client such as Claude Desktop or any tool that calls the MCP endpoints. The server presents tables and columns derived from the Teams data source and allows read-only SQL-like querying against those tables. Typical usage involves discovering available tables with microsoft_teams_get_tables, inspecting the schema with microsoft_teams_get_columns, and then issuing microsoft_teams_run_query requests to fetch data, all with no SQL layer required for the end user.

Prerequisites:

• Java JDK (recommended version compatible with the CData MCP server and your driver)
• Maven (for building the MCP server from source)
• The CData JDBC Driver for Microsoft Teams installed and licensed on the host machine

Installation steps:

1. Clone the repository: git clone https://github.com/cdatasoftware/microsoft-teams-mcp-server-by-cdata.git cd microsoft-teams-mcp-server-by-cdata

2. Build the server: mvn clean install This will produce the JAR file: CDataMCP-jar-with-dependencies.jar

3. Install and license the CData JDBC Driver for Microsoft Teams:

   • Download from: https://www.cdata.com/drivers/msteams/download/jdbc
   • Follow the license steps in the Driver documentation (as described in the README).

4. Create a .prp file (e.g., microsoft-teams.prp) with the connection details to your Teams data source, using the example structure in the README. Ensure the JdbcUrl and required properties are set for your environment.

5. Start the MCP server locally using the generated JAR and PRP file: java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/microsoft-teams.prp

6. (Optional) Configure Claude Desktop or other clients to connect to the MCP server using the provided JSON config format in the README. Ensure the client can reach the host and port where the MCP server exposes its stdio interface.

Notes and tips:

• This MCP server is read-only by design; write/update/delete actions are not exposed for the Microsoft Teams data source.
• The server uses stdio for communication, so the client must run on the same machine or ensure proper inter-process communication if using local tooling.
• When configuring Claude Desktop, full quit and relaunch may be required for the server to appear in the client list after changes.
• If you encounter connection issues, verify that the JDBC driver is properly licensed, the DriverPath and JdbcUrl in the .prp file are correct, and that any OAuth prompts were completed during connection testing.
• You can customize the server entry name in Claude Desktop by changing the {classname_dash} key in your claude_desktop_config.json to a naming friendly for your environment (e.g., microsoft_teams).