llms.txt for AI Editors
meetbot publishes /llms.txt and /llms-full.txt so AI coding tools can ground themselves on our docs in one fetch. Here's how to point Cursor, Claude Code, and ChatGPT at them.
llms.txt is a small Markdown file at the root
of a website that tells AI agents what's available and where to look.
It's the robots.txt of the LLM era — opt-in, structured,
machine-readable.
We publish two:
https://meetbot.dev/llms.txt— short overview with links to every doc page, the API surface, the SDK, and the MCP server. Fetch this first.https://meetbot.dev/llms-full.txt— full Markdown of every doc page concatenated, for one-shot grounding in agents that can't follow links.
Both are auto-generated from the Fumadocs source under
apps/web/content/docs/** so they never drift.
Point your tool at it
Cursor (@Docs)
Cmd+Shift+P → "Add new docs" → paste https://meetbot.dev/llms-full.txt →
name it meetbot. Then in any chat:
@Docs meetbot how do I dispatch a bot to a Zoom URL?Cursor will use the indexed doc to answer without fetching anything live.
Claude Code
In a turn, paste the URL — Claude will fetch it via WebFetch:
Read https://meetbot.dev/llms-full.txt and tell me how to verify a webhook.Or add to your project's CLAUDE.md:
When working with meetbot, the canonical reference is
https://meetbot.dev/llms-full.txt — fetch it before answering questions
about the meetbot API.ChatGPT / Claude.ai (web)
Just paste the URL into the chat. Both can fetch and parse
text/plain Markdown documents.
Custom RAG / agent
curl https://meetbot.dev/llms-full.txt > meetbot-docs.mdEmbed, chunk, index — the file is plain Markdown with stable section
headers (one ## <Page Title> per page, plus a Source: line with the
canonical URL).
What's in llms.txt
# meetbot
> meetbot is the open, EU-hosted, $0.30/hr meeting-bot API for
> Google Meet, Microsoft Teams, and Zoom…
## Overview
- [Getting Started](https://meetbot.dev/docs): …
## Basics
- [Webhooks — Signature Verification](https://meetbot.dev/docs/basics/webhooks-verify): …
- [Billing](https://meetbot.dev/docs/basics/billing): …
## Meeting Bots
- [Bot Quickstart](https://meetbot.dev/docs/meeting-bots/quickstart): …
- [Failure sub-codes](https://meetbot.dev/docs/meeting-bots/sub-codes): …
## API
- [POST /api/v1/jobs](…): dispatch a bot
- [GET /api/v1/jobs/:id](…): fetch one bot's status
- [Webhook signing](…): HMAC-SHA256 over the raw body
## SDKs and tools
- [@meetbot/sdk](https://www.npmjs.com/package/@meetbot/sdk)
- [@meetbot/mcp-server](https://www.npmjs.com/package/@meetbot/mcp-server)See also
- MCP server — for direct tool access (vs. doc grounding) in Cursor / Claude Code / Windsurf / Cline.
- llmstxt.org — the spec.
MCP Server (Cursor, Claude Code, Windsurf)
Plug meetbot into your AI coding assistant. The @meetbot/mcp-server npm package exposes 17 tools — dispatch bots, fetch recordings, control live bots, verify webhooks — over the Model Context Protocol.
Bot Features (coming soon)
Recording, separate audio, separate video, output media, chat send. Shipping with M1 bot control API.