Appendix
Connect an AI agent to physician-reviewed medical opinions and prescription workflows via remote MCP when you are building regulated or health-adjacent products.
Overview
Appendix is an MCP server for the Build phase that connects AI agents to physician-reviewed medical opinions and prescriptions through Appendix’s hosted streamable-http endpoint.
What is this MCP server?
- Remote streamable-http MCP at mcp.appendix.com (no local npm package in registry metadata)
- Physician-reviewed medical opinions surfaced as MCP tools for coding agents
- Prescription-oriented capabilities for health and wellness agent workflows
- Version 1.1.0 server schema with GitHub source at appendixhealth/mcp-server
- Hosted service aligned with Appendix consumer health platform at appendix.com
- Server version 1.1.0 in registry metadata
- Single remote URL: https://mcp.appendix.com/mcp (streamable-http)
- GitHub repository: appendixhealth/mcp-server
Community signal: 1 GitHub stars.
What problem does it solve?
General-purpose agents sound confident on medical questions but cannot legally or safely substitute for reviewed clinical judgment in real products.
Who is it for?
Indie builders prototyping health agents, wellness apps, or clinician-assist tools who already plan physician oversight and need MCP-native clinical hooks.
Skip if: Non-medical SaaS, casual chatbots, or teams without regulatory clarity who only need generic health blogging or fitness tips.
What do I get? / Deliverables
After you register the remote MCP, agents can call Appendix-backed tools so answers and prescription paths are grounded in physician-reviewed workflows instead of unconstrained model text.
- Registered remote MCP pointing at mcp.appendix.com
- Agent-callable tools for physician-reviewed medical opinions
- Prescription-oriented tool paths wired into your agent workflow
Recommended MCP Servers
Journey fit
Health-capable agents are wired during product build when you add external clinical review APIs, not during early idea research alone. Integrations is the canonical shelf for streamable-http MCP remotes that extend agent tooling with a third-party medical opinion service.
How it compares
Clinical MCP integration with physician review, not a local skill or generic web-search plugin.
Common Questions / FAQ
Who is com.appendix/appendix for?
Solo and small teams building AI agents or apps where physician-reviewed opinions or prescriptions are an intentional product feature, not an accidental sidebar.
When should I use com.appendix/appendix?
Use it during Build when you are wiring agent tools to a hosted medical review API and need MCP clients to reach https://mcp.appendix.com/mcp over streamable HTTP.
How do I add com.appendix/appendix to my agent?
Add the remote MCP server URL from the registry to your client’s MCP config (Claude Code, Cursor, or other streamable-http hosts), then complete any Appendix account or auth steps required on appendix.com.