Reference

Docs MCP server

Point any MCP client at the docs server and your agent searches and reads these pages mid-conversation.

The docs site runs its own Model Context Protocol server at https://docs.polylane.com/mcp, so any MCP client can search and read these pages while you work. It only reads documentation; to give an agent access to your workspace (topology, issues, threads), use the platform MCP server.

Tools

ToolDescription
list-pagesLists every page with its title, path, description and full URL. It takes no parameters, and agents call it first to find what exists.
get-pageReturns one page in full: title, description and markdown. It takes one parameter, path, a page path from list-pages such as /investigate/autofix.

Resources

Clients that support MCP resources can read the documentation without calling a tool.

ResourceURIDescription
docs-indexhttps://docs.polylane.com/llms.txtThe llms.txt index: every page with its title, description and raw markdown URL, organized by section.
docs-fullhttps://docs.polylane.com/llms-full.txtThe complete content of every page in one markdown document.

Both URIs are plain HTTPS URLs too, so anything that cannot speak MCP can fetch them directly.

Install in your editor

Terminal
claude mcp add --transport http polylane-docs https://docs.polylane.com/mcp

Once connected, your editor's agent searches the docs mid-conversation, cites exact pages and stays current as the documentation changes.

  • Platform MCP server to query your own workspace from the same editor.
  • llms.txt for the same pages as plain text, without MCP.
  • Plugins to install both MCP servers in one step.