Skip to navigation

Docs for Agents & LLMs

Everything here is machine-readable, point your agent at it

View as Markdown

These docs are built to be read by agents as much as by humans. If you’re integrating MeetStream with Claude, Cursor, or any LLM-driven workflow, start here.

The machine-readable surface

ResourceURLWhat it’s for
llms.txt indexdocs.meetstream.ai/llms.txtThe page index agents should fetch first
Markdown twin of any pageappend .md to any docs URLClean Markdown, no HTML chrome - e.g. docs.meetstream.ai/guides/help/faq.md
OpenAPI specdocs.meetstream.ai/openapi.jsonThe full API schema for codegen and validation

Two MCP servers (use both)

  • Docs-search MCP - https://docs.meetstream.ai/_mcp/server - searches these docs. Read-only, no key needed.
  • Action MCP - https://mcp.meetstream.ai/mcp (hosted: sign in with OAuth or send your key) - actually does things: creates bots, pulls transcripts and status, sends messages into live meetings. This is the one that lets an agent debug a real bot session.

In Claude Code, add the action MCP with one command, then the agent skills plugin for MeetStream-specific coding knowledge. The plugin ships skills only, so install it alongside the MCP server:

claude mcp add --transport http meetstream https://mcp.meetstream.ai/mcp
# then run /mcp, choose meetstream and Authenticate: sign in at app.meetstream.ai and click Allow
/plugin marketplace add meetstream-ai/claude-plugin
/plugin install meetstream@meetstream-ai

For a copy-paste guide that points a coding agent at all of this and then builds a full app, see Agent Quickstarts.

Agent-friendly CLI

Every @meetstream/cli command supports --json, so agents can drive the full API from a shell without parsing prose:

meetstream bot create "https://meet.google.com/abc-defg-hij" -t deepgram --json
meetstream bot status <bot_id> --json
meetstream transcript <bot_id> --wait --json

Ground rules worth telling your agent

  • Auth is Authorization: Token <key> - Token, not Bearer. The word matters.
  • create_bot requires meeting_link. bot_name is optional (default MeetStream).
  • Webhook envelopes carry both event and bot_event; every ending arrives once as event: "bot.stopped" and bot_event gives the reason (bot_status can’t tell a kick from a clean exit). bot.done is the final event on every path. Details in Debugging Bots.
  • An Idempotency-Key replay returns 507 with the original bot - treat as success, never retry-loop on it.
  • Media links are presigned and expire - re-fetch the endpoint, don’t cache URLs.