Skip to main content
Your AI coding tools can query Flint AI CLI documentation directly — no browser tab, no context switching. Ask a question in your IDE and get answers grounded in the latest docs.

​
MCP server

The Flint AI CLI docs MCP server lets AI tools like Claude Code, Cursor, and Windsurf read documentation programmatically. Your agent asks “how do I add input guardrails?” and gets the current answer from the docs, not a stale training cutoff. 
claude mcp add --transport http flintai-docs https://sandboxaq.mintlify.app/mcp
Once connected, your AI tool can search across all flintai-cli documentation and return grounded, cited answers in your workflow.

​
Machine-readable docs

Flint AI CLI publishes an llms.txt file that gives AI agents a structured index of every docs page — titles, descriptions, and URLs. AI tools use this to discover what documentation is available without crawling the site.
  • llms.txt — lightweight index of all pages
  • llms-full.txt — full content of all pages in a single file

​
Contextual menu

Every page in the Flint AI CLI docs includes a contextual menu that lets you send content directly to your preferred AI tool. Click the menu on any page to:
  • Copy as markdown - paste into any AI conversation
  • Open in Claude - send the page content to Claude
  • Open in Cursor - load the page as context in Cursor
  • Open in VS Code - use with Copilot or other VS Code AI tools

​
Why this matters

AI developers spend most of their time in the terminal and IDE, not in a browser. Programmatic docs access means:
  • No context switching - ask questions without leaving your editor
  • Always current - your AI tool reads the live docs, not cached training data
  • Framework-aware - ask “how do I scan a LangChain agent?” and get the specific answer, not a generic overview