MCP Server

Eirly publishes a Model Context Protocol (MCP) server for developers. Adding it to your AI coding assistant gives the assistant direct access to this API's real contract, so it can help you build an integration without guessing at endpoint names, field types, or error codes.

It is public and read-only. There is no sign-up and no authentication. The server only exposes what is already published here and in the OpenAPI document.

This is not the patient-facing MCP

This developer server answers questions about the API. It holds no patient data, no customer records, and no account of yours, so there is no way to authenticate to it, so there is nothing for it to look up. It cannot place an order or read a result.

Connect

Add the following URL to your MCP client:

https://mcp.eirly.health/dev/v1

The transport is streamable HTTP, and no authentication headers are required.

Claude Code

claude mcp add --transport http eirly-dev https://mcp.eirly.health/dev/v1

Cursor, Windsurf, and other clients

Add the server to your client's MCP configuration file:

{
  "mcpServers": {
    "eirly-dev": {
      "type": "http",
      "url": "https://mcp.eirly.health/dev/v1"
    }
  }
}

What it can tell you

Tool	What it answers
list_endpoints	Every endpoint in the API, with its method, tags and whether it needs auth.
get_endpoint	The full contract for one endpoint: parameters, request body, every response, and the worked examples.
get_schema	One object type (Referral, Result, Biomarker, …) with all nested types inlined, for modelling the API in your own code.
search_docs	Ranked passages from this documentation site.
get_doc	A full documentation page as markdown.
list_webhook_events	Every webhook event, and the envelope your handler receives.
list_error_codes	Every error code, its HTTP status, and what it means.
list_tests	The real test ids, so a generated order payload uses ids that exist.

Things worth knowing

The endpoint reference is generated, not written. list_endpoints, get_endpoint and get_schema read the API's own OpenAPI document, which is built from the deployed source. What the MCP tells you about an endpoint is what that endpoint actually does, and it cannot fall behind a release.

Pricing is not available here. list_tests returns ids, names and categories but no prices, because prices depend on your organisation's agreement. Use the authenticated GET /v1/tests or POST /v1/calculate with your own access token for a real quote.

There is one server per environment, and this page documents the production one. The URL above is the production server, matching this documentation site. Both environments run the same API contract, so what it tells you about an endpoint holds in either; only the host you call and the credentials you use differ. See Getting Started.

The URL is versioned. /dev/v1 is the current tool set. If we ever need to change it in a way that would break existing configurations, we will publish /dev/v2 and leave /dev/v1 serving, so nothing you have pinned stops working.

Getting a useful answer

The assistant will do better if you tell it to consult the server. Some prompts that work well:

• "Using the Eirly MCP, write a TypeScript function that creates a referral for a cholesterol test and handles every documented error code."
• "What is the difference between reference and referenceNumber on a referral?"
• "Which webhook events fire between ordering a test and getting a result?"
• "Show me the exact request body for ordering a Medicare test."

Once you are ready to make real calls, you still need credentials, so follow Getting Started to create an organisation and enable the API.