build_health_timeline — Juno Open Health Tools MCP Tool
build_health_timeline
(build health timeline) is one of 5 tools on the
Juno Open Health Tools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call build_health_timeline from your client
- Claude Code Juno Open Health Tools build_health_timeline run in your project directory
- Claude Desktop Juno Open Health Tools build_health_timeline ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Juno Open Health Tools build_health_timeline ~/.cursor/mcp.json
- VS Code Juno Open Health Tools build_health_timeline .vscode/mcp.json
- Zed Juno Open Health Tools build_health_timeline ~/.config/zed/settings.json
- Windsurf Juno Open Health Tools build_health_timeline ~/.codeium/windsurf/mcp_config.json
- Cline Juno Open Health Tools build_health_timeline ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Juno Open Health Tools build_health_timeline ~/.gemini/settings.json
- Grok Juno Open Health Tools build_health_timeline .mcp.json (in your project root)
- ChatGPT Juno Open Health Tools build_health_timeline Settings → Connectors → Advanced → Developer mode
- Claude.ai Juno Open Health Tools build_health_timeline Settings → Connectors → Add custom connector
- LangChain Juno Open Health Tools build_health_timeline pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http juno-open-health-tools https://juno-health-tools.vercel.app/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.