Skip to main content

Troubleshooting

The Thyris Documentation MCP is a public, read-only service. Connect an MCP-compatible client to this exact endpoint:

https://docs.thyris.ai/mcp

A normal browser request is not a complete protocol test. Use an MCP client, MCP Inspector, or a valid JSON-RPC initialize request.

Request Limits​

The endpoint permits 30 MCP HTTP requests per minute per client. Initialization, tool discovery, and tool calls all count toward this limit. When a request returns HTTP 429, wait for the duration in the Retry-After response header before retrying.

Troubleshooting​

/mcp returns 404​

Confirm that the URL is exactly https://docs.thyris.ai/mcp. Do not use the documentation site root or append another path. If the exact endpoint still returns 404, try again later or contact Thyris support.

GET /mcp returns 405​

This can be expected. Send a valid MCP JSON-RPC request with POST, or connect with MCP Inspector or an MCP-compatible client.

Requests return 429​

Wait for the duration in the Retry-After response header. Reduce repeated tool discovery, avoid reconnect loops, and filter list_doc_sections by section when possible.

Codex does not show thyris_docs​

Check registration:

codex mcp get thyris_docs
codex mcp list

Restart the Codex CLI session, desktop application, or IDE extension after changing MCP configuration.

Search returns no results​

  • Use at least two characters.
  • Prefer exact product, endpoint, header, service, or capability terms.
  • Remove conversational filler from the query.
  • Confirm that the subject appears in the public Thyris documentation.

For normal questions and requested actions, prefer resolve_docs_action and preserve the complete user request. Simplifying text into search terms is only useful when directly calling search_docs for a focused follow-up.

resolve_docs_action selects weak evidence​

  • Add the relevant top-level section when the domain is known.
  • Supply concise constraints, environment facts, or inspected code facts through context.
  • Use search_docs for a focused follow-up, then read the selected source with get_document or read_documents.
  • Use find_related_docs when the initial evidence omits a prerequisite, security control, payload detail, or operational requirement.

get_document reports “Document not found”​

Call search_docs and pass the exact path returned in the search result. Public page URLs and MCP document paths are not always identical.

Security Model​

The server is public and unauthenticated by design. Its risk is constrained by:

  • Read-only, idempotent tools.
  • Only public Thyris documentation is available.
  • Input length and result-count validation.
  • Request limiting.

The MCP tools cannot edit documents, change user data, or perform actions in external systems.