Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.amps.ai/llms.txt

Use this file to discover all available pages before exploring further.

The Documentation MCP server grounds your agent in the Amps docs corpus. Plug it into Claude Desktop, Cursor, Windsurf, Continue, or any custom MCP client and your agent stops hallucinating mode names like selfconsumption or gridcharge. It uses the canonical vocabulary directly: auto.balanced, auto.export, charge, discharge, with the live API contract one query away. The server is hosted at https://docs.amps.ai/mcp and speaks the Model Context Protocol over JSON-RPC. Nothing to deploy. This is the grounding surface: the agent searches docs, reads recipes, looks up canonical names, and queries the live OpenAPI spec. For the surface that lets an agent call the Amps API on a user’s behalf, see the Execution MCP.

​
What the server exposes

Two tools, both read-only, both stateless. Each call resets the working directory to / and discards shell variables.
  • search_amps_ai_documentation runs a semantic search across every Amps docs page and returns ranked snippets with titles, page paths, and direct links. Reach for it on conceptual questions: “how does scheduling work”, “what does auto.balanced do”.
  • query_docs_filesystem_amps_ai_documentation runs shell-style commands (rg, grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq) against a virtual filesystem rooted at /. The filesystem holds every published .mdx page plus the OpenAPI spec at /openapi/openapi.json. Reach for it on exact lookups: read a page, grep a canonical name, list endpoint paths.
See the tools reference for input and output shapes.

​
Why it matters

Your agents stop hallucinating mode names like selfconsumption or gridcharge and use the canonical vocabulary directly: auto.balanced, auto.export, charge, discharge. Your CI can fail builds when an internal config drifts from the public schema, by querying the spec at build time. Your support tooling can answer customer questions in the exact language of the API. The corpus behind the endpoint is the same one that backs https://docs.amps.ai. One source of truth, no drift.

​
Quick connect

Add the Documentation MCP server to Claude Desktop by editing ~/Library/Application Support/Claude/claude_desktop_config.json: 
{
  "mcpServers": {
    "amps-docs": {
      "url": "https://docs.amps.ai/mcp"
    }
  }
}
Restart Claude Desktop. A hammer icon appears in the chat input once the tools have loaded. For Cursor, Windsurf, Continue, and custom MCP clients, see the install guide.

​
What next

Install

Per-client config snippets for Claude Desktop, Cursor, Windsurf, Continue, and custom clients.

Tool reference

Input shapes, output examples, and call patterns for the two server tools.

Examples

Concrete agent workflows: write a curl from a prompt, validate config, build an integration.

Execution MCP

The companion surface for calling the Amps API on a user’s behalf. Coming soon.