google-bigquery-mcp-server-by-cdata

Created By
CDataSoftwarea year ago
This read-only MCP Server allows you to connect to Google BigQuery data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at
Overview

What is Google BigQuery MCP Server?

The Google BigQuery MCP Server by CData is a read-only server that allows users to connect to Google BigQuery data from Claude Desktop using CData JDBC Drivers. It enables LLMs to query live data without needing to write SQL queries.

How to use Google BigQuery MCP Server?

To use the server, clone the repository, build the server, install the CData JDBC Driver, configure your connection, and create a configuration file for Claude Desktop. Finally, run the server and refresh your client to access the data.

Key features of Google BigQuery MCP Server?

  • Read-only access to Google BigQuery data.
  • Natural language querying capabilities for LLMs.
  • Simplified setup process for connecting to data sources.

Use cases of Google BigQuery MCP Server?

  1. Querying live data from Google BigQuery using natural language.
  2. Integrating with AI clients like Claude Desktop for data retrieval.
  3. Accessing and managing data from various sources through a unified interface.

FAQ from Google BigQuery MCP Server?

  • Can I write data to Google BigQuery using this server?

No, this server is read-only. For write capabilities, consider using the full CData MCP Server for Google BigQuery.

  • Is there a cost associated with using the server?

The server is currently in beta and is free to use.

  • What programming language is the server built with?

The server is built using Java.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CDataSoftware
Star
0
Language
Java
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago