Docs for AI assistants
Read the same public documentation through MCP or generated text files.
The documentation service exposes a read-only, public Model Context Protocol endpoint at /api/mcp. It reads the documentation bundled with this frontend deployment. It does not access your organization, run evaluations, create policies or expose account keys.
The endpoint is available when this version of the frontend is deployed. For a local rehearsal, replace the host with your running frontend URL, for example http://localhost:3000/api/mcp. Verify your deployed host before configuring a team-wide client.
Connect with Streamable HTTP
In VS Code, use the following .vscode/mcp.json configuration:
{
"servers": {
"nyraxis-docs": {
"type": "http",
"url": "https://nyraxis.io/api/mcp"
}
}
}In Cursor, add a remote MCP server using the same URL. A typical .cursor/mcp.json configuration is:
{
"mcpServers": {
"nyraxis-docs": {
"url": "https://nyraxis.io/api/mcp"
}
}
}For clients that support only a local command transport, use a compatible HTTP-to-stdio adapter such as mcp-remote. Review and pin any adapter your team installs; its settings belong to that client, not the Nyraxis SDK. This service uses Streamable HTTP rather than the legacy SSE endpoint.
Available tools
| Tool | Arguments | Result |
|---|---|---|
search_docs | query | Ranked public page titles, links and excerpts |
get_page | slug, such as guides/api-keys | Full page text |
get_integration | integration, such as langgraph | Integration guide |
get_provider | provider, such as secrets-detection | Provider settings and limits |
get_sdk | language: python or node | SDK reference |
list_integrations | None | All 24 integration recipes |
get_quickstart | None | First evaluation walkthrough |
Ask “Show the LangGraph agent journey and explain its tool authorization boundary” or “Which response fields show an incomplete evaluation?” Check linked source pages when using an assistant-generated answer.
Text files without MCP
- llms.txt contains the complete documentation index.
- llms-full.txt contains all page content, including examples and scope limits.
These assets and MCP content are generated from the same MDX source. Search uses that source too. Updating documentation requires regenerating the assets and deploying the frontend; it does not require exposing your account API key to an editor.