Octane MCP
The remote MCP server forOctane— docs search, real-compiler.tsrxvalidation, and bindings knowledge for AI agents, no install required.
Connect
The MCP endpoint speaks stateless Streamable HTTP atPOST https://mcp.octanejs.dev/v1/mcp:
claude mcp add --transport http octane https://mcp.octanejs.dev/v1/mcp
Tools
octane_docs_search- Section-level full-text search over the official Octane docs.
octane_docs_read- Read one doc as markdown by slug.
octane_compile- Compile/validate pasted .tsrx source with the real Octane compiler.
octane_bindings- The React-package → @octanejs/* binding map and catalog.
octane_bindings_status- Per-binding parity status: upstream version, surface, divergences, SSR.
octane_bridge_scan- Scan pasted React source for a compatibility report and migration plan.
octane_skill- Task guides: bridging packages, migrating components, SSR setup.
Plain HTTP
No MCP client handy? The same knowledge is served as versioned JSON and text:
GET /v1/docs- Docs index (slugs, titles, sections).
GET /v1/docs/:slug- One doc as JSON, markdown included.
GET /v1/bindings- Binding map, catalog, and per-package status.
GET /llms.txt- The condensed agent-facing summary of Octane.
GET /llms-full.txt- llms.txt plus the full docs corpus, one plain-text file.
Versioning
The/v1prefix is the API contract: tools and response shapes stay stable within it, while the served knowledge tracks the latest Octane release. Breaking changes ship as a new/v2prefix alongside.