Skip to content
ToolCargo

The MCP directory / Open to explore

MCP server directory.
Find your next tool.

Search 3,974 indexed servers from the official MCP Registry and selected vendor documentation. Find remote endpoints and local packages, inspect the publisher’s setup details, then connect in your AI client.

Where will your next task take you?

Free discovery · no account · no API key

Let your agent do the finding.

Paste into your AI agent
Read https://toolcargo.com/agents.txt, then find the MCP servers I need and help me connect them. Ask me what I want to do first.

Or add https://toolcargo.com/mcp as a Streamable HTTP MCP server. Discovery is free and needs no account.

Compare task fit, publisher, permissions and a small acceptance test with the MCP server selection guide.

Connect directly to official MCP servers

Vendor setup guides for your existing accounts. These connections run with the vendor; ToolCargo does not host them or supply their credentials.

Browse the remote MCP server directory →

Not sure which connection to choose? Read local vs remote MCP servers. Building a discovery workflow? See the MCP server search API reference.

google-health-fitbit-mcp

Close details

Privacy-first Google Health API MCP server for health, sleep, activity and HR agents

Directory identity: io.github.BerkKilicoglu/google-health-fitbit-mcp · Version: 1.0.2

Publisher connection metadata
{
  "remotes": [],
  "packages": [
    {
      "registryType": "npm",
      "identifier": "google-health-fitbit-mcp",
      "version": "1.0.2",
      "transport": {
        "type": "stdio"
      },
      "environmentVariables": [
        {
          "description": "Google Cloud OAuth client ID for Google Health API. Optional when configured with google-health-fitbit-mcp-server setup.",
          "format": "string",
          "name": "GOOGLE_HEALTH_CLIENT_ID"
        },
        {
          "description": "Google Cloud OAuth client secret. Prefer google-health-fitbit-mcp-server setup so this secret is stored in ~/.google-health-mcp/config.json instead of MCP client config.",
          "format": "string",
          "isSecret": true,
          "name": "GOOGLE_HEALTH_CLIENT_SECRET"
        },
        {
          "description": "Redirect URI configured in the Google Cloud OAuth client. Optional when configured with google-health-fitbit-mcp-server setup.",
          "format": "string",
          "name": "GOOGLE_HEALTH_REDIRECT_URI"
        },
        {
          "description": "Optional local path for OAuth tokens. Defaults to ~/.google-health-mcp/tokens.json.",
          "format": "string",
          "name": "GOOGLE_HEALTH_TOKEN_PATH"
        },
        {
          "description": "Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Google Health API payloads, not continuous 24/7 raw sensor telemetry.",
          "format": "string",
          "name": "GOOGLE_HEALTH_PRIVACY_MODE"
        },
        {
          "description": "Optional SQLite cache toggle. Set to true or sqlite to enable.",
          "format": "string",
          "name": "GOOGLE_HEALTH_CACHE"
        },
        {
          "description": "Optional local SQLite cache path. Defaults to ~/.google-health-mcp/cache.sqlite.",
          "format": "string",
          "name": "GOOGLE_HEALTH_CACHE_PATH"
        },
        {
          "description": "Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless.",
          "format": "string",
          "name": "GOOGLE_HEALTH_NO_CACHE"
        }
      ]
    }
  ]
}

Remote URLs go into your client's MCP settings. Local packages need a compatible runtime. Check required headers, environment variables, permissions and provider costs before setup.

Publisher repository ↗

3,974 results

Index updated 2026-10-02

This directory combines dated registry listings and selected vendor-documentation entries. Documentation checks are not live account or client verification. Third-party servers run with their own providers, credentials and pricing. ToolCargo discovery supplies setup metadata; it does not run their tools. Explore ToolCargo's hosted connectors.