Google Health Developer MCP server

The Google Health Developer Model Context Protocol (MCP) server gives AI-powered development tools and agents the ability to search and retrieve up-to-date, grounded documentation for the Google Health API—with no API key or authentication setup required.

An MCP server acts as a proxy between an external service that provides context or data and an AI application (the host). The Google Health Developer MCP server exposes executable tools that let Large Language Models (LLMs) find precise answers directly from indexed documentation. To learn more about MCP servers, see What is the MCP and how does it work?.

The server operates over the standard MCP Streamable HTTP transport at:

https://healthdevelopers.googleapis.com/mcp

Available tools

The server provides two core tools for technical documentation discovery and retrieval:

  • search_health_docs: Searches Google Health API documentation for relevant technical content chunks matching your query. Each chunk includes the page title, source URL, relevant text content, and canonical document resource name.
  • get_health_docs: Retrieves the complete Markdown content of one or more documentation pages using the resource names returned by search_health_docs.

For full input and output schemas, see the Google Health Developer MCP reference. All content is scoped strictly to public technical documentation hosted under https://developers.google.com/health/.

Prerequisites

To connect to the server, you need an MCP-compatible AI development environment or code assistant, such as:

Configure your client

Connect immediately using a one-click IDE installer, a single CLI command, an editor configuration file, or an automated chat prompt. No Google Cloud project or API key is required.

One-click IDE installation

If you use Google Antigravity, Cursor, or Visual Studio Code, select one of the following buttons to open your editor and install the HealthDevelopers MCP server:

Add to Antigravity Add to Cursor Add to VS Code

Command-line and editor setup

Select your AI client from the following tabs to add the server with a single command or configuration entry:

Gemini CLI

Add the server to Gemini CLI using the gemini mcp add command:

gemini mcp add --transport http --scope user \
  HealthDevelopers https://healthdevelopers.googleapis.com/mcp

Google Antigravity

Add the server using the Antigravity CLI:

agy mcp add HealthDevelopers https://healthdevelopers.googleapis.com/mcp

Alternatively, open ~/.gemini/config/mcp_config.json (or .agents/mcp_config.json in your workspace) and add HealthDevelopers under mcpServers. Antigravity CLI, Antigravity 2.0, and Antigravity IDE all share ~/.gemini/config/mcp_config.json:

{
  "mcpServers": {
    "HealthDevelopers": {
      "serverUrl": "https://healthdevelopers.googleapis.com/mcp"
    }
  }
}

Codex

Add the server to OpenAI Codex using the codex mcp add command:

codex mcp add HealthDevelopers \
  --url https://healthdevelopers.googleapis.com/mcp

Claude Code

Add the server to Claude Code using the claude mcp add command:

claude mcp add HealthDevelopers \
  --transport http https://healthdevelopers.googleapis.com/mcp

Cursor

If you prefer manual configuration instead of the one-click button, add the server to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project-level):

{
  "mcpServers": {
    "HealthDevelopers": {
      "url": "https://healthdevelopers.googleapis.com/mcp"
    }
  }
}

Grok

Add the server to Grok CLI using the grok mcp add command:

grok mcp add --transport http \
  HealthDevelopers https://healthdevelopers.googleapis.com/mcp

GitHub Copilot

If you prefer manual configuration instead of the one-click button, edit .vscode/mcp.json in your workspace (or add the configuration under an "mcp" root key in your VS Code user settings):

{
  "servers": {
    "HealthDevelopers": {
      "type": "http",
      "url": "https://healthdevelopers.googleapis.com/mcp"
    }
  }
}

Automated setup using a prompt

If your AI assistant supports managing MCP tool configurations directly from chat, instruct your assistant to configure the server by pasting the following prompt:

Please configure the Google Health Developer MCP server for me:
- Name: HealthDevelopers
- Server URL: https://healthdevelopers.googleapis.com/mcp
- Transport: http

Verify your connection

Confirm that HealthDevelopers is connected in Gemini CLI or Google Antigravity:

Gemini CLI

Run gemini mcp list from your terminal (or enter /mcp inside an interactive session):

gemini mcp list

Confirm that HealthDevelopers reports Connected:

Configured MCP servers:

✓ HealthDevelopers: https://healthdevelopers.googleapis.com/mcp (http) - Connected

Google Antigravity

  • Antigravity CLI: Enter /mcp in the prompt panel to open the MCP Manager and confirm HealthDevelopers shows an active status ring, or run agy mcp list from your terminal:

    NAME              TYPE  STATUS   COMMAND/URL
    HealthDevelopers  http  enabled  https://healthdevelopers.googleapis.com/mcp
    
  • Antigravity IDE: Click ... at the top of the agent side panel, select MCP Servers > Manage MCP Servers, and confirm HealthDevelopers is enabled.

  • Antigravity 2.0: Open Settings > Customizations > Installed MCP Servers and confirm HealthDevelopers is listed.

Example prompts

Once connected, your assistant automatically calls search_health_docs and get_health_docs when you ask about the Google Health API:

What OAuth scopes are needed to read steps and heart rate data in the Google
Health API, and how do I query daily step rollups?
Migrate my Fitbit Web API /1/user/-/activities/steps endpoint call to the
Google Health API v4.
How do I set up webhook subscriptions in the Google Health API to receive
updates when new sleep or workout data arrives?

Test with curl

You can also test the endpoint directly using curl. The MCP Streamable HTTP transport requires both Content-Type: application/json and Accept: application/json, text/event-stream headers.

List available tools

Run the following command to list the tools exposed by the server:

curl -s -X POST "https://healthdevelopers.googleapis.com/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": {}
  }'

Search documentation

Run the following command to test search_health_docs:

curl -s -X POST "https://healthdevelopers.googleapis.com/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "search_health_docs",
      "arguments": {
        "query": "steps scope",
        "pageSize": 2
      }
    }
  }'

Retrieve full document Markdown

Run the following command to test get_health_docs:

curl -s -X POST "https://healthdevelopers.googleapis.com/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "get_health_docs",
      "arguments": {
        "names": [
          "documents/developers.google.com/health/data-types/steps"
        ]
      }
    }
  }'

Feedback and support

To report issues, suggest improvements, or get help with the Google Health Developer MCP server, use the feedback and support channels on the Google Health API support page.