mirror of
https://github.com/googleapis/genai-toolbox.git
synced 2026-01-11 16:38:15 -05:00
Compare commits
2 Commits
spanner-cr
...
antigravit
| Author | SHA1 | Date | |
|---|---|---|---|
|
89c85729d1 | ||
|
|
93f638650d |
@@ -54,18 +54,8 @@ An editor configured to use the AlloyDB MCP server can use its AI capabilities t
|
||||
|
||||
### Configuration
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"alloydb-admin": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "alloydb-postgres-admin", "--stdio"],
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "AlloyDB for PostgreSQL Admin", and click "Install".
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -57,33 +57,20 @@ An editor configured to use the AlloyDB MCP server can use its AI capabilities t
|
||||
|
||||
### Configuration
|
||||
|
||||
The AlloyDB MCP server is configured using environment variables.
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "AlloyDB for PostgreSQL", and click "Install".
|
||||
3. **Configuration**: The following configuration is needed for the server:
|
||||
* AlloyDB Project ID: The GCP project ID.
|
||||
* AlloyDB Region: The region of your AlloyDB instance.
|
||||
* AlloyDB Cluster ID: The ID of your AlloyDB cluster.
|
||||
* AlloyDB Instance ID: The ID of your AlloyDB instance.
|
||||
* AlloyDB Database Name: The name of the database.
|
||||
* AlloyDB Database User: (Optional) The database username. Defaults to IAM authentication if unspecified.
|
||||
* AlloyDB Database Password: (Optional) The password for the database user. Defaults to IAM authentication if unspecified.
|
||||
* AlloyDB IP Type: (Optional) The IP type i.e. “Public” or “Private”. Defaults to "Public" if unspecified.
|
||||
|
||||
```bash
|
||||
export ALLOYDB_POSTGRES_PROJECT="<your-gcp-project-id>"
|
||||
export ALLOYDB_POSTGRES_REGION="<your-alloydb-region>"
|
||||
export ALLOYDB_POSTGRES_CLUSTER="<your-alloydb-cluster-id>"
|
||||
export ALLOYDB_POSTGRES_INSTANCE="<your-alloydb-instance-id>"
|
||||
export ALLOYDB_POSTGRES_DATABASE="<your-database-name>"
|
||||
export ALLOYDB_POSTGRES_USER="<your-database-user>" # Optional
|
||||
export ALLOYDB_POSTGRES_PASSWORD="<your-database-password>" # Optional
|
||||
export ALLOYDB_POSTGRES_IP_TYPE="PUBLIC" # Optional: `PUBLIC`, `PRIVATE`, `PSC`. Defaults to `PUBLIC`.
|
||||
```
|
||||
|
||||
> **Note:** If your AlloyDB instance uses private IPs, you must run the MCP server in the same Virtual Private Cloud (VPC) network.
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"alloydb-postgres": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "alloydb-postgres", "--stdio"],
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
> [!NOTE]
|
||||
> If your AlloyDB instance uses private IPs, you must run the MCP server in the same Virtual Private Cloud (VPC) network.
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -55,26 +55,11 @@ An editor configured to use the BigQuery MCP server can use its AI capabilities
|
||||
|
||||
### Configuration
|
||||
|
||||
The BigQuery MCP server is configured using environment variables.
|
||||
|
||||
```bash
|
||||
export BIGQUERY_PROJECT="<your-gcp-project-id>"
|
||||
export BIGQUERY_LOCATION="<your-dataset-location>" # Optional
|
||||
export BIGQUERY_USE_CLIENT_OAUTH="true" # Optional
|
||||
```
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"bigquery": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "bigquery", "--stdio"],
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "BigQuery", and click "Install".
|
||||
3. **Configuration**: The following configuration is needed for the server:
|
||||
* BigQuery Project ID: The GCP project ID.
|
||||
* BigQuery Location: (Optional) The location of your BigQuery dataset (e.g. "US", "EU").
|
||||
|
||||
### Usage
|
||||
|
||||
|
||||
@@ -54,18 +54,8 @@ An editor configured to use the Cloud SQL for SQL Server MCP server can use its
|
||||
|
||||
### Configuration
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"cloud-sql-sqlserver-admin": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "cloud-sql-mssql-admin", "--stdio"],
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "Cloud SQL for SQL Server Admin", and click "Install".
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -54,40 +54,20 @@ An editor configured to use the Cloud SQL for SQL Server MCP server can use its
|
||||
|
||||
### Configuration
|
||||
|
||||
The MCP server is configured using environment variables.
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "Cloud SQL for SQL Server", and click "Install".
|
||||
3. **Configuration**: The following configuration is needed for the server:
|
||||
* Cloud SQL Project ID: The GCP project ID.
|
||||
* Cloud SQL Region: The region of your Cloud SQL instance.
|
||||
* Cloud SQL Instance ID: The ID of your Cloud SQL instance.
|
||||
* Cloud SQL Database Name: The name of the database.
|
||||
* Cloud SQL Database User: The database username.
|
||||
* Cloud SQL Database Password: The password for the database user.
|
||||
* Cloud SQL IP Type: (Optional) The IP type i.e. “Public” or “Private”. Defaults to "Public" if unspecified.
|
||||
|
||||
```bash
|
||||
export CLOUD_SQL_MSSQL_PROJECT="<your-gcp-project-id>"
|
||||
export CLOUD_SQL_MSSQL_REGION="<your-cloud-sql-region>"
|
||||
export CLOUD_SQL_MSSQL_INSTANCE="<your-cloud-sql-instance-id>"
|
||||
export CLOUD_SQL_MSSQL_DATABASE="<your-database-name>"
|
||||
export CLOUD_SQL_MSSQL_USER="<your-database-user>" # Optional
|
||||
export CLOUD_SQL_MSSQL_PASSWORD="<your-database-password>" # Optional
|
||||
export CLOUD_SQL_MSSQL_IP_TYPE="PUBLIC" # Optional: `PUBLIC`, `PRIVATE`, `PSC`. Defaults to `PUBLIC`.
|
||||
```
|
||||
> [!NOTE]
|
||||
> If your instance uses private IPs, you must run the MCP server in the same Virtual Private Cloud (VPC) network.
|
||||
|
||||
> **Note:** If your instance uses private IPs, you must run the MCP server in the same Virtual Private Cloud (VPC) network.
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"cloud-sql-mssql": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "cloud-sql-mssql", "--stdio"],
|
||||
"env": {
|
||||
"CLOUD_SQL_MSSQL_PROJECT": "your-project-id",
|
||||
"CLOUD_SQL_MSSQL_REGION": "your-region",
|
||||
"CLOUD_SQL_MSSQL_INSTANCE": "your-instance-id",
|
||||
"CLOUD_SQL_MSSQL_DATABASE": "your-database-name",
|
||||
"CLOUD_SQL_MSSQL_USER": "your-username",
|
||||
"CLOUD_SQL_MSSQL_PASSWORD": "your-password"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -54,18 +54,8 @@ An editor configured to use the Cloud SQL for MySQL MCP server can use its AI ca
|
||||
|
||||
### Configuration
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"cloud-sql-mysql-admin": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "cloud-sql-mysql-admin", "--stdio"]
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "Cloud SQL for MySQL Admin", and click "Install".
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -56,40 +56,19 @@ An editor configured to use the Cloud SQL for MySQL MCP server can use its AI ca
|
||||
|
||||
### Configuration
|
||||
|
||||
The MCP server is configured using environment variables.
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "Cloud SQL for MySQL", and click "Install".
|
||||
3. **Configuration**: The following configuration is needed for the server:
|
||||
* Cloud SQL Project ID: The GCP project ID.
|
||||
* Cloud SQL Region: The region of your Cloud SQL instance.
|
||||
* Cloud SQL Instance ID: The ID of your Cloud SQL instance.
|
||||
* Cloud SQL Database Name: The name of the database.
|
||||
* Cloud SQL Database User: The database username.
|
||||
* Cloud SQL Database Password: The password for the database user.
|
||||
* Cloud SQL IP Type: (Optional) The IP type i.e. “Public” or “Private”. Defaults to "Public" if unspecified.
|
||||
|
||||
```bash
|
||||
export CLOUD_SQL_MYSQL_PROJECT="<your-gcp-project-id>"
|
||||
export CLOUD_SQL_MYSQL_REGION="<your-cloud-sql-region>"
|
||||
export CLOUD_SQL_MYSQL_INSTANCE="<your-cloud-sql-instance-id>"
|
||||
export CLOUD_SQL_MYSQL_DATABASE="<your-database-name>"
|
||||
export CLOUD_SQL_MYSQL_USER="<your-database-user>" # Optional
|
||||
export CLOUD_SQL_MYSQL_PASSWORD="<your-database-password>" # Optional
|
||||
export CLOUD_SQL_MYSQL_IP_TYPE="PUBLIC" # Optional: `PUBLIC`, `PRIVATE`, `PSC`. Defaults to `PUBLIC`.
|
||||
```
|
||||
|
||||
> **Note:** If your instance uses private IPs, you must run the MCP server in the same Virtual Private Cloud (VPC) network.
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"cloud-sql-mysql": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "cloud-sql-mysql", "--stdio"],
|
||||
"env": {
|
||||
"CLOUD_SQL_MYSQL_PROJECT": "your-project-id",
|
||||
"CLOUD_SQL_MYSQL_REGION": "your-region",
|
||||
"CLOUD_SQL_MYSQL_INSTANCE": "your-instance-id",
|
||||
"CLOUD_SQL_MYSQL_DATABASE": "your-database-name",
|
||||
"CLOUD_SQL_MYSQL_USER": "your-username",
|
||||
"CLOUD_SQL_MYSQL_PASSWORD": "your-password"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
> [!NOTE]
|
||||
> If your instance uses private IPs, you must run the MCP server in the same Virtual Private Cloud (VPC) network.
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -54,18 +54,8 @@ An editor configured to use the Cloud SQL for PostgreSQL MCP server can use its
|
||||
|
||||
### Configuration
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"cloud-sql-postgres-admin": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "cloud-sql-postgres-admin", "--stdio"]
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "Cloud SQL for PostgreSQL Admin", and click "Install".
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -56,41 +56,20 @@ An editor configured to use the Cloud SQL for PostgreSQL MCP server can use its
|
||||
|
||||
### Configuration
|
||||
|
||||
The MCP server is configured using environment variables.
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "Cloud SQL for PostgreSQL", and click "Install".
|
||||
3. **Configuration**: The following configuration is needed for the server:
|
||||
* Cloud SQL Project ID: The GCP project ID.
|
||||
* Cloud SQL Region: The region of your Cloud SQL instance.
|
||||
* Cloud SQL Instance ID: The ID of your Cloud SQL instance.
|
||||
* Cloud SQL Database Name: The name of the database.
|
||||
* Cloud SQL Database User: (Optional) The database username. Defaults to IAM authentication if unspecified.
|
||||
* Cloud SQL Database Password: (Optional) The password for the database user. Defaults to IAM authentication if unspecified.
|
||||
* Cloud SQL IP Type: (Optional) The IP type i.e. “Public” or “Private”. Defaults to "Public" if unspecified.
|
||||
|
||||
```bash
|
||||
export CLOUD_SQL_POSTGRES_PROJECT="<your-gcp-project-id>"
|
||||
export CLOUD_SQL_POSTGRES_REGION="<your-cloud-sql-region>"
|
||||
export CLOUD_SQL_POSTGRES_INSTANCE="<your-cloud-sql-instance-id>"
|
||||
export CLOUD_SQL_POSTGRES_DATABASE="<your-database-name>"
|
||||
export CLOUD_SQL_POSTGRES_USER="<your-database-user>" # Optional
|
||||
export CLOUD_SQL_POSTGRES_PASSWORD="<your-database-password>" # Optional
|
||||
export CLOUD_SQL_POSTGRES_IP_TYPE="PUBLIC" # Optional: `PUBLIC`, `PRIVATE`, `PSC`. Defaults to `PUBLIC`.
|
||||
```
|
||||
> [!NOTE]
|
||||
> If your instance uses private IPs, you must run the MCP server in the same Virtual Private Cloud (VPC) network.
|
||||
|
||||
> **Note:** If your instance uses private IPs, you must run the MCP server in the same Virtual Private Cloud (VPC) network.
|
||||
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"cloud-sql-postgres": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "cloud-sql-postgres", "--stdio"],
|
||||
"env": {
|
||||
"CLOUD_SQL_POSTGRES_PROJECT": "your-project-id",
|
||||
"CLOUD_SQL_POSTGRES_REGION": "your-region",
|
||||
"CLOUD_SQL_POSTGRES_INSTANCE": "your-instance-id",
|
||||
"CLOUD_SQL_POSTGRES_DATABASE": "your-database-name",
|
||||
"CLOUD_SQL_POSTGRES_USER": "your-username",
|
||||
"CLOUD_SQL_POSTGRES_PASSWORD": "your-password"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -54,27 +54,10 @@ An editor configured to use the Dataplex MCP server can use its AI capabilities
|
||||
|
||||
### Configuration
|
||||
|
||||
The MCP server is configured using environment variables.
|
||||
|
||||
```bash
|
||||
export DATAPLEX_PROJECT="<your-gcp-project-id>"
|
||||
```
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"dataplex": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "dataplex", "--stdio"],
|
||||
"env": {
|
||||
"DATAPLEX_PROJECT": "your-project-id"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "Dataplex", and click "Install".
|
||||
3. **Configuration**: The following configuration is needed for the server:
|
||||
* Dataplex Project ID: The GCP project ID.
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -56,35 +56,17 @@ An editor configured to use the Looker MCP server can use its AI capabilities to
|
||||
|
||||
### Configuration
|
||||
|
||||
The MCP server is configured using environment variables.
|
||||
|
||||
```bash
|
||||
export LOOKER_BASE_URL="<your-looker-instance-url>" # e.g. `https://looker.example.com`. You may need to add the port, i.e. `:19999`.
|
||||
export LOOKER_CLIENT_ID="<your-looker-client-id>"
|
||||
export LOOKER_CLIENT_SECRET="<your-looker-client-secret>"
|
||||
export LOOKER_VERIFY_SSL="true" # Optional, defaults to true
|
||||
export LOOKER_SHOW_HIDDEN_MODELS="true" # Optional, defaults to true
|
||||
export LOOKER_SHOW_HIDDEN_EXPLORES="true" # Optional, defaults to true
|
||||
export LOOKER_SHOW_HIDDEN_FIELDS="true" # Optional, defaults to true
|
||||
```
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"looker": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "looker", "--stdio"],
|
||||
"env": {
|
||||
"LOOKER_BASE_URL": "https://your.looker.instance.com",
|
||||
"LOOKER_CLIENT_ID": "your-client-id",
|
||||
"LOOKER_CLIENT_SECRET": "your-client-secret"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "Looker", and click "Install".
|
||||
3. **Configuration**: The following configuration is needed for the server:
|
||||
* Looker Base URL: The URL of your Looker instance.
|
||||
* Looker Client ID: The client ID for the Looker API.
|
||||
* Looker Client Secret: The client secret for the Looker API.
|
||||
* Looker Verify SSL: Whether to verify SSL certificates.
|
||||
* Looker Use Client OAuth: Whether to use OAuth for authentication.
|
||||
* Looker Show Hidden Models: Whether to show hidden models.
|
||||
* Looker Show Hidden Explores: Whether to show hidden explores.
|
||||
* Looker Show Hidden Fields: Whether to show hidden fields.
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -55,33 +55,13 @@ An editor configured to use the Cloud Spanner MCP server can use its AI capabili
|
||||
|
||||
### Configuration
|
||||
|
||||
The MCP server is configured using environment variables.
|
||||
|
||||
```bash
|
||||
export SPANNER_PROJECT="<your-gcp-project-id>"
|
||||
export SPANNER_INSTANCE="<your-spanner-instance-id>"
|
||||
export SPANNER_DATABASE="<your-spanner-database-id>"
|
||||
export SPANNER_DIALECT="googlesql" # Optional: "googlesql" or "postgresql". Defaults to "googlesql".
|
||||
```
|
||||
|
||||
Add the following configuration to your MCP client (e.g., `settings.json` for Gemini CLI):
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"spanner": {
|
||||
"command": "toolbox",
|
||||
"args": ["--prebuilt", "spanner", "--stdio"],
|
||||
"env": {
|
||||
"SPANNER_PROJECT": "your-project-id",
|
||||
"SPANNER_INSTANCE": "your-instance-id",
|
||||
"SPANNER_DATABASE": "your-database-name",
|
||||
"SPANNER_DIALECT": "googlesql"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "Spanner", and click "Install".
|
||||
3. **Configuration**: The following configuration is needed for the server:
|
||||
* Spanner Project ID: The GCP project ID.
|
||||
* Spanner Instance ID: The Spanner instance ID.
|
||||
* Spanner Database ID: The Spanner database ID.
|
||||
* Spanner Dialect: (Optional) The database dialect, which can be "googlesql" or "postgresql". Defaults to "googlesql" if unspecified.
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -44,9 +44,12 @@ The MCP Toolbox for Databases Server gives AI-powered development tools the abil
|
||||
|
||||
### Configuration
|
||||
|
||||
Add your [`tools.yaml` configuration
|
||||
file](https://googleapis.github.io/genai-toolbox/getting-started/configure/) to
|
||||
the directory you are running Antigravity
|
||||
1. **Access the Store**: Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
|
||||
2. **Browse and Install**: Search for "MCP Toolbox for Databases", and click "Install".
|
||||
3. **Configuration**: The following configuration is needed for the server:
|
||||
* Add your [`tools.yaml` configuration
|
||||
file](https://googleapis.github.io/genai-toolbox/getting-started/configure/)
|
||||
to the directory you are running Antigravity
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
Reference in New Issue
Block a user