MCP server · Health Gorilla

health-gorilla-docs

Health Gorilla serves a live remote MCP endpoint from its own developer-portal host. An agent can reach it today at https://developer.healthgorilla.com/mcp — no install step, no local process. What it exposes, however, is the DOCUMENTATION, not the FHIR API: it is the MCP server ReadMe provisions for a hosted developer portal, so its tools search and read developer.healthgorilla.com pages rather than call api.healthgorilla.com. tools/list is auth-gated (JSON-RPC -32001 "Authorization required"), so the real tool schemas could not be read anonymously and none were invented. There is no MCP server in front of the FHIR API itself, and none is listed in the official MCP registry.

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Health Gorilla Type: Hosted endpoint Transport: http Host: developer.healthgorilla.com

Endpoint

https://developer.healthgorilla.com/mcp

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "health-gorilla": { "url": "https://developer.healthgorilla.com/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "health-gorilla": { "command": "npx", "args": ["-y", "mcp-remote", "https://developer.healthgorilla.com/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

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

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.