Agent collaboration
MCP and WebMCP tools
Use QueryHost's public playground with a compatible browser agent while keeping the result visible and controllable in the page.
Available tools
| Tool | Purpose |
|---|---|
list_supported_games | Lists canonical game IDs, ports, recommended modes, and capability support from the installed QueryHost registry. |
query_game_server | Queries a public game server through the same bounded route as the human playground, renders it in the page, and returns a summary, playground link, and complete structured result to the agent. |
compare_game_servers | Queries two to four servers sequentially and returns ordered results, including individual failures, warnings, and source details. |
People and agents share one result
For remote clients such as ChatGPT, connect to https://query.host/mcp using Streamable HTTP. This server endpoint exposes the same tools and returns structured data directly, without requiring an open playground. The existing private Railway API still performs production queries. No client account or API token is required. Remote responses omit binary assets and raw data and bound large detail lists. Omitted details are reported explicitly; the playground retains the full result.
An agent can discover a supported profile and start a query without guessing at the page controls. QueryHost then fills the existing form, updates the share URL, and displays the same overview, game data, source provenance, warnings, and JSON available to a person. The person can inspect that result, change any input, and continue with the normal playground. For comparisons, each result is displayed in turn and the last remains visible; the agent receives the complete ordered set. Query failures do not prove a server is offline, and query RTT is measured from QueryHost, not the user's machine.
Server cards in ChatGPT
Compatible MCP Apps hosts can show query results as inline server cards and comparisons side by side. Cards show population, version, map, query RTT, warnings, and expandable source details, with links to the full playground. Missing values stay missing, and a failed query is shown as a query failure. Text and structured results remain available in clients without card support. Refresh your MCP connection after a deployment that changes tool metadata.
Same security boundary
WebMCP does not create another API or grant new network access. Tool execution calls the same-origin POST /api/query route, which preserves the web caller gate, private API authentication, target validation, resource limits, cache semantics, and stable result contract. The private Railway hostname and origin token never enter browser code.
Browser support
QueryHost uses the current imperative document.modelContext API and registers tools only when the browser exposes it. Browsers without WebMCP keep the complete human playground with no polyfill or compatibility layer.
Open query.host in ChatGPT's in-app browser or a WebMCP-enabled version of Chrome to let a compatible agent discover the tools.