CData JDBC Driver connects to Google Contacts by exposing them as relational SQL models.
Connect Google Contacts By Cdata to Claude, Cursor or any other MCP client and it stops being a tab you switch to. CData JDBC Driver connects to Google Contacts by exposing them as relational SQL models. The google contacts by cdata mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
source_get_tables — The source_get_tables tool exposed by this serversource_get_columns — The source_get_columns tool exposed by this serversource_run_query — The source_run_query tool exposed by this serverBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Google Contacts By Cdata's toolset — source_get_tables, source_get_columns, source_run_query — is a fair guide to whether it matches your workflow. It is maintained by CDataSoftware; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Google Contacts By Cdata's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| source_get_tables | The source_get_tables tool exposed by this server. |
| source_get_columns | The source_get_columns tool exposed by this server. |
| source_run_query | The source_run_query tool exposed by this server. |
**Linux/Mac**
```json
{
"mcpServers": {
"{classname_dash}": {
"command": "/PATH/TO/java",
"args": [
"-jar",
"/PATH/TO/CDataMCP-jar-with-dependencies.jar",
"/PATH/TO/google-contacts.prp"
]
},
...
}
}Configuration as documented by the project. Restart the client after saving.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.