Skip to main content
How do I point my agent, IDE, or automation at Tavus’s documentation and HTTP APIs? This guide helps you pick the right artifact for your workflow.
For AI agents: The MCP endpoint documented on this page (https://docs.tavus.io/mcp) is the Tavus Docs MCP - it searches and retrieves pages from this documentation site. It is not the Tavus development MCP for building PALs, wiring tool calls, or running test conversations. For that toolkit, see Tavus MCP & CLI.

Documentation bundle reference

ArtifactRoleURL
llms.txtCurated directory of doc URLs for selective fetchhttps://docs.tavus.io/llms.txt
llms-full.txtFull bundled text export for offline or bulk ingesthttps://docs.tavus.io/llms-full.txt
openapi.yamlHTTP API contract (paths, request/response schemas, security schemes)https://docs.tavus.io/openapi.yaml
skill.mdAgent-oriented capability summary (Agent Skills conventions)https://docs.tavus.io/skill.md
Tavus Docs MCPHosted Model Context Protocol server for this docs site: search plus fetch full pages from the indexed documentation (see Tavus Docs MCP)https://docs.tavus.io/mcp

When to use what

  • Tavus Docs MCP: Interactive tools that need live search and current page retrieval against the indexed documentation site.
  • llms-full.txt: Bulk or offline ingestion; snapshot of doc text (not a substitute for OpenAPI).
  • openapi.yaml: Source of truth for HTTP APIs (requests, responses, auth headers); agents should not invent endpoints that contradict it.
  • llms.txt / selective fetches: Discovery and pulling specific pages when you do not want the full bundle.
  • skill.md: Compact capability orientation for agents; still point to OpenAPI and deep docs for details.

Tavus Docs MCP

An MCP endpoint is available for this documentation site - not for building PALs or testing Tavus API tool calls; for that, use Tavus MCP & CLI. Configure docs MCP clients that support HTTP transport with:
{
  "url": "https://docs.tavus.io/mcp",
  "transport": "http"
}
Use MCP when the tool needs live search and retrieval against the current indexed documentation, not a frozen file export.