Tavus

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-08-24. On 2026-09-04 the recorded URL answered an MCP initialize as a server, which is liveness and nothing more: nobody has run its tools.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://mcp.tavus.io/mcp (docs: https://docs.tavus.io/sections/agent-tools/mcp-server.md, https://docs.tavus.io/sections/agent-tools/mcp-tools-reference.md); community alternative at https://github.com/rakeshdavid/Tavus-MCP

• https://mcp.tavus.io/mcp
• https://docs.tavus.io/sections/agent-tools/mcp-server.md
• https://docs.tavus.io/sections/agent-tools/mcp-tools-reference.md
• https://github.com/rakeshdavid/Tavus-MCP

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

This list came from a repo the vendor does not own. Those are that author's tools for the vendor's API, not the vendor's own published surface, and the two must not be read as the same thing.

• create_conversation
  Create a new conversational video interface
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• create_lipsync
  Create a lipsync video by synchronizing audio with video
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• create_persona
  Create a new persona for conversational AI
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• create_replica
  Create a new AI replica from a training video
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• delete_conversation
  Delete a conversation permanently
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• delete_lipsync
  Delete a lipsync permanently
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• delete_persona
  Delete a persona permanently
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• delete_replica
  Delete a replica permanently
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• delete_speech
  Delete a speech permanently
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• delete_video
  Delete a video permanently
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• end_conversation
  End an active conversation
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• generate_speech
  Generate speech audio from text using a replica
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• generate_video
  Generate a video using a replica and script or audio
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_conversation
  Get details of a specific conversation
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_lipsync
  Get details of a specific lipsync
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_persona
  Get details of a specific persona
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_replica
  Get details of a specific replica
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_speech
  Get details of a specific speech
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_video
  Get details of a specific video
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_conversations
  List all conversations in your account
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_lipsyncs
  List all lipsyncs in your account
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_personas
  List all personas in your account
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_replicas
  List all replicas in your account
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_speeches
  List all speeches in your account
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_videos
  List all videos in your account
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• patch_persona
  Update a persona using JSON patch format
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• rename_replica
  Rename an existing replica
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• rename_speech
  Rename an existing speech
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• rename_video
  Rename an existing video
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.

This is a third party's CLI. It was published by somebody other than the vendor, so it is that author's surface for the vendor's API and not the vendor's published surface. The two must not be read as the same thing.

Install, as the source shows it:

pip install tavus-cli

quoted from https://pypi.org/project/tavus-cli/ on 2026-09-27, via pypi, a third party source

pip install tavus

quoted from https://pypi.org/project/tavus/ on 2026-09-27, via pypi, a third party source

Packages seen, with the version on 2026-09-27:

• pypi: tavus-cli 0.4.4, third party
• pypi: tavus 0.4.4, third party
• pypi: tavus-cli 0.4.4, third party

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.

api_gate, verbatim from the file:

free tier available. Free plan includes 25 minutes of conversational video/month; Starter/solo-developer tier is $59/mo (100 min + 3 custom replicas); Growth $397/mo (1,250 min); Enterprise custom. Overage billed per-minute.

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

• https://github.com/rakeshdavid/Tavus-MCP

github.com/Tavus-Engineering tied to the vendor by rule 3, account website tavus.io has the vendor's domain, confidence strong

The five most recently pushed, on 2026-09-08:

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

• Book a meeting
• Answer an inbound chat or call

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

• https://www.tavus.io/
• https://www.tavus.io/pricing
• https://docs.tavus.io/llms.txt
• https://docs.tavus.io/sections/agent-tools/mcp-server.md
• https://github.com/rakeshdavid/Tavus-MCP
• https://coldiq.com/blog/tavus-video-prospecting

6 source URLs. Raw sources field, verbatim:

https://www.tavus.io/, https://www.tavus.io/pricing, https://docs.tavus.io/llms.txt, https://docs.tavus.io/sections/agent-tools/mcp-server.md, https://github.com/rakeshdavid/Tavus-MCP, https://coldiq.com/blog/tavus-video-prospecting

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.