mcp-bigquery-server-with-datacatalog

Created By
atamaplus-publica year ago
Overview

what is mcp-bigquery-server-with-datacatalog?

The mcp-bigquery-server-with-datacatalog is a cloud-based solution that integrates Google BigQuery with a data catalog for efficient data management and querying.

how to use mcp-bigquery-server-with-datacatalog?

To use this project, set up the server by following the instructions in the GitHub repository, configure your data sources, and utilize the BigQuery interface to run queries and manage your data catalog.

key features of mcp-bigquery-server-with-datacatalog?

  • Seamless integration with Google BigQuery.
  • Data cataloging for better data organization and retrieval.
  • Support for various data sources and formats.

use cases of mcp-bigquery-server-with-datacatalog?

  1. Managing large datasets in a cloud environment.
  2. Performing complex queries on structured and unstructured data.
  3. Enhancing data discoverability through cataloging.

FAQ from mcp-bigquery-server-with-datacatalog?

  • What is the primary function of this project?

It serves as a server for managing and querying data using Google BigQuery along with a data catalog.

  • Is there any cost associated with using this project?

The project is open-source and free to use, but Google BigQuery may have associated costs based on usage.

  • How can I contribute to the project?

Contributions can be made by submitting pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
atamaplus-public
Star
0
Language
-
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)

a day ago