bigquery-mcp

Created By
PaddyAltona year ago
An MCP server to help AI Agents inspect the contents of a BigQuery warehouse
Overview

what is bigquery-mcp?

bigquery-mcp is a Model Context Protocol (MCP) server designed to assist AI agents in inspecting the contents of a BigQuery data warehouse, helping them to generate better SQL queries for data analysis tasks.

how to use bigquery-mcp?

To use bigquery-mcp, ensure you have the necessary prerequisites installed, clone the repository, install dependencies using uv sync, and start the server with the provided command in Cursor IDE settings.

key features of bigquery-mcp?

  • Provides AI agents with tools to examine datasets, tables, columns, and query history in BigQuery.
  • Helps AI agents generate more accurate SQL queries by providing context about database contents.
  • Integrates with Cursor IDE for seamless operation.

use cases of bigquery-mcp?

  1. Assisting AI agents in writing SQL queries for data analysis.
  2. Enabling better understanding of database structures for AI-driven applications.
  3. Improving the efficiency of data-related tasks performed by AI agents.

FAQ from bigquery-mcp?

  • What are the prerequisites for using bigquery-mcp?

You need to have the uv dependency management tool and Taskfile installed, along with gcloud for creating a BigQuery client.

  • Is bigquery-mcp free to use?

Yes! bigquery-mcp is open-source and available for free on GitHub.

  • How does bigquery-mcp improve AI agents' performance?

By providing context about the contents of the database, it helps AI agents write better SQL queries, thus enhancing their data analysis capabilities.

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

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago