Connect an AI client
Connect an AI client
ICU Visor has two ways to operate:
- Local mode: install the
icuvisorbinary, runicuvisor setup, and connect a client to the local MCP server. Use this when the client can launch a local process or reach loopback HTTP. - Hosted mode: add
https://connect.icuvisor.app/mcpas a remote HTTPS MCP connector and sign in with Intervals.icu OAuth. Use this when the client needs a public endpoint.
Choose your connection
| Client | Connection | Setup |
|---|---|---|
| Claude Desktop | Local stdio, with a Desktop Extension or manual configuration | Claude Desktop |
| Claude.ai | Hosted HTTPS with Intervals.icu OAuth | Claude.ai |
| ChatGPT web | Hosted HTTPS through a custom MCP plugin, subject to account/workspace policy | ChatGPT |
| Claude Code, Codex CLI, and other coding clients | Local stdio; loopback HTTP where supported | Claude Code, Codex CLI, other clients |
| Local model clients | Local stdio or loopback HTTP where the client supports MCP | Other clients |
Switching assistants keeps the same Intervals.icu source data. Available tools depend on your toolset and write permissions; how Resources, Prompts, approvals, and metadata appear depends on the client. Start a fresh conversation after connecting or changing toolsets. Local software is free; your AI provider’s usage limits still apply.
Pick the path that matches your client. After the connection works, start with What can I ask icuvisor? for beginner-friendly prompts before reading the full tool reference.
Use the public HTTPS MCP URL for clients that cannot run a local server.
Add hosted icuvisor from Claude’s custom connector settings.
Install as a Desktop Extension or configure the MCP stdio server by hand.
Start icuvisor over MCP stdio from Claude Code.
Register icuvisor with Codex MCP config or the codex mcp command.
Add the hosted MCP plugin or configure a supported local MCP surface.
Core Streamable HTTP setup and reachability limits.
The standard MCP JSON shape for Cursor, Continue, Zed, Pi, and more.