Riot Docs

You can access Riot Games API endpoint documentation through this MCP server, enabling you to explore and retrieve endpoint details and parameters from Riot’s documentation directly within your MCP client workflow.

How to use

Use your MCP client to connect to the Riot Docs MCP server. You have two primary ways to run the server locally and expose its API documentation tools to your MCP environment:

How to install

Prerequisites: you need a system with Node.js and a compatible MCP client installed. Ensure you have either npm or a local runtime for MCP commands.

{
  "mcpServers": {
    "riot_docs": {
      "command": "uv",
      "args": [
        "--directory",
        "/absolute/path/to/riot-docs",
        "run",
        "riot_docs_server"
      ]
    }
  }
}

Additional configuration and usage notes

You can also run the Riot Docs MCP using the Smithery CLI with an API key. This method is useful when you want the MCP client to manage access keys centrally. The key is passed as a parameter in the following setup.

{
  "mcpServers": {
    "riot_docs_mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli@latest",
        "run",
        "@chirpon9/riot-docs-mcp",
        "--key",
        "{SMITHERY API KEY}"
      ]
    }
  }
}

Security and keys

If you use the MCP with a key, keep the key value secure and avoid storing it in plain text in shared configurations. Use environment variables or a secure secret management mechanism where possible.

Troubleshooting

If you cannot retrieve endpoint documentation, verify that the Milan CLI wrapper is installed and that the Riot Docs server is reachable from your MCP host. Check that the path in the first configuration matches where you store or build the Riot Docs server assets.

Available tools

list_available_docs

Lists all 33 available Riot API endpoint documentation files so you can see what is documented and pick what you want to inspect.

get_endpoint_docs

Retrieves the full documentation for a specific Riot endpoint given a filename, including endpoints, parameters, and response formats.