AI tools

These docs are machine-readable. There is an MCP server that any compatible assistant can connect to, and a set of plain-text files for tools that don't speak MCP. Both serve the same content as the pages you're reading — so an assistant using them cites what is actually documented rather than reconstructing an API from training data.

MCP server

https://www.fftvisualizer.com/mcp

Streamable HTTP, no authentication, no API key. Nothing to install.

Claude Code

claude mcp add --transport http fft-visualizer https://www.fftvisualizer.com/mcp

Other clients

Most MCP clients take a JSON block like this — the file it goes in and the exact field names vary, so check your client's own docs:

{
  "mcpServers": {
    "fft-visualizer": {
      "type": "http",
      "url": "https://www.fftvisualizer.com/mcp"
    }
  }
}

Available tools

• list-pages — every documentation page, with its title, path and description.
• get-page — the full Markdown of one page, given a path from list-pages.

A typical exchange is one list-pages call to find the right page, then one get-page to read it — so a question about, say, Nuxt integration is answered from that page verbatim.

Without MCP

For assistants that can fetch a URL but don't support MCP, the same content is available as plain text:

• /llms.txt — an index: every page with a one-line summary and a link.
• /llms-full.txt — the entire documentation in a single file, around 55 KB.
• /raw/<path>.md — any single page as Markdown, e.g. /raw/vue/nuxt.md.

Pasting llms-full.txt into a chat is the zero-setup option: it fits comfortably in a modern context window and covers the guide, the Core API, and both wrappers.