build_integration — Anpheros FHIR MCP Prompt
build_integration
is one of 3 prompts on the
Anpheros FHIR
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke build_integration from your client
- Claude Code Anpheros FHIR Prompt/build_integration run in your project directory
- Claude Desktop Anpheros FHIR Prompt/build_integration ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Anpheros FHIR Prompt/build_integration ~/.cursor/mcp.json
- VS Code Anpheros FHIR Prompt/build_integration .vscode/mcp.json
- Zed Anpheros FHIR Prompt/build_integration ~/.config/zed/settings.json
- Windsurf Anpheros FHIR Prompt/build_integration ~/.codeium/windsurf/mcp_config.json
- Cline Anpheros FHIR Prompt/build_integration ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Anpheros FHIR Prompt/build_integration ~/.gemini/settings.json
- Grok Anpheros FHIR Prompt/build_integration .mcp.json (in your project root)
- ChatGPT Anpheros FHIR Prompt/build_integration Settings → Connectors → Advanced → Developer mode
- Claude.ai Anpheros FHIR Prompt/build_integration Settings → Connectors → Add custom connector
- LangChain Anpheros FHIR Prompt/build_integration pip install langchain-mcp-adapters
Other prompts on this server
Anpheros FHIR also offers 1 resource — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 11 October 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.