Koskamo

iAM360 MCP

An official MCP server for iAM360 that allows AI assistants to read and write fitness data, including wearable metrics from WHOOP or Oura, nutrition logs, workout plans, challenges, life events, and journal entries. It supports OAuth authentication and provides tools for tracking health progress and managing daily habits.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

iAM360 MCP logo, by iAM360Vendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by iAM360
You need:Authorization: Bearer <access token> on every request, from iAM360's OAuth sign-in.
MCP endpoint (Streamable HTTP)
https://app.iam360.ai/api/mcp
Vendor documentation

What you can do with it

  • Read recovery, sleep, and training load from wearable devices
  • Log meals with nutritional details or let the system estimate them
  • Log workouts and add exercises to existing sessions
  • Write to or read private journal entries

Source and maintenance

Vendor evidenceRegistry 1.0.0

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
138 ms
95th percentile latency
138 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 138 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http iam360-mcp https://app.iam360.ai/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add iam360-mcp --url https://app.iam360.ai/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable iam360-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "iam360-mcp": {
      "url": "https://app.iam360.ai/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "iam360-mcp": {
      "type": "streamableHttp",
      "url": "https://app.iam360.ai/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start iam360-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "iam360-mcp": {
      "type": "http",
      "url": "https://app.iam360.ai/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http iam360-mcp https://app.iam360.ai/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "iam360-mcp": {
      "url": "https://app.iam360.ai/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "iam360-mcp": {
      "serverUrl": "https://app.iam360.ai/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like iAM360 MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run iAM360 MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing