Tellers.AI

ai.tellers.mcpPublished by mcp.tellers.aiOfficial publisherv0.0.1Updated Oct 24, 2026

This MCP lets your agent edit your videos, generate voiceovers, AI clips, titles, motion, music, etc

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Tellers.AI is a remote MCP server that lets an AI assistant edit your videos and generate voiceovers, AI clips, titles, motion and music.

What you can do
Edit videos through the assistant, including cutting and assembling footage into a finished piece. Generate voiceovers and AI-generated clips for a project. Add titles, motion effects and music to videos. The manifest lists no individual tools, so the exact operations available are not documented here.
When to use it
Use it when you want an assistant to help produce or revise video content, such as adding narration, titles, music or generated clips, rather than editing by hand in a separate editor.
Requirements
A remote MCP endpoint at mcp.tellers.ai over streamable HTTP, with OAuth sign-in required. No environment variables, headers or local packages are declared.
Before you install
Access is tied to your Tellers.AI account through OAuth, and your video material and generated assets are handled by that third-party service. Editing actions may change or overwrite existing project content, so confirm before applying changes. Pricing and storage terms are not stated in the input.

Installation

In SourceWeft

  1. Open Tellers.AI in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.tellers.mcp%2Ftellers-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tellers-ai": {
      "type": "http",
      "url": "https://mcp.tellers.ai/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.0.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.