We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

Google AlloyDB, verified

MCP server by Google Cloud · Verified

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

OAuth sign-in (You sign in with the vendor the first time you connect)Streamable HTTP

Connect to Google AlloyDB

Google AlloyDB needs sign-in. Connect with its own URL:

https://alloydb.googleapis.com/mcp

Your client opens Google Cloud’s sign-in the first time you use it. The token stays between your client and Google Cloud.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/alloydb

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.

What you can do

  • 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

Tools 17

  • list_clustersRead-only

    List all clusters in a project and location.

  • create_clusterWrites

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

  • get_clusterRead-only

    Get details of a cluster.

  • list_instancesRead-only

    List all instances in a cluster.

  • restore_clusterWrites

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

  • create_backupWrites

    Create a backup of a cluster in READY state.

  • create_instanceWrites

    Create a primary or read pool instance in a cluster.

  • get_instanceRead-only

    Get details of an instance.

  • update_instanceWrites

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

  • create_userWrites

    Create an IAM-based database user in a cluster.

  • get_userRead-only

    Get a user in a cluster.

  • list_usersRead-only

    List all users in a cluster.

Show 5 more tools
  • execute_sqlCan delete

    Execute a SQL statement on an instance, including writes.

  • execute_sql_read_onlyRead-only

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

  • export_dataWrites

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

  • import_dataWrites

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

  • get_operationRead-only

    Get the status of a long-running operation.

Read from the live server on 17 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

Example 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

Set up

Every client connects to alloydb.googleapis.com, and Google Cloud asks you to sign in the first time. Pick yours; the page remembers your choice.

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 Customize → Connectors, click + Add, then 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:
  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, go to Plugins, select +, then Add custom MCP server.
  2. Enter a name for the server.
  3. Under Connection, paste https://alloydb.googleapis.com/mcp as the server URL, then for authentication choose OAuth. ChatGPT sends you to Google Cloud to sign in.
  4. Check I understand and want to continue, then select Create as a plugin.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

Cursor

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 authentication next to the server. Click the button beside it to sign in.

VS Code

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.

Embed

Show Google AlloyDB in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, 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>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

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

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

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>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

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

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Google AlloyDB card to your site.

Markdown
Add the mcp.tc card for Google AlloyDB, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

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

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="alloydb"><a href="https://mcp.tc/i/alloydb">Google AlloyDB on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Google AlloyDB on mcp.tc](https://mcp.tc/i/alloydb/badge.svg)](https://mcp.tc/i/alloydb)
```

Reference: https://mcp.tc/embed

Change history

We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:35 UTC.

Follow Google AlloyDB and we’ll email you when something changes.

  1. , Automatic check

    2 tools changed.

    Details, 31 Oct 2026, 08:47 UTC

    Changed 2

    • get_instanceoutput schema
    • list_instancesoutput schema
  2. , Automatic check

    6 tools changed.

    Details, 22 Oct 2026, 22:37 UTC

    Changed 6

    • create_clusterinput schema
      • New parameters: expressConfig
    • create_instanceinput schema
      • New parameters: publicDnsEnabled
    • get_clusteroutput schema
    • get_instanceoutput schema
    • list_clustersoutput schema
    • list_instancesoutput schema
  3. , Automatic check

    2 tools changed.

    Details, 12 Oct 2026, 04:36 UTC

    Changed 2

    • get_instanceoutput schema
    • list_instancesoutput schema
  4. , Automatic check

    Tracking started: 17 tools.

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, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to Google AlloyDB?

Yes. Google AlloyDB’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.

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.

mcp.tc isn’t affiliated with Google Cloud. This page was built from Google AlloyDB’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.