pinterest_get_tablesLABSCO SUMMARY
Read-only by construction, and the vendor says so up front.
Only SELECT gets through, which makes this safe to point at a live account but means it cannot create or update anything — CData directs you to its own commercial MCP server for that. The setup cost is front-loaded and mostly belongs to the driver rather than the server: installing it, licensing it, and getting a connection string that tests clean. Once that works, the MCP side is a JAR and a properties file.
What it is
A thin MCP wrapper around the CData JDBC Driver for Pinterest. The driver models the Pinterest API as relational tables, and the server exposes those tables so an assistant can answer questions with SELECT statements it writes itself.
What you get
- Three tools, each named with the prefix you set in the connection properties file: list the tables the driver exposes, list a table's columns, and run a SQL SELECT query
- Results come back as CSV with a header row on the first line
- A
Tablessetting 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 - The same server pattern covers CData's other JDBC sources, so the shape carries across connectors
Requirements
Java and Maven — mvn clean install builds a JAR with dependencies. Separately, the CData JDBC Driver for Pinterest must be installed and licensed by running its jar with --license and entering a name, an email and either TRIAL or a licence key. Then write a .prp file naming the prefix, the driver path, the driver class and the JDBC connection string; the driver ships a utility that builds and tests that string, opening a browser for OAuth. Transport is stdio only, so client and server run on the same machine.
Setup effort
Build from source — clone the repository, then point your client at the binary
USE CASES
Asking a question about your Pinterest data without SQL
Describe what you want; the assistant discovers the tables and columns and writes the query itself.
Working out what data is even available
List the tables, then the columns on the one that looks right, before writing anything.
Limiting what the assistant can see
Name specific tables in the properties file so the rest of the account is out of scope.
3 tools
Listed in project docs. Your client may show a different list.
pinterest_get_columnspinterest_run_queryBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation. Tool names take the Prefix from your .prp file, such as pinterest_get_tables. Read-only: run_query executes SELECT only, despite a boilerplate claim of write support.
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Clone the repository, then point your client at the binary. This one is built from source rather than installed with a single command.
Server setup
git clone https://github.com/cdatasoftware/pinterest-mcp-server-by-cdata.git
cd pinterest-mcp-server-by-cdata
mvn clean installDownload and install the CData JDBC Driver for Pinterest from https://www.cdata.com/drivers/pinterest/download/jdbc
License the driver: from the driver install's lib folder run java -jar cdata.jdbc.pinterest.jar --license, then enter your name, email, and "TRIAL" (or your license key)
Build the connection string: run java -jar cdata.jdbc.pinterest.jar to open the Connection String utility, click "Test Connection" (browser OAuth if the source needs it), and copy the connection string
Create pinterest.prp with:
Prefix=pinterest
ServerName=CDataPinterest
ServerVersion=1.0
DriverPath=<YOUR_DRIVER_PATH>
DriverClass=cdata.jdbc.pinterest.PinterestDriver
JdbcUrl=<YOUR_JDBC_URL>
Tables=Tables only picks which tables also get a ready-made description for your assistant, and empty means none; the server can still list and query every table your connection string reaches, so to keep data out of reach, limit that connection or the account it signs in with.
Add the mcpServers entry (block below) to claude_desktop_config.json, then fully quit and re-open the client
MCP Clients
Claude Desktop — macOS/Linux, Windows
{
"mcpServers": {
"pinterest": {
"command": "<YOUR_PATH_TO_JAVA>",
"args": [
"-jar",
"<YOUR_PATH_TO_CDATA_MCP_JAR_WITH>",
"<YOUR_PATH_TO_PINTEREST>"
]
}
}
}