Speedrun

What the Speedrun MCP server does

The Speedrun MCP server exposes selected Speedrun.com API v1 data to MCP-compatible clients. It supports a lookup workflow that starts with a game search, continues by retrieving that game's categories, and then uses the resulting identifiers to fetch a leaderboard. A separate user search supports finding speedrunners by username.

Returned game records include the game ID, abbreviation, release year, and Speedrun.com link. Category results include category IDs and names such as Any%, 100%, or Glitchless. Leaderboard results contain ranked runs, durations in ISO-8601 format and seconds, run dates, player information, and run links. User results include matching IDs, display names, and profile links.

How it works

The tools use identifiers from earlier calls where the API workflow requires them:

• search_games accepts a game-name query and an optional maximum result count.
• get_categories accepts the game ID returned by search_games.
• get_leaderboard accepts a game ID, category ID, and optional top-result count.
• find_user searches for a speedrunner by username.

For example, an agent can search for “Super Mario 64,” select a matching game, list its categories, and request the top 10 runs for a selected category. The results provide links for checking the corresponding records on Speedrun.com.

Setup and configuration

The Speedrun MCP server can be connected through the hosted Pipeworx endpoint:

{
  "mcpServers": {
    "speedrun": {
      "url": "https://gateway.pipeworx.io/speedrun/mcp"
    }
  }
}

Claude Desktop, Cursor, and Windsurf are named as supported client examples. The hosted connection does not require an account for its first calls. Its tool list includes the four Speedrun tools plus shared Pipeworx meta-tools, including routing and discovery functions.

For a local connection, run the package with npx:

{
  "mcpServers": {
    "speedrun": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-speedrun"]
    }
  }
}

The local process communicates over stdin and stdout and does not require a Pipeworx account or a gateway round trip. It lists only the Speedrun package tools.

Limitations and notes

The Speedrun MCP server is focused on read operations described by the available tools: game search, category lookup, leaderboard retrieval, and user lookup.

The hosted pack endpoint and the full Pipeworx gateway use the same gateway infrastructure and data-source catalog, but they differ in which pack tools are listed directly. The pack endpoint includes shared gateway meta-tools by design. For a connection containing only the Speedrun tools, use the standalone stdio package instead.