Skip to directory

About Bigtable MCP

Google Cloud managed MCP server for Bigtable. Exact tool names and accessible operations depend on the published server reference and configured Google Cloud permissions.

Connection and setup
Hosting
Google-managed remote
Transport
Streamable HTTP
Endpoint
Local process; no hosted endpoint documented
Authentication
Google Cloud authentication: OAuth 2.0 using Application Default Credentials (ADC) in supported Google clients, or a client OAuth ID/secret or bearer token in compatible third-party clients. The principal needs mcp.tools.call plus the underlying product permissions; API key authentication is only available for services that explicitly support it.

Requirements

  • A Google Cloud project and access to the target product/resource.
  • Enable this MCP service and its underlying Google Cloud API as required by the product guide.
  • An MCP client that supports Streamable HTTP.
  • An identity with the MCP Tool User role (roles/mcp.toolUser) or equivalent mcp.tools.call permission, plus permissions for the underlying product operations.

Setup steps

  1. Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint.
  2. In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it.
  3. Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client.
  4. Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations.
  5. Add bigtableadmin.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in.
  6. Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset.
Tools 16+

The 16 stored names combine 15 documented Bigtable Admin tools and the separate Data MCP execute_sql tool. Admin operations can create/delete instances, tables and views; execute_sql can read or write table data. Keep admin and data scopes separate; all calls use Google OAuth/IAM and incur ordinary Bigtable resource charges.

  • create_instance
    01
  • get_instance
    02
  • list_instances
    03
  • delete_instance
    04
  • create_table
    05
  • get_table
    06
  • list_tables
    07
  • delete_table
    08
  • create_logical_view
    09
  • get_logical_view
    10
  • list_logical_views
    11
  • update_logical_view
    12
  • delete_logical_view
    13
  • list_hot_tablets
    14
  • get_system_metrics
    15
  • execute_sql
    16

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Original sources

Documentation checked 2026-10-28. Connection has not been runtime tested.