Skip to main content
The Aspect documentation is served through a hosted Model Context Protocol (MCP) server. Connecting your AI coding assistant to it lets the assistant search and read the Aspect docs directly while it works in your repo. Use it for tasks like migrating YAML tasks to AXL, extending Gazelle in Starlark, upgrading Aspect Workflows, or wiring up the Aspect CLI in CI. This server serves documentation. To give an agent your build and test results, see Build results over MCP.

MCP server URLs

The anonymous endpoint serves every public page: Aspect Cloud, the Aspect CLI, the open-source rulesets and the training courses. The authenticated endpoint adds the installation and configuration pages for Aspect Enterprise, so agents working on an Enterprise deployment can read them. It needs a one-time OAuth authorization with an Aspect account that has customer documentation access. Documentation search and retrieval are read-only; the server also exposes an optional tool for submitting documentation feedback.

Quick copy from any docs page

Every page on this site exposes a contextual menu (top of the page) with one-click options to:
  • Copy MCP Server: Copies the anonymous endpoint to your clipboard.
  • Connect to Cursor: Installs the anonymous endpoint in Cursor.
  • Connect to VS Code: Installs the anonymous endpoint in VS Code.

Connect from common clients

Claude Desktop

  1. Open Settings → Connectors in Claude.
  2. Click Add custom connector.
  3. Set the name to Aspect Docs and the URL to https://aspect.build/mcp.
  4. Click Add.
  5. In a Claude chat, click the attachments (+) button and select Aspect Docs to give that thread access to the Aspect docs.

Claude Code

Verify with:

Codex CLI

Add the server to ~/.codex/config.toml:
Then start a Codex session and ask “What tools do you have available?” The aspect-docs server should be listed.

Cursor

  1. Open the command palette with Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux).
  2. Run Open MCP settings.
  3. Click Add custom MCP and add the following to mcp.json:

VS Code

Create .vscode/mcp.json in your workspace with:
See the VS Code MCP documentation for details on scope and permissions.

What the assistant can do with it

Once connected, the assistant can:
  • Search the Aspect docs across the CLI, Aspect Workflows, AXL reference, and Bazel guides.
  • Fetch full pages as Markdown when it needs the complete instructions (for example, an upgrade guide or a migration walk-through).
  • Cite the page it used, so you can jump to the source directly.
The migration docs recommend pointing an AI coding assistant at them for the bulk of a YAML-to-AXL conversion.

Troubleshooting

  • The tool doesn’t appear after adding it. Restart the AI client after editing mcp.json / config.toml. Most clients only load MCP servers at startup.
  • The client can search public docs but can’t find Aspect Enterprise docs. Check that it uses https://aspect.build/authed/mcp, then complete the client’s OAuth login. The /mcp endpoint is anonymous and public-only.
  • The client reports 401, 405, or “method not allowed” when opening the URL in a browser. That’s expected: the MCP endpoints respond to MCP protocol requests, not plain GET requests. Configure the URL in your MCP client instead of visiting it directly.