Google Cloud Logging, verified
MCP server by Google Cloud · Verified
Search and read Cloud Logging entries, log names, buckets and views in your Google Cloud projects.
Connect to Google Cloud Logging
Google Cloud Logging needs sign-in. Connect with its own URL:
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/google-cloud-loggingAbout
Connects an assistant to Google Cloud Logging so it can search log entries with filters, list the log names in a project, and inspect log buckets and log views. All six tools are read-only, which suits debugging, finding error messages and auditing events.
It runs as a hosted remote endpoint over streamable HTTP at logging.googleapis.com/mcp. Access uses Google OAuth 2.0 and IAM permissions on the project, and the MCP endpoint must be enabled for the project first. Log entry searches work against one resource project at a time.
What you can do
- Search log entries using filters on severity, resource type and text
- List the log names available in a project
- Get and list log buckets
- Get and list log views on a bucket
- Page through results with page size and tokens
- Read-only access to logging data
Tools 6
list_log_entriesRead-onlySearch and retrieve log entries using a filter, ordering and paging for one project.
list_log_namesRead-onlyList the log names in a project that have log entries.
get_bucketRead-onlyGet a specific log bucket by name.
list_bucketsRead-onlyList the log buckets in a Google Cloud project.
get_viewRead-onlyGet a specific log view on a log bucket.
list_viewsRead-onlyList the log views in a given log bucket.
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
Find ERROR log entries from the last hour in project my-prod-project
List the log names available in my-prod-project
Show all log buckets in my-prod-project
List the views on the _Default log bucket
Set up
Every client connects to logging.googleapis.com, and Google Cloud asks you to sign in the first time. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http google-cloud-logging https://logging.googleapis.com/mcp- Start Claude Code, type
/mcp, pick google-cloud-logging 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
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it Google Cloud Logging and paste this URL:
https://logging.googleapis.com/mcp- 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
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://logging.googleapis.com/mcpand click Add. - 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
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://logging.googleapis.com/mcpas the server URL, then for authentication choose OAuth. ChatGPT sends you to Google Cloud to sign in. - 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
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"google-cloud-logging": {
"url": "https://logging.googleapis.com/mcp"
}
}
}Cursor shows Needs authentication next to the server. Click the button beside it to sign in.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"google-cloud-logging","type":"http","url":"https://logging.googleapis.com/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"google-cloud-logging": {
"type": "http",
"url": "https://logging.googleapis.com/mcp"
}
}
}VS Code asks you to sign in the first time the server starts.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"google-cloud-logging": {
"serverUrl": "https://logging.googleapis.com/mcp"
}
}
}- 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 google-cloud-logging --url https://logging.googleapis.com/mcp
codex mcp login google-cloud-loggingOr edit ~/.codex/config.toml directly:
[mcp_servers.google-cloud-logging]
url = "https://logging.googleapis.com/mcp"Gemini CLI
gemini mcp add --transport http google-cloud-logging https://logging.googleapis.com/mcpThen, inside Gemini CLI, run /mcp auth google-cloud-logging 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": {
"google-cloud-logging": {
"type": "http",
"url": "https://logging.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://logging.googleapis.com/mcp.
Embed
Show Google Cloud Logging 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
[](https://mcp.tc/i/google-cloud-logging)<a href="https://mcp.tc/i/google-cloud-logging"><img src="https://mcp.tc/i/google-cloud-logging/badge.svg" alt="Google Cloud Logging 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
<script src="https://mcp.tc/w/google-cloud-logging.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
<iframe src="https://mcp.tc/embed/google-cloud-logging" title="Google Cloud Logging 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/google-cloud-logging.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Google Cloud Logging card to your site.
Add the mcp.tc card for Google Cloud Logging, 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/google-cloud-logging.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="google-cloud-logging"><a href="https://mcp.tc/i/google-cloud-logging">Google Cloud Logging 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
[](https://mcp.tc/i/google-cloud-logging)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:35 UTC.
FAQ
Can I paste mcp.tc/i/google-cloud-logging into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://logging.googleapis.com/mcp, so your client talks to Google Cloud Logging 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 Cloud Logging 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 Cloud Logging a remote or a local server?
Remote. Google Cloud hosts it at https://logging.googleapis.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can Google Cloud Logging do?
It has 6 tools, including list_log_entries, list_log_names and get_bucket. You can search log entries using filters on severity, resource type and text, list the log names available in a project and get and list log buckets.
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 Cloud Logging?
Yes. Google Cloud Logging’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 Cloud Logging’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 Cloud Logging’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.