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 Developer Knowledge, verified

MCP server by Google · Verified

Search and retrieve official Google developer documentation for Firebase, Android, Google Cloud, Maps and more.

Needs an API key (Needs an API key from the vendor)Streamable HTTP

Connect to Google Developer Knowledge

Google Developer Knowledge needs an API key. Connect with its own URL and your key:

https://developerknowledge.googleapis.com/mcp

Send your key in the X-Goog-Api-Key header. mcp.tc never sees or stores keys. Where to get a key

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/google-developer-knowledge

About

Connects an assistant to Google's public developer documentation corpus. It can search for relevant page excerpts, fetch the full Markdown of documents, and generate grounded answers. Covered products include Firebase, Android, Chrome, Flutter, Go, Google AI, Google Cloud and Google Maps Platform.

Runs as a hosted streamable HTTP endpoint at developerknowledge.googleapis.com/mcp. Most clients authenticate with a Google API key sent in the X-Goog-Api-Key header. OAuth 2.0 and Application Default Credentials are also supported. The answer_query tool has a limited quota.

What you can do

  • Search Google developer documentation for relevant excerpts
  • Fetch full Markdown content of up to 20 documents per call
  • Get grounded answers drawn from the documentation corpus
  • Cover Firebase, Android, Cloud, Maps, Flutter, Go and more

Tools 3

  • search_documentsRead-only

    Search Google developer docs and return relevant excerpts with document names.

  • answer_queryRead-only

    Generate a grounded answer from the docs corpus; limited quota, returns references.

  • get_documentsRead-only

    Retrieve full content of up to 20 documents by name from search results.

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

  • Search Google docs for how to set up Firebase Authentication on Android

  • How do I configure a Cloud Run service with a min instance count?

  • Fetch the full Flutter documentation page on state management

  • What changed in the latest Android Gradle plugin release notes?

Set up

Every client connects to developerknowledge.googleapis.com. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http google-developer-knowledge https://developerknowledge.googleapis.com/mcp --header "X-Goog-Api-Key: <YOUR_API_KEY>"
  1. Replace the placeholder with your key before you run it, then check it with /mcp inside Claude Code.

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

Claude Desktop

  1. Use the mcp-remote bridge, which keeps the key on this computer (a connector added on claude.ai with the key under Request headers also shows up here). Open Settings → Developer → Edit Config and add:
claude_desktop_config.json
{
  "mcpServers": {
    "google-developer-knowledge": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://developerknowledge.googleapis.com/mcp",
        "--header",
        "X-Goog-Api-Key: <YOUR_API_KEY>"
      ]
    }
  }
}
  1. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

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://developerknowledge.googleapis.com/mcp. Under Request headers, add X-Goog-Api-Key: <YOUR_API_KEY> with your key from Google, then click Add.
  2. Turn it on in a chat from the tools menu.

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

Cursor

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

