A Model Context Protocol (MCP) server acts as a proxy between an external service that provides context, data, or capabilities to a Large Language Model (LLM) or AI application. MCP servers connect AI applications to external systems such as databases and web services, translating their responses into a format that the AI application can understand.
Server Setup
You must enable MCP servers and set up authentication before use. For more information about using Google and Google Cloud remote MCP servers, see Google Cloud MCP servers overview.
Server Endpoints
An MCP service endpoint is the network address and communication interface (usually a URL) of the MCP server that an AI application (the Host for the MCP client) uses to establish a secure, standardized connection. It is the point of contact for the LLM to request context, call a tool, or access a resource. Google MCP endpoints can be global or regional.
The developerknowledge.googleapis.com MCP server has the following MCP endpoint:
- https://developerknowledge.googleapis.com
MCP Tools
An MCP tool is a function or executable capability that an MCP server exposes to a LLM or AI application to perform an action in the real world.
The developerknowledge.googleapis.com MCP server has the following tools:
| MCP Tools | |
|---|---|
| search_documents |
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: * Android: developer.android.com * Apigee: docs.apigee.com * Chrome: developer.chrome.com * Firebase: firebase.google.com * Fuchsia: fuchsia.dev * Google AI: ai.google.dev * Google Cloud: docs.cloud.google.com * Google Developers, Ads, Search, Google Maps, Youtube: developers.google.com * Google Home: developers.home.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 detailed enough to answer the user's question, use get_document or batch_get_documents with the parent from this tool's output to retrieve the full document content.
|
| get_document |
Use this tool to retrieve the full content of a single document. The document name should be obtained from the parent field of results from a call to the search_documents tool. If you need to retrieve multiple documents, use batch_get_documents instead.
|
| batch_get_documents |
Use this tool to retrieve the full content of 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. Use this tool instead of calling get_document multiple times to fetch multiple documents.
|
Get MCP tool specifications
To get the MCP tool specifications for all tools in an MCP server, use the tools/list method. The following example demonstrates how to use curl to list all tools and their specifications currently available within the MCP server.
| Curl Request |
|---|
curl --location 'https://developerknowledge.googleapis.com' \ --header 'content-type: application/json' \ --header 'accept: application/json, text/event-stream' \ --data '{ "method": "tools/list", "jsonrpc": "2.0", "id": 1 }' |