Google Cloud BigQuery vs Databricks MCP Server
Google Cloud BigQuery is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). Databricks MCP Server is an MCP server published by pramodbhatofficial. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Databricks MCP Server | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 133 Stars (GitHub): 11 569 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Downloads/month (PyPI): 206 Downloads/week (PyPI): 49 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Google Cloud BigQuery | Databricks MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 11 569 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 133 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (bigquery.googleapis.com/mcp) | On your machine (databricks-sdk-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cursor/plugins | github.com/pramodbhatofficial/databricks-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 14 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Google Cloud BigQuery
Explore datasets and tables and run SQL queries.
Databricks MCP Server
263 tools for Databricks: Unity Catalog, SQL, Compute, Jobs, Serving, and more.
How to run each
Google Cloud BigQuery
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Databricks MCP Server As a local MCP server: PyPI package
claude mcp add --env "DATABRICKS_HOST=<YOUR_DATABRICKS_HOST>" --env "DATABRICKS_TOKEN=<YOUR_DATABRICKS_TOKEN>" --transport stdio databricks-sdk-mcp -- uvx databricks-sdk-mcpRequires: DATABRICKS_HOST, DATABRICKS_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Google Cloud BigQuery has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Google Cloud BigQuery publish no settings it asks for, so we do not compare settings.
What it can do: Google Cloud BigQuery · What it can do: Databricks MCP Server · Compare two other plugins
Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.