metriport-docs
Metriport serves a remote MCP endpoint from its documentation host. A tools/list POST returns HTTP 200 anonymously with three real tools and their inputSchemas — captured verbatim in metriport-mcp-tools.json. This is a Mintlify-generated DOCUMENTATION server: it searches and reads the Metriport docs corpus and files docs feedback. It exposes no Medical API operation, so an agent can learn how to call Metriport through it but cannot create a patient, start a network query or read consolidated FHIR data with it. There is no MCP server over the Medical API itself, hosted or stdio.
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.
Endpoint
Hosted endpoint · transport streamable-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, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tools
search_metriport— Search across the Metriport knowledge base for documentation, code examples, API references and guides. Returns contextual content with titles and direct links.query_docs_filesystem_metriport— Run a read-only shell-like query (rg, grep, find, tree, ls, cat, head, tail, jq and friends) against a virtualised in-memory filesystem containing only the Metriport documentation pages. This is how a page is read; there is no separate get-page tool. Stateless per call.submit_feedback— Report a problem with a documentation page to the docs team.
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.