Model Context Protocol

steamwebapi MCP for AI coding agents

Plug Claude Code, Cursor, Windsurf, Zed or Continue.dev directly into the steamwebapi.com knowledge base. Agents get fuzzy endpoint search, full request/response schemas and curated Steam domain concepts — no more copy-pasting documentation.


                https://mcp.steamwebapi.com/mcp

Get an API key

Install in your editor

Pick the snippet for your client. Project-scoped configs (like .mcp.json in the repo root) let a whole team share the same MCP setup via git.

Claude Code

CLI (user-scope, all projects)

claude mcp add steamwebapi --transport http --url https://mcp.steamwebapi.com/mcp

Project-scoped — .mcp.json in repo root

{
  "mcpServers": {
    "steamwebapi": {
      "type": "http",
      "url": "https://mcp.steamwebapi.com/mcp"
    }
  }
}

Cursor

~/.cursor/mcp.json (or Settings → MCP)

{
  "mcpServers": {
    "steamwebapi": {
      "url": "https://mcp.steamwebapi.com/mcp"
    }
  }
}

Windsurf

Settings → Cascade → MCP Servers

{
  "steamwebapi": {
    "serverUrl": "https://mcp.steamwebapi.com/mcp"
  }
}

Zed

settings.json

{
  "context_servers": {
    "steamwebapi": {
      "command": { "path": "https://mcp.steamwebapi.com/mcp" }
    }
  }
}

Continue.dev

~/.continue/config.json

{
  "experimental": {
    "modelContextProtocolServers": [
      { "transport": { "type": "http", "url": "https://mcp.steamwebapi.com/mcp" } }
    ]
  }
}

Tools the MCP server exposes

Tool	What it returns
search_endpoints	Fuzzy search across all endpoints and Steam domain concepts.
get_endpoint	Full OpenAPI spec for a single endpoint: parameters, responses, examples.
list_endpoints	Enumerate every endpoint grouped by tag.
list_games	Supported Steam games with appId and query slug.
list_markets	Third-party marketplaces covered by the price-API.
list_products	Product packages and the endpoints each one bundles.
get_concept	Domain glossary: assetid, doppler phase, pricelatest, marketable, etc.
list_concepts	Enumerate every domain concept, optionally filtered by category.

Resources the MCP server exposes

docs://swagger Live OpenAPI 3.0 specification (5-minute cache).
docs://llms-full Curated long-form overview with all games, markets and products.
docs://markdown/<file> Static documentation files (price-doc, response-format, market-index history, …).
docs://markdown/phases.json CS2 Doppler phase image-hash table.

How it works

Your AI agent talks to the MCP server over Streamable HTTP. The server reads the live OpenAPI specification of steamwebapi.com so every endpoint, parameter and response stays in sync with the production API. Domain concepts (Doppler phases, wear ranges, pricing fields, assetid vs classid) are exposed as a curated glossary.

All discovery tools work without an API key. Live data tools (planned next phase) will use your existing steamwebapi API key passed via the standard MCP Authorization header.