MCP

Connect Appendix to any MCP-compatible client. The MCP server exposes three tools — search the knowledge base, submit encounters, and list treatable conditions.

Two ways to connect: use the hosted server we run, or clone the open source repo and run your own. Most users want the hosted option.

Option 1 — Use our hosted server

Recommended

Point your MCP client at mcp.appendix.com/mcp. No install, no maintenance. Works with any client that speaks the Model Context Protocol.

Claude Code (one-liner)

claude mcp add --transport http appendix https://mcp.appendix.com/mcp

Other clients

{
  "mcpServers": {
    "appendix": {
      "url": "https://mcp.appendix.com/mcp"
    }
  }
}

The config file location varies by client — check your client’s documentation for where to place this snippet.

Option 2 — Run the server yourself

The MCP server is open source. Clone it, run it, and point your client at your own URL instead of ours.

Terminal

git clone https://github.com/appendixhealth/mcp-server.git
cd mcp-server
npm install && npm run build && npm start

View the source on GitHub. The README covers env vars (API_BASE_URL, PORT) and the Render deployment manifest.

Available tools

`search_knowledge_base`

Search the medical knowledge base for clinical literature and treatment guidelines.

Parameter	Type	Description
query	string	Clinical topic or question
limit	int	Max results (default: 5, max: 10)

`submit_encounter`

Submit a clinical letter for evaluation and physician review.

Parameter	Type	Description
query	string	Clinical letter in Markdown (500-10,000 chars)
session_token	string	Token from prior response (omit for new)

`list_conditions`

List all conditions and medications available for treatment. Returns conditions organized by category.

No authentication required

The Appendix MCP server does not require API keys or authentication. All public endpoints are freely accessible. Rate limits apply per session (5/hour, 10/day).

Use the prompt instead →Install as a skill →Direct API reference →