Google AlloyDBvf.sr

listing.by · home.legend.verified

Manage AlloyDB for PostgreSQL clusters, instances, backups and users, and run SQL against your databases.

state.auth.long (state.auth.title)Streamable HTTP

listing.connect

listing.explain.oauth

https://alloydb.googleapis.com/mcp

listing.note.oauth

act.add_to a11y.new_tabact.add_to a11y.new_tabact.add_to a11y.new_tab

listing.share.h

listing.share.p

mcp.tc/i/alloydb

listing.about

Connects to Google Cloud AlloyDB for PostgreSQL. You can list and create clusters and instances, update instance settings, create backups, restore clusters, manage IAM-based database users, import and export data through Cloud Storage, and run SQL statements, including a read-only mode.

Runs as a hosted remote endpoint at alloydb.googleapis.com/mcp over streamable HTTP. Access uses Google OAuth 2.0 and IAM permissions on your project. The MCP endpoint must be enabled for the project before use. Long-running operations such as cluster creation are tracked with a status tool.

listing.can

  • List, inspect and create AlloyDB clusters
  • Create, inspect and update instances
  • Create backups and restore clusters
  • Create and list IAM-based database users
  • Run SQL statements or read-only queries
  • Import and export data via Cloud Storage
  • Check status of long-running operations

listing.tools 17

  • list_clusterslisting.hint.ro

    List all clusters in a project and location.

  • create_clusterlisting.hint.writes

    Create an AlloyDB cluster; returns a long-running operation.

  • get_clusterlisting.hint.ro

    Get details of a cluster.

  • list_instanceslisting.hint.ro

    List all instances in a cluster.

  • restore_clusterlisting.hint.writes

    Restore a cluster from a backup or a point in time.

  • create_backuplisting.hint.writes

    Create a backup of a cluster in READY state.

  • create_instancelisting.hint.writes

    Create a primary or read pool instance in a cluster.

  • get_instancelisting.hint.ro

    Get details of an instance.

  • update_instancelisting.hint.writes

    Update instance settings such as machine type, flags or node count.

  • create_userlisting.hint.writes

    Create an IAM-based database user in a cluster.

  • get_userlisting.hint.ro

    Get a user in a cluster.

  • list_userslisting.hint.ro

    List all users in a cluster.

listing.tools_more
  • execute_sqllisting.hint.delete

    Execute a SQL statement on an instance, including writes.

  • execute_sql_read_onlylisting.hint.ro

    Execute a SQL query on an instance in read-only mode.

  • export_datalisting.hint.writes

    Export cluster data to a Cloud Storage file as SQL or CSV.

  • import_datalisting.hint.writes

    Import SQL or CSV data from Cloud Storage into a cluster.

  • get_operationlisting.hint.ro

    Get the status of a long-running operation.

listing.prov.live_on listing.prov.hints

listing.prompts

  • List all AlloyDB clusters in my project in us-central1

  • Create a backup of the cluster named orders-prod

  • Run a read-only query to count rows in the customers table

  • Add a primary instance with 4 vCPUs to my new cluster

listing.setup.h

listing.setup.oauth

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http alloydb https://alloydb.googleapis.com/mcp
  1. Start Claude Code, type /mcp, pick alloydb and choose Authenticate. A browser window opens for the Google Cloud sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it Google AlloyDB and paste this URL:
https://alloydb.googleapis.com/mcp
  1. Click Add, then Connect, and sign in when Google Cloud asks.

Claude Desktop's JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:

Add to claude.ai a11y.new_tab

  1. Check that the URL reads https://alloydb.googleapis.com/mcp and click Add.
  2. Click Connect and sign in when Google Cloud asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://alloydb.googleapis.com/mcp as the server URL and choose OAuth. ChatGPT sends you to Google Cloud to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "alloydb": {
      "url": "https://alloydb.googleapis.com/mcp"
    }
  }
}

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Install in VS Code a11y.new_tab

Or from a terminal:

code --add-mcp '{"name":"alloydb","type":"http","url":"https://alloydb.googleapis.com/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "alloydb": {
      "type": "http",
      "url": "https://alloydb.googleapis.com/mcp"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "alloydb": {
      "serverUrl": "https://alloydb.googleapis.com/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add alloydb --url https://alloydb.googleapis.com/mcp
codex mcp login alloydb

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.alloydb]
url = "https://alloydb.googleapis.com/mcp"

Gemini CLI

gemini mcp add --transport http alloydb https://alloydb.googleapis.com/mcp

Then, inside Gemini CLI, run /mcp auth alloydb to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI's settings file.

{
  "mcpServers": {
    "alloydb": {
      "type": "http",
      "url": "https://alloydb.googleapis.com/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://alloydb.googleapis.com/mcp.

listing.faq

Can I paste mcp.tc/i/alloydb into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://alloydb.googleapis.com/mcp, so your client talks to Google AlloyDB directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Google AlloyDB need an API key or a sign-in?

Yes, you need a Google Cloud account. The first time your client connects, it opens Google Cloud's sign-in page. The token goes straight to the server's own URL, never through mcp.tc.

Is Google AlloyDB a remote or a local server?

Remote. Google Cloud hosts it at https://alloydb.googleapis.com/mcp, and it speaks Streamable HTTP. There's nothing to install.

What can Google AlloyDB do?

It has 17 tools, including list_clusters, create_cluster and get_cluster. You can list, inspect and create AlloyDB clusters, create, inspect and update instances and create backups and restore clusters.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc's robot read Google AlloyDB's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![Google AlloyDB on mcp.tc](https://mcp.tc/i/alloydb/badge.svg)](https://mcp.tc/i/alloydb)
HTML
<a href="https://mcp.tc/i/alloydb"><img src="https://mcp.tc/i/alloydb/badge.svg" alt="Google AlloyDB on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/alloydb.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/alloydb" title="Google AlloyDB on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json

https://mcp.tc/i/alloydb.json

listing.em.fields

listing.related

listing.more_in

  • Google Spannervf.sr

    Google Cloud

    state.auth.label (state.auth.title)

    Manage Spanner instances, databases and schemas, and run SQL queries and transactions against Google Cloud Spanner.

    mcp.tc/i/spanner

  • Memorystore for Valkeyvf.sr

    Google Cloud

    state.auth.label (state.auth.title)

    Manage Memorystore for Valkey instances, maintenance schedules and backups on Google Cloud.

    mcp.tc/i/memorystore-valkey

  • Google Cloud Bigtablevf.sr

    Google Cloud

    state.auth.label (state.auth.title)

    Create and manage Bigtable instances, tables and logical views, and find hot tablets in a cluster.

    mcp.tc/i/bigtable

  • Firestorevf.sr

    Google Cloud

    state.auth.label (state.auth.title)

    Read and write Firestore documents and manage databases, indexes, backups and backup schedules in Google Cloud.

    mcp.tc/i/firestore

  • Google Cloud SQLvf.sr

    Google Cloud

    state.auth.label (state.auth.title)

    Create and manage Cloud SQL instances, users and backups, and run SQL queries against them.

    mcp.tc/i/cloud-sql

  • Google BigQueryvf.sr

    Google Cloud

    state.auth.label (state.auth.title)

    List datasets, inspect tables and run SQL queries in Google BigQuery projects, with job status and cancellation.

    mcp.tc/i/bigquery

listing.disclaimer_checked