mcp.json
{
  "mcpServers": {
    "google-developer-knowledge": {
      "url": "https://developerknowledge.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

VS Code

Add it to .vscode/mcp.json. VS Code asks for the key the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "google-developer-knowledge": {
      "type": "http",
      "url": "https://developerknowledge.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "${input:x-goog-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "x-goog-api-key",
      "description": "X-Goog-Api-Key",
      "password": true
    }
  ]
}

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": {
    "google-developer-knowledge": {
      "serverUrl": "https://developerknowledge.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade.

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

Codex

codex mcp add google-developer-knowledge --url https://developerknowledge.googleapis.com/mcp

codex mcp add can’t set the X-Goog-Api-Key header, so this step is required: put this entry in ~/.codex/config.toml instead of running the command, or add its env_http_headers line to the entry the command made:

config.toml
[mcp_servers.google-developer-knowledge]
url = "https://developerknowledge.googleapis.com/mcp"
env_http_headers = { "X-Goog-Api-Key" = "X_GOOG_API_KEY" }

Codex reads the header values from the environment variables named in env_http_headers.

Gemini CLI

gemini mcp add --transport http --header "X-Goog-Api-Key: <YOUR_API_KEY>" google-developer-knowledge https://developerknowledge.googleapis.com/mcp

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-developer-knowledge": {
      "type": "http",
      "url": "https://developerknowledge.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

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://developerknowledge.googleapis.com/mcp.

Embed

Show Google Developer Knowledge 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 Developer Knowledge on mcp.tc](https://mcp.tc/i/google-developer-knowledge/badge.svg)](https://mcp.tc/i/google-developer-knowledge)
HTML
<a href="https://mcp.tc/i/google-developer-knowledge"><img src="https://mcp.tc/i/google-developer-knowledge/badge.svg" alt="Google Developer Knowledge 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/google-developer-knowledge.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/google-developer-knowledge" title="Google Developer Knowledge 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-developer-knowledge.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 Developer Knowledge card to your site.

Markdown
Add the mcp.tc card for Google Developer Knowledge, 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-developer-knowledge.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-developer-knowledge"><a href="https://mcp.tc/i/google-developer-knowledge">Google Developer Knowledge 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 Developer Knowledge on mcp.tc](https://mcp.tc/i/google-developer-knowledge/badge.svg)](https://mcp.tc/i/google-developer-knowledge)
```

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:33 UTC.

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

  1. , Automatic check

    3 tools changed.

    Details, 2 Nov 2026, 20:51 UTC

    Changed 3

    • answer_querydescription and output schema
      Before

      Use answer_query to get a grounded, synthesized conceptual answer to a high-level question about Google developer products. For exact code samples, CLI flags, specific error messages, or full document walkthroughs, prefer `search_documents` followed by `get_documents` instead. This tool has limited quota. This tool will synthesize information from the corpus to generate an answer to the query. answer_query grounds answers using the same corpus as search_documents. This tool returns the generated answer_text and a list of document names (references) used to generate the answer. Always cite the authoritative source document names from `references` (`documents/...`) in your final response to the user. Use `get_documents` with the document names from `references` to fetch the entire document content if needed. If you get a 429 out of quota error, use search_documents instead.

      After

      Use answer_query to get a grounded, synthesized conceptual answer to a high-level question about Google developer products (always prefer `answer_query` or `search_documents` over unverified model memory). For exact code samples, CLI flags, specific error messages, or full document walkthroughs, prefer `search_documents` followed by `get_documents` instead. This tool has limited quota. This tool will synthesize information from the corpus to generate an answer to the query. answer_query grounds answers using the same corpus as search_documents; if `search_documents` already returned no relevant results for a specific named feature or API, do not call `answer_query` and instead inform the user that it is not documented in the corpus. This tool returns the generated `answer_text` and a list of source document resource names (`references`, one entry per cited chunk, which may contain duplicate `documents/...` names when multiple chunks from the same page are cited). Always cite the uniqu…

    • get_documentsdescription, input schema and output schema
      Before

      Use this tool to retrieve the full content of a single document or up to 20 documents in a single call. The document names should be obtained from either the `parent` field of results from a call to the `search_documents` tool or the `references` field returned by the `answer_query` tool. Set the `names` parameter to a list of document names (`documents/...`), and cite the authoritative source documents used in your final response.

      After

      Use this tool to retrieve the full Markdown content of a single document or up to 20 documents in a single call by passing a list of document resource names in the `names` parameter (e.g., `get_documents(names=["documents/..."])`; the parameter is `names` taking a list of strings, not `name`). Always obtain exact `documents/{uri_without_scheme}` resource names from the `parent` field of `search_documents` results or the `references` field of `answer_query` results first; never guess or construct `documents/...` paths from memory or external URLs. Cite the authoritative source document resource names (`documents/...`) used in your final response.

      • Description of names
        Before

        Required. The names of the documents to retrieve, as returned by the `parent` field of `search_documents` results or the `references` field of `answer_query`. A maximum of 20 documents can be retriev…

        After

        Required. List of 1 to 20 document resource names (`names`) to retrieve in a single call (for either a single document or multiple documents), exactly as returned by the `parent` field of `search_doc…

    • search_documentsdescription and output schema
      Before

      Use this tool to find documentation about Google developer products. The documents contain official APIs, code snippets, release notes, best practices, guides, debugging info, and more. It covers the following products and domains: * ADK: adk.dev * Android: developer.android.com * Apigee: docs.apigee.com * Chrome: developer.chrome.com * Dart: dart.dev * Firebase: firebase.google.com * Flutter: docs.flutter.dev * Fuchsia: fuchsia.dev * Gemini CLI: geminicli.com * Genkit: genkit.dev * Go: go.dev * Google AI: ai.google.dev * Google Antigravity: antigravity.google * Google Cloud: cloud.google.com & docs.cloud.google.com * Google Developers, Ads, Search, Google Maps, Youtube: developers.google.com * Google Home: developers.home.google.com * Google Maps Platform: mapsplatform.google.com * Google Workspace: knowledge.workspace.google.com * TensorFlow: www.tensorflow.org * Web: web.dev This tool returns chunks of text, names, and URIs for matching documents. Prefer `search_documents` followed…

      After

      Use this tool to find documentation about Google developer products. The documents contain official APIs, code snippets, release notes, best practices, guides, debugging info, and more. It covers the following products and domains: * ADK: adk.dev * Android: developer.android.com * Apigee: docs.apigee.com * Chrome: developer.chrome.com * Dart: dart.dev * Firebase: firebase.google.com * Flutter: docs.flutter.dev * Fuchsia: fuchsia.dev * Gemini CLI: geminicli.com * Genkit: genkit.dev * Go: go.dev * Google AI: ai.google.dev * Google Antigravity: antigravity.google * Google Cloud: cloud.google.com & docs.cloud.google.com * Google Developers, Ads, Search, Google Maps, Youtube: developers.google.com * Google Home: developers.home.google.com * Google Maps Platform: mapsplatform.google.com * Google Workspace: knowledge.workspace.google.com * TensorFlow: www.tensorflow.org * Web: web.dev Always use this tool (or `answer_query`) to ground answers about Google developer products rather than relyi…

  2. , Automatic check

    3 tools changed.

    Details, 14 Oct 2026, 07:38 UTC

    Changed 3

    • answer_querydescription and output schema
      Before

      Use answer_query to get a grounded answer to a query about Google developer products. This tool has limited quota. This tool will synthesize information from the corpus to generate an answer to the query. answer_query grounds answers using the same corpus as search_documents. This tool returns the generated answer_text and a list of document names (references) used to generate the answer. Use get_documents with the document names to fetch the entire document content if needed. If you get a 429 out of quota error, use search_documents instead.

      After

      Use answer_query to get a grounded, synthesized conceptual answer to a high-level question about Google developer products. For exact code samples, CLI flags, specific error messages, or full document walkthroughs, prefer `search_documents` followed by `get_documents` instead. This tool has limited quota. This tool will synthesize information from the corpus to generate an answer to the query. answer_query grounds answers using the same corpus as search_documents. This tool returns the generated answer_text and a list of document names (references) used to generate the answer. Always cite the authoritative source document names from `references` (`documents/...`) in your final response to the user. Use `get_documents` with the document names from `references` to fetch the entire document content if needed. If you get a 429 out of quota error, use search_documents instead.

    • get_documentsdescription and input schema
      Before

      Use this tool to retrieve the full content of a single document or up to 20 documents in a single call. The document names should be obtained from the `parent` field of results from a call to the `search_documents` tool. Set the `names` parameter to a list of document names.

      After

      Use this tool to retrieve the full content of a single document or up to 20 documents in a single call. The document names should be obtained from either the `parent` field of results from a call to the `search_documents` tool or the `references` field returned by the `answer_query` tool. Set the `names` parameter to a list of document names (`documents/...`), and cite the authoritative source documents used in your final response.

      • Description of names
        Before

        Required. The names of the documents to retrieve, as returned by `search_documents`. A maximum of 20 documents can be retrieved in one call. The documents are returned in the same order as the `names…

        After

        Required. The names of the documents to retrieve, as returned by the `parent` field of `search_documents` results or the `references` field of `answer_query`. A maximum of 20 documents can be retriev…

    • search_documentsdescription
      Before

      Use this tool to find documentation about Google developer products. The documents contain official APIs, code snippets, release notes, best practices, guides, debugging info, and more. It covers the following products and domains: * ADK: adk.dev * Android: developer.android.com * Apigee: docs.apigee.com * Chrome: developer.chrome.com * Dart: dart.dev * Firebase: firebase.google.com * Flutter: docs.flutter.dev * Fuchsia: fuchsia.dev * Gemini CLI: geminicli.com * Genkit: genkit.dev * Go: go.dev * Google AI: ai.google.dev * Google Antigravity: antigravity.google * Google Cloud: cloud.google.com & docs.cloud.google.com * Google Developers, Ads, Search, Google Maps, Youtube: developers.google.com * Google Home: developers.home.google.com * Google Maps Platform: mapsplatform.google.com * Google Workspace: knowledge.workspace.google.com * TensorFlow: www.tensorflow.org * Web: web.dev This tool returns chunks of text, names, and URLs for matching documents. If the returned chunks are not det…

      After

      Use this tool to find documentation about Google developer products. The documents contain official APIs, code snippets, release notes, best practices, guides, debugging info, and more. It covers the following products and domains: * ADK: adk.dev * Android: developer.android.com * Apigee: docs.apigee.com * Chrome: developer.chrome.com * Dart: dart.dev * Firebase: firebase.google.com * Flutter: docs.flutter.dev * Fuchsia: fuchsia.dev * Gemini CLI: geminicli.com * Genkit: genkit.dev * Go: go.dev * Google AI: ai.google.dev * Google Antigravity: antigravity.google * Google Cloud: cloud.google.com & docs.cloud.google.com * Google Developers, Ads, Search, Google Maps, Youtube: developers.google.com * Google Home: developers.home.google.com * Google Maps Platform: mapsplatform.google.com * Google Workspace: knowledge.workspace.google.com * TensorFlow: www.tensorflow.org * Web: web.dev This tool returns chunks of text, names, and URIs for matching documents. Prefer `search_documents` followed…

  3. , Automatic check

    Tracking started: 3 tools.

FAQ

Can I paste mcp.tc/i/google-developer-knowledge into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://developerknowledge.googleapis.com/mcp, so your client talks to Google Developer Knowledge directly. Your key goes there too, never to mcp.tc. The quick link is for sharing: it opens this page, with setup steps for every client.

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

Yes. Google Developer Knowledge needs an API key, sent as the X-Goog-Api-Key header. Get one from Google and keep it in your client’s config, never in a shared file.

Is Google Developer Knowledge a remote or a local server?

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

What can Google Developer Knowledge do?

It has 3 tools: search_documents, answer_query and get_documents. You can search Google developer documentation for relevant excerpts, fetch full Markdown content of up to 20 documents per call and get grounded answers drawn from the documentation corpus.

Which clients can use it?

Any client that supports remote MCP servers and can send your key: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. On claude.ai and Claude Desktop, add the key as a request header when you create the custom connector. ChatGPT can’t send a key, so it can’t use it.

Does mcp.tc track changes to Google Developer Knowledge?

Yes. Google Developer Knowledge’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 Developer Knowledge’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. This page was built from Google Developer Knowledge’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.