Tegas MCP Server

Tegas turns an idea into a finished short video. An agent writes a scenario with Tessa (our scenario model), optionally attaches reference images of your product or characters, generates a 5–60 second video with voice-over, subtitles and music, and can then edit the result — scenes, voice, subtitles, music, volumes — and rebuild it.

Tegas runs a hosted remote MCP server, so there is nothing to install or self-host:

https://api.tegas.ai/mcp

• Transport: Streamable HTTP (stateless)

• Auth: Authorization: Bearer tg_live_...

• Russian mirror: https://api.tegasai.ru

This repository holds the public metadata and documentation for the Tegas MCP server (server.json, install instructions, issue tracker). The server implementation itself is closed source.

Prerequisites

1. A Tegas account — sign up at tegas.ai (RU: tegasai.ru).

2. An active paid plan. Video rendering and hero sheets spend tokens, and the paid tools refuse to run without an active plan.

3. An API key: in the Tegas cabinet go to Settings → API → Create key. The key looks like tg_live_.... Treat it like a password.

Related MCP server: ittybitty MCP server

Install

Claude Code

claude mcp add --transport http tegas https://api.tegas.ai/mcp \
  --header "Authorization: Bearer tg_live_..."

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

{
  "mcpServers": {
    "tegas": {
      "url": "https://api.tegas.ai/mcp",
      "headers": {
        "Authorization": "Bearer tg_live_..."
      }
    }
  }
}

VS Code

Add to .vscode/mcp.json in your workspace (this keeps the key out of the file by prompting for it once and storing it in VS Code's secret storage):

{
  "inputs": [
    {
      "id": "tegas-key",
      "type": "promptString",
      "description": "Tegas API key (tg_live_...)",
      "password": true
    }
  ],
  "servers": {
    "tegas": {
      "type": "http",
      "url": "https://api.tegas.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${input:tegas-key}"
      }
    }
  }
}

Claude.ai custom connector

Tegas is not (yet) in the Claude connectors directory, so add it as a custom connector:

1. Open Settings → Connectors on claude.ai.

2. Choose Add custom connector.

3. URL: https://api.tegas.ai/mcp.

4. Under advanced settings, add the header Authorization with the value Bearer tg_live_....

Custom connectors are available on paid Claude plans. See Anthropic's guide to custom connectors.

Tools

12 tools. Only two of them ever spend tokens.

Paid tools never spend tokens on the first call. With confirm=false (the default) they return the price and wait for your consent; only a second call with confirm=true charges. Every render carries an Idempotency-Key, so retrying after a timeout never charges twice. A failed render is refunded.

Current prices are always live from tegas_account — check there rather than trusting any number written down here.

Example

Make a 15-second vertical video about a cozy coffee shop in Russian, 720p. Show me the scenario and the price first.

Privacy and data

• The prompts, ideas, reference images and music you pass to the tools are sent to Tegas servers to generate and store your videos, and are associated with the account that owns the API key.

• Reference images on the hosted connector must be passed as base64 — the connector cannot read files from your machine (file_path works only on local/self-hosted runs with MCP_ALLOW_LOCAL_FILES=true).

• Your API key identifies and bills your account. Do not paste it into shared configs or commit it to a repository.

• Full details: Tegas Privacy Policy (RU: tegasai.ru/privacy-policy) and the terms of offer.

Docs and support

• Documentation: docs.tegas.ai

• Agent-oriented quick reference: docs.tegas.ai/quickstart.md (also served to agents as the MCP resource tegas://quickstart)

• OpenAPI schema: api.tegas.ai/v1/openapi.json

• Bugs in this metadata or in the MCP server: open an issue

License

The contents of this repository — documentation and metadata only — are released under the MIT License. The MIT license covers these files alone. It does not apply to the Tegas MCP server, the Tegas API, or the Tegas service, which are proprietary and governed by the terms of offer.