CData JDBC Driver connects to Google Calendars by exposing them as relational SQL models.
If you already use Google Calendars By Cdata, the google calendars by cdata mcp server is the piece that lets your assistant work with it directly. CData JDBC Driver connects to Google Calendars by exposing them as relational SQL models.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
google_calendars_get_tables — The google_calendars_get_tables tool exposed by this servergoogle_calendars_get_columns — The google_calendars_get_columns tool exposed by this servergoogle_calendars_run_query — The google_calendars_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 Calendars By Cdata's toolset — google_calendars_get_tables, google_calendars_get_columns, google_calendars_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.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| google_calendars_get_tables | The google_calendars_get_tables tool exposed by this server. |
| google_calendars_get_columns | The google_calendars_get_columns tool exposed by this server. |
| google_calendars_run_query | The google_calendars_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-calendars.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.