Koskamo

livedot MCP

The livedot MCP server enables AI agents to track participants in live running and cycling races, find local sports clubs and coaches, and retrieve detailed race-day weather forecasts. It provides tools to locate individuals by name, check event status, and access route data, all without requiring user authentication.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

livedot MCP logo, by livedotNo sign-inEndpoint checked 2026-10-18Operated by livedot
MCP endpoint (Streamable HTTP)
https://livedot.me/mcp
Vendor documentation

What you can do with it

  • Track a specific runner's location and pace during a live race
  • Find nearby running or cycling clubs based on user location
  • Retrieve weather forecasts for a specific race course
  • Locate certified coaches for training plans
Tools advertised by the last live check:
  • find_person
  • where_is
  • event_status
  • club_in_race
  • event_weather
  • fly_route
  • tour_route
  • tour_notes
  • tap_on_the_back
  • find_clubs
  • find_events
  • find_coaches
  • plan_route
  • list_my_events
  • create_event
  • update_event
  • add_tour_notes
  • publish_event
  • post_club_ride
  • invite_members

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 a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http livedot-mcp https://livedot.me/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 livedot-mcp --url https://livedot.me/mcp

Cursor

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "livedot-mcp": {
      "type": "streamableHttp",
      "url": "https://livedot.me/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start livedot-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "livedot-mcp": {
      "type": "http",
      "url": "https://livedot.me/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 livedot-mcp https://livedot.me/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": {
    "livedot-mcp": {
      "url": "https://livedot.me/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": {
    "livedot-mcp": {
      "serverUrl": "https://livedot.me/mcp"
    }
  }
}

Do you run livedot 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