CData JDBC Driver connects to Google BigQuery by exposing them as relational SQL models.
Google Bigquery By Cdata MCP server exists for a simple reason — assistants are far more useful when they can act on Google Bigquery By Cdata directly instead of describing what you should do. CData JDBC Driver connects to Google BigQuery by exposing them as relational SQL models.
Once Google Bigquery By Cdata is connected, these are the calls the assistant has available:
google_bigquery_get_tables — The google_bigquery_get_tables tool exposed by this servergoogle_bigquery_get_columns — The google_bigquery_get_columns tool exposed by this servergoogle_bigquery_run_query — The google_bigquery_run_query tool exposed by this serverBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Google Bigquery By Cdata's toolset — google_bigquery_get_tables, google_bigquery_get_columns, google_bigquery_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.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| google_bigquery_get_tables | The google_bigquery_get_tables tool exposed by this server. |
| google_bigquery_get_columns | The google_bigquery_get_columns tool exposed by this server. |
| google_bigquery_run_query | The google_bigquery_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-bigquery.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.