Connect ChatGPT
ChatGPT has two different setup paths:
- Hosted connector: use this for ChatGPT web at
chatgpt.comwhen it asks for a remote HTTPS connector URL. - Local MCP surface: use this only when your ChatGPT client explicitly supports launching a local MCP server by stdio or connecting to loopback HTTP.
Hosted connector for ChatGPT web
Use hosted mode for ChatGPT’s custom connector/app flow. ChatGPT connects from OpenAI’s infrastructure, so it cannot reach http://127.0.0.1:8765/mcp on your laptop.
Open ChatGPT Plugins.
Select +, then Add custom MCP server.
Enter a name such as
icuvisorand a short description:Read my Intervals.icu training data and preview approved workout changes.Under Connection, choose a public endpoint and enter:
https://connect.icuvisor.app/mcpConfigure OAuth authentication, review ChatGPT’s connection notice, and select I understand and want to continue, then Create as a plugin.
Complete the hosted icuvisor authorization flow: choose preferences, continue to Intervals.icu, and approve the requested scopes. Choose
corefor normal use orfullfor advanced workflows. Keep read-only access unless you need writes.Review the discovered tools, install the resulting plugin, and start a fresh conversation. Type
@and select icuvisor.
Verify with:
Use icuvisor to tell me my current FTP and timezone. Do not estimate.Hosted mode uses Intervals.icu OAuth. Do not paste an Intervals API key into ChatGPT, the connector metadata, or chat.
Provider reference: OpenAI: Connect from ChatGPT.
If the connection option is missing or fails
- No Add custom MCP server option: confirm you are in the intended ChatGPT account and workspace. Custom MCP access depends on account and workspace policy; ask your workspace administrator about permissions. The absence of this option does not establish a problem with the icuvisor endpoint. Older screenshots may mention Developer mode or Apps & Connectors; follow the current official connection guide.
- Authorization fails: finish the Intervals.icu OAuth flow and return to ChatGPT. If you need broader write scopes later, use hosted settings to re-consent.
- Connection succeeds but tools look old: open the connection in ChatGPT Plugins, select Refresh, verify the tools, and start a new conversation.
- Tools are missing: check hosted toolset and write preferences before assuming a feature is unsupported. Advanced analysis may require
full.
When reporting a connection failure, include the stage that failed and the exact non-secret error text. Keep authorization codes, tokens, and API keys out of the report.
Local MCP surfaces
Use this section only when the ChatGPT surface you are using explicitly supports local MCP servers. ChatGPT web custom connectors should use the hosted flow above.
Before you start
- Install icuvisor and run setup.
- Confirm the binary starts with
icuvisor version. - Know your non-secret athlete ID and timezone.
Stdio configuration shape
Use the same stdio server definition as the Claude clients when ChatGPT asks for a local MCP server command:
macOS:
{
"mcpServers": {
"icuvisor": {
"command": "/Applications/icuvisor.app/Contents/MacOS/icuvisor",
"env": {
"INTERVALS_ICU_ATHLETE_ID": "i12345",
"ICUVISOR_TIMEZONE": "America/Sao_Paulo",
"ICUVISOR_TRANSPORT": "stdio",
"ICUVISOR_TOOLSET": "core"
}
}
}
}Windows:
{
"mcpServers": {
"icuvisor": {
"command": "C:\\Users\\<you>\\AppData\\Local\\Programs\\icuvisor\\icuvisor.exe",
"env": {
"INTERVALS_ICU_ATHLETE_ID": "i12345",
"ICUVISOR_TIMEZONE": "Europe/Brussels",
"ICUVISOR_TRANSPORT": "stdio",
"ICUVISOR_TOOLSET": "core"
}
}
}
}If your ChatGPT MCP surface expects a single server object rather than a full mcpServers map, use the icuvisor object from the example as that server definition. ICUVISOR_TOOLSET=core is the recommended default for ChatGPT; switch to compact for reduced-catalog compatibility only after starting a fresh conversation.
HTTP alternative
If your ChatGPT MCP surface expects an HTTP URL, start icuvisor with Streamable HTTP on loopback:
macOS:
ICUVISOR_TRANSPORT=http /Applications/icuvisor.app/Contents/MacOS/icuvisorWindows PowerShell:
$env:ICUVISOR_TRANSPORT = "http"
& "$env:LOCALAPPDATA\Programs\icuvisor\icuvisor.exe"Then point the client at:
http://127.0.0.1:8765/mcpDo not bind icuvisor to a LAN address unless you intentionally want other machines to reach the unauthenticated local MCP server. The HTTP transport guide covers the security tradeoff in more detail.
If a ChatGPT UI asks only for a remote HTTPS connector URL, use the hosted connector instead. Do not tunnel the local server with cloudflared, ngrok, or a similar public tunnel; that would expose an unauthenticated MCP endpoint using the intervals.icu credentials configured for the local process.
Verify
Start a fresh ChatGPT conversation after saving the MCP configuration, then ask a simple profile question such as What's my FTP? The expected tool call is get_athlete_profile. After that, try What can I ask icuvisor? for concrete starter prompts. If ChatGPT keeps using old tool names, old schemas, or stale timezone/zone assumptions, follow the stale conversation troubleshooting guide.