LabscoMCP early access ↗
CDataSoftwareMCP SERVER

Pipedrive MCP Server by CData

Query your Pipedrive CRM — deals, people, activities — as SQL tables, read-only, from an MCP client.

by CDataSoftware ↗SaaS-to-SQL ConnectorsCommunity

LABSCO SUMMARY

Pipeline questions answered with SQL instead of filters.

Deals, organisations and activities come through the CData JDBC Driver as relational tables, which makes the cross-cutting questions easy: deals by stage and owner, activities with no follow-up, everything closed in a quarter. The server cannot move a deal or edit a contact — it reads.

What it is

A Java MCP server that puts CData's JDBC Driver for Pipedrive behind three read-only tools: list the tables, list a table's columns, and run a SQL SELECT. The driver is what does the work — it exposes Pipedrive as relational SQL models — and the server hands those models to your client so you can ask questions in plain language instead of writing SQL yourself.

What you get

  • get_tables returns the tables available in the data source, as CSV with a header row
  • get_columns returns the columns of one table, in the same CSV shape
  • run_query executes a SQL SELECT and returns the rows
  • Every tool name is prefixed with the server name from your .prp file, so several CData servers can run side by side without colliding
  • Questions like "how many open tickets do I have" go straight to the client — it picks the tools and writes the SQL

Requirements

Build the server with mvn clean install, which produces CDataMCP-jar-with-dependencies.jar. Separately download the CData JDBC Driver for Pipedrive and license it: run java -jar cdata.jdbc.pipedrive.jar --license and enter your name, email and either TRIAL or a licence key. Then write a .prp file naming DriverClass=cdata.jdbc.pipedrive.PipedriveDriver plus the JdbcUrl you build in the driver's connection-string utility, and point your client at java -jar with the jar and that file. Transport is stdio, so the server has to run on the same machine as the client.

Setup effort

Build from source — clone the repository, then point your client at the binary