Ask your AI assistant about your own training

1. Add UMO — run this in your terminal:

   claude mcp add --transport http umo https://webapp.umo-health.com/mcp

   Add --scope user if you want UMO available in every project, not just this one.

2. Sign in — start Claude Code and run:

   /mcp

   Pick umo and choose to authenticate. Your browser opens; sign in to your UMO account. That's it — the connection renews itself from then on.

3. Try it. Ask "how's my training load looking?"

Works in the Claude desktop app and on claude.ai.

1. Open Settings → Connectors and choose Add custom connector.

2. Give it the name UMO and this URL:

   https://webapp.umo-health.com/mcp

3. Click Connect. Sign in to your UMO account on the page that opens.

4. Start a new chat and ask "what strength work should I do this week?"

   A chat only picks up new tools when it starts, so use a fresh chat after connecting.

For GitHub Copilot's agent mode in VS Code.

1. Open the Command Palette (Cmd/Ctrl + Shift + P) and run MCP: Add Server. Choose HTTP, paste the URL, and name it umo:

   https://webapp.umo-health.com/mcp

2. Prefer editing the file yourself? Put this in .mcp.json at the root of your workspace (or your user mcp.json):

   {
     "servers": {
       "umo": {
         "type": "http",
         "url": "https://webapp.umo-health.com/mcp"
       }
     }
   }

3. VS Code will prompt you to allow and then sign in. Sign in to your UMO account in the browser window it opens.

4. Open Copilot Chat in Agent mode and ask "how's my training load looking?"

1. Add UMO — open your workspace's .agents/mcp_config.json file. To make it available in every project instead, use ~/.gemini/config/mcp_config.json. Add this entry inside mcpServers (keep any servers already there):

   {
     "mcpServers": {
       "umo": {
         "serverUrl": "https://webapp.umo-health.com/mcp"
       }
     }
   }

   Antigravity CLI requires serverUrl for remote MCP servers; url and httpUrl will not connect.

2. Authenticate — start (or restart) Antigravity CLI with agy, then enter /mcp. Select umo and choose Authenticate.

   Your browser opens to UMO. Sign in with your normal UMO account, then return to Antigravity CLI when the browser says you can.

3. Try it. Ask "how's my training load looking?"

1. Add UMO — run this in your terminal:

   gemini mcp add --transport http umo https://webapp.umo-health.com/mcp

   Prefer editing the file yourself? Put this in your project's .gemini/settings.json (or your user ~/.gemini/settings.json) under mcpServers instead:

   {
     "mcpServers": {
       "umo": {
         "httpUrl": "https://webapp.umo-health.com/mcp"
       }
     }
   }

2. Sign in — start Gemini CLI and run:

   /mcp auth umo

   Your browser opens; sign in to your UMO account. Gemini CLI will also offer this automatically the first time it tries to use a UMO tool.

3. Try it. Ask "how's my training load looking?"

ChatGPT can talk to UMO, but custom connectors are the least settled part of its product — they need a paid plan, and where the setting lives moves around. If you can't find it, one of the other clients above will be quicker.

1. Open Settings → Connectors. If you see a Developer mode or Advanced toggle, turn it on — that's what reveals custom connectors.

2. Add a connector named UMO with this URL:

   https://webapp.umo-health.com/mcp

3. Choose OAuth when asked how to authenticate, then sign in to your UMO account.

   If it asks for a client ID and secret instead, leave them blank — UMO registers your client automatically.

4. If OAuth isn't offered at all, use an access token instead: create one here and paste it as an Authorization header with the value Bearer <your token>.

Cursor, Windsurf, Zed, Claude Desktop's config file, your own script — anything that speaks MCP over HTTP works the same way.

1. Point it at this URL, as a streamable HTTP (not stdio) server:

   https://webapp.umo-health.com/mcp

   Most clients use a config file shaped like this:

   {
     "mcpServers": {
       "umo": {
         "url": "https://webapp.umo-health.com/mcp"
       }
     }
   }

2. If the client supports OAuth, it will offer to sign you in — take that path.

3. If it doesn't, create an access token and send it as a header:

   {
     "mcpServers": {
       "umo": {
         "url": "https://webapp.umo-health.com/mcp",
         "headers": {
           "Authorization": "Bearer umo_pat_..."
         }
       }
     }
   }

   Treat that token like a password. It expires on its own; changing your UMO password invalidates it immediately.