Content Tools
tegas.ai
An MCP server for managing a Tegas account and creating or editing multimedia content by uploading references, drawing heroes, and editing videos.
ENDPOINT 1
https://api.tegas.ai/mcp
MCP server metadata
- Name
- tegas
- Version
- 1.0.0
Tegas makes short AI videos (5-60 s) from an idea. Flow: tegas_account (balance, prices) -> tegas_write_scenario (optionally after tegas_upload_reference for a product/character photo) -> optional tegas_find_heroes/tegas_draw_heroes -> tegas_start_video with confirm=false to quote the price -> show the price to the user and get consent -> confirm=true -> tegas_wait_video. Paid tools never run without confirm=true. Once a video is completed, tegas_edit_video can change its scenes, voice, subtitles, music or volumes for free - it rebuilds the whole video (a few minutes), so tell the user what you are changing first, then wait again with tegas_wait_video; tegas_upload_music supplies a track for music.url. Read tegas://quickstart for details.
Known tools 12
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.tegas]
url = "https://api.tegas.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tegas": {
"type": "http",
"url": "https://api.tegas.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tegas
Remote MCP URL: https://api.tegas.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"tegas": {
"url": "https://api.tegas.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tegas": {
"type": "http",
"url": "https://api.tegas.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tegas",
"transport": "streamable-http",
"url": "https://api.tegas.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.