Read these docs through MCP
Give your agent searchable Ravensight documentation while it integrates your game or audits existing tracking. Documentation reads are free and require no account, API key, or prepaid balance.
This public server reads the documentation on this page. It cannot see your studio, query player data, change your project, or spend Ravensight units. The analytics MCP is a separate, authenticated service with its own metering. Your agent provider may still charge for the agent's work.
1. Connect your agent
Use this remote HTTP MCP URL, with authentication set to none:
https://docs-mcp.ravensight.io/mcp
Codex CLI
codex mcp add ravensight-docs --url https://docs-mcp.ravensight.io/mcp
Claude Code
claude mcp add --transport http ravensight-docs https://docs-mcp.ravensight.io/mcp
VS Code / GitHub Copilot: merge into .vscode/mcp.json
{
"servers": {
"ravensight-docs": {
"type": "http",
"url": "https://docs-mcp.ravensight.io/mcp"
}
}
}
Keep your other server entries when merging configuration. Reload the agent's tools if needed. In another MCP-compatible client, add the same URL as a remote server. In ChatGPT, use a supported custom MCP connection if your account and workspace allow it; connecting the docs does not grant access to your code.
Client setup references: Codex, Claude Code, and VS Code. Client interfaces and workspace policies may differ.
2. Ask a concrete integration question
Use ravensight-docs to find the event payload limits and Godot
session setup instructions. Read the relevant sections, cite their
links, and compare them with the SDK version installed in this project.
| Tool | What it returns |
|---|---|
search_docs(query, limit?, section?) | Up to 10 relevant records with excerpts, IDs, source links, and content revisions. An optional section narrows the search. |
get_doc(id, offset?, max_chars?, revision?) | A Markdown record with code examples and tables. For long records, continue at next_offset with the same document revision. |
Clients that browse MCP resources can open ravensight-docs://index and the individual document resources. A section link may point to its parent section when the website has no more specific anchor. The server retrieves documentation; your agent interprets it and should check it against your installed SDK.
3. Use it with the instrumentation skill
The instrumentation skill supplies the audit and implementation workflow. This server supplies current documentation. They work together, and each remains useful on its own. The skill installer does not add MCP connections or change your agent's settings.
Freshness, limits, and troubleshooting
The catalog is generated from this page on every website build. Responses include document and catalog revisions, the last successful source check, and a stale flag. Normal refresh is within five minutes. If the source is temporarily unavailable, previously validated content may be served for up to one hour and is marked stale. After that, the server reports unavailable; read this page directly.
- No tools: confirm the URL ends in
/mcp, choose remote HTTP, and reload the connection. This service needs no bearer token. Opening the MCP URL in a browser may return 405 because MCP requests use POST. - Too many requests (429): pause and retry with backoff. Public capacity is shared; avoid polling or sending the entire codebase as a search query.
- Stale or unavailable: check service health and use the ordinary docs links. A healthy transport alone does not prove telemetry delivery in your game.
- Document changed while paging: restart at offset 0. Search again for an unknown ID. Narrow broad searches using a section from the index.
Send only documentation questions, not credentials, private source, or player data. The server does not call an AI model or store search queries in an application database. Operational request metadata may be recorded by the hosting provider. Source and deployment instructions are in the public ravensight-docs-mcp repository; the generated documentation catalog is also available without MCP.