servers / com-googleapis-bigtableadmin-mcp
com.googleapis.bigtableadmin/mcp
communitystreamable_httpremotedestructive capablehealthy
Interact with your Google Bigtable resources using natural language commands.
01Tools · 14
| Tool | Risk | Side effects | Approval |
|---|---|---|---|
| create_instance Create a new instance in the specified project.
The request requires project_id, instance_id, display_name, and at least one cluster.
The instance_id must be RFC 1035 compliant.
Each cluster must specify its zone (e.g. us-central1-a).
Example: { "project_id": "my-project", "instance_id": "my-instance", "display_name": "This is my instance", "clusters": [ { "zone": "us-central1-a", "serve_nodes": 3, "default_storage_type": "SSD" } ] }
| write | true | unknown |
| get_instance Get information about an instance.
The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}'.
Example: { "name": "projects/my-project/instances/my-instance" }
| write | true | unknown |
| list_instances List information about instances in a project.
The request requires the 'parent' field to be set in the format 'projects/{project}'.
Example: { "parent": "projects/my-project" }
| write | true | unknown |
| delete_instance Delete an instance from a project.
The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}'.
Example: { "name": "projects/my-project/instances/my-instance" }
Before executing the deletion, you MUST confirm the action with the user by stating the full instance name and asking for "yes/no" confirmation.
| destructive | true | true |
| create_table Create a new table in the specified instance.
| write | true | unknown |
| get_table Get metadata information about the specified table.
The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}/tables/{table}'.
Example: { "name": "projects/my-project/instances/my-instance/tables/my-table" }
| write | true | unknown |
| list_tables List all tables in a specified instance.
The request requires the 'parent' field to be set in the format 'projects/{project}/instances/{instance}'.
Example: { "parent": "projects/my-project/instances/my-instance" }
| write | true | unknown |
| delete_table Delete a table.
The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}/tables/{table}'.
Example: { "name": "projects/my-project/instances/my-instance/tables/my-table" }
The table must exist. You can use `list_tables` to verify.
Before executing the deletion, you MUST confirm the action with the user by stating the full table name and asking for "yes/no" confirmation.
| destructive | true | true |
| create_logical_view Create a new Bigtable logical view within a specified instance.
The request requires project_id, instance_id, logical_view_id, and logical_view.
The logical_view_id can be any name up to 128 characters.
Example: { "project_id": "my-project", "instance_id": "my-instance", "logical_view_id": "my-logical-view", logical_view: { "query": "SELECT CF FROM my-table" } }
| write | true | unknown |
| get_logical_view Get information about the specified logical view.
The request requires the `name` field to be set in the format 'projects/{project}/instances/{instance}/logicalViews/{logical_view}'.
Example: { "name": "projects/my-project/instances/my-instance/logicalViews/my-logical-view" }
| write | true | unknown |
| list_logical_views List information about all logical views within a specified instance.
The request requires the `parent` field to be set in the format 'projects/{project}/instances/{instance}'.
Example: { "parent": "projects/my-project/instances/my-instance" }
| write | true | unknown |
| update_logical_view Updates a Bigtable logical view within a specified instance. You can update the GoogleSQL query and/or the deletion protection setting.
At least one field to update (e.g., `query` or `deletion_protection`) must be provided in logical_view field.
Update query example: { "project_id": "my-project", "instance_id": "my-instance", "logical_view_id": "my-logical-view", logical_view: { "query": "SELECT CF FROM my-table" } }
Update deletion protection example: { "project_id": "my-project", "instance_id": "my-instance", "logical_view_id": "my-logical-view", logical_view: { "deletion_protection": true } }
Update query and deletion protection example: { "project_id": "my-project", "instance_id": "my-instance", "logical_view_id": "my-logical-view", logical_view: { "query": "SELECT CF FROM my-table", "deletion_protection": true } }
| write | true | unknown |
| list_hot_tablets Lists hot tablets in a Cloud Bigtable cluster.
Start time defaults to Now if it is unset, and end time defaults to Now - 24 hours if it is unset. The start time should be less than the end time, and the maximum allowed time range between start time and end time is 48 hours. Start time and end time should have values between Now and Now - 14 days.
| read | unknown | unknown |
| delete_logical_view Deletes a Bigtable logical view within a specified instance.
The request requires the `name` field to be set in the format 'projects/{project}/instances/{instance}/logicalViews/{logical_view}'.
Example: { "name": "projects/my-project/instances/my-instance/logicalViews/my-logical-view" }
Before executing the deletion, you MUST confirm the action with the user by stating the full logical view name and asking for "yes/no" confirmation.
| destructive | true | unknown |
02Install & source
https://bigtableadmin.googleapis.com/mcp
remote_url03Access granted
Query a database · destructive
The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.
05Provenance & freshness
sourcesOfficial MCP Registry [p1]
last_checked2026-07-07 08:50Z
next_check2026-07-09 08:42Z
cadenceevery 48h
verifiedtools_list:passed handshake:passed metadata:passed
index_statusindex — 5 unique facts >= 5
06Badge
Add the “as seen on MCPExplorer” badge to your README.
[](https://mcpexplorer.com/servers/com-googleapis-bigtableadmin-mcp)
Next step
This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.
Explore loadouts →