Thyris Documentation MCP
The Thyris Documentation MCP is a public, read-only Model Context Protocol server that lets AI clients fulfill documentation-grounded actions against the content published on docs.thyris.ai. A client can ask a direct question, request an explanation or comparison, troubleshoot a problem, summarize a subject, ask for a recommendation, or build an implementation plan. The server finds and reads the relevant sources before the client produces the result.
URL: https://docs.thyris.ai/mcp
The /mcp endpoint is a protocol endpoint. Opening it in a normal browser tab is not a valid MCP test because browsers do not send MCP JSON-RPC messages by default.
What the Server Provides
The server exposes seven read-only tools. resolve_docs_action is the default AI-native entry point; the remaining tools provide explicit control for follow-up research:
| Tool | Purpose |
|---|---|
resolve_docs_action | Accept any user action, detect its intent, retrieve and read multiple sources, and return citation-ready evidence. |
research_docs | Turn an implementation goal and code context into a multi-query, ordered reading plan. |
search_docs | Run a focused, passage-level follow-up search with domain-aware query expansion. |
read_documents | Read several selected sources as a bounded evidence pack. |
get_document | Read the complete Markdown source of one published document. |
find_related_docs | Follow direct links, backlinks, and topically similar pages to close evidence gaps. |
list_doc_sections | List all published pages or pages within one top-level section. |
A typical client workflow is:
For most requests, the client should pass the user's complete request to resolve_docs_action. Optional context can contain conversation details, constraints, environment facts, or inspected code facts. The tool detects whether the user wants an answer, explanation, comparison, recommendation, summary, troubleshooting help, or implementation work; it then retrieves and reads a diverse set of relevant documents. The client synthesizes the requested result only after reviewing that evidence.
Content Coverage
The MCP server searches the public Thyris documentation available on docs.thyris.ai. Returned results can include page titles, headings, relevant passages, related pages, and public URLs. Private, unpublished, and internal material is not available through the server.
Server Characteristics
| Characteristic | Current behavior |
|---|---|
| Transport | Streamable HTTP |
| Authentication | None |
| Access | Public, read-only |
| Endpoint path | /mcp |
| Rate limit | 30 MCP HTTP requests per minute per client |
| Tool side effects | None; all tools declare read-only and idempotent annotations |
The rate limit applies to MCP HTTP requests, not only tool calls. Client initialization and tool discovery also consume requests. See Troubleshooting for limit behavior and common errors.
Documentation Map
| Document | Use it for |
|---|---|
| Installation and Configuration | Connect Claude, ChatGPT, Codex, VS Code, MCP Inspector, or another compatible client. |
| Tools | Review every tool, parameter, return field, error, and recommended workflow. |
| Request Examples | Run JSON-RPC, curl, and natural-language tool-call examples. |
| Troubleshooting | Diagnose connection, request, rate-limit, and search problems. |
Quick Start with Codex
Register the URL with Codex:
codex mcp add thyris_docs --url https://docs.thyris.ai/mcp
codex mcp get thyris_docs
codex mcp list
Then ask Codex:
Use the thyris_docs MCP server to explain how Merchant catalog webhooks work, when I should use them, and what security controls I need. Find and read the relevant documents before answering, combine details across sources, and cite every documentation URL used.