Treza MCP Server

Treza plugin

Agent Plugins package for the Treza MCP server. Install it in Cursor, Codex, GitHub Copilot, VS Code, or any client that supports the standard, and your agent can build, run, schedule, and publish AI video pipelines to YouTube and TikTok.

• Server: https://www.trezalabs.com/api/mcp (Streamable HTTP, OAuth with dynamic client registration)
• Landing page and setup snippets: https://www.trezalabs.com/connect
• Docs: https://docs.trezalabs.com/api/mcp-server
• Privacy: https://docs.trezalabs.com/terms-and-privacy/privacy

Two ways to connect

Remote (recommended). Point any client that supports OAuth at https://www.trezalabs.com/api/mcp. The first connection signs you in with Google and creates the Treza account. Nothing to install.

stdio bridge. For clients and agent runtimes that only spawn local servers, this repo ships treza-mcp, a small Node bridge that forwards every tool, prompt, and resource to the hosted endpoint. It needs a scoped API key in TREZA_API_KEY (mint one in the Treza app under Settings, API keys, or have an OAuth-connected client call create_api_key).

{
  "mcpServers": {
    "treza": {
      "command": "npx",
      "args": ["-y", "treza-mcp"],
      "env": { "TREZA_API_KEY": "treza_live_..." }
    }
  }
}

TREZA_MCP_URL overrides the endpoint (staging, self-hosted). The bridge runs nothing locally; it is a proxy.

What is inside

Tools

Twenty-four tools in five groups:

• Authoring: list_pipeline_templates, list_node_types, get_node_type, create_pipeline, update_pipeline, publish_pipeline
• Running: list_pipelines, get_pipeline, run_pipeline, get_run, list_runs, set_schedule_paused
• Your media: list_assets browses the media library, import_media adds a file (an attachment, a public link, or a local file sent through create_upload_url), assemble_video joins clips into one video with optional narration, a music bed, and burned-in captions, and edit_asset runs node operations (captions, upscale, trim, crop, and more) over a single file
• Channels and publishing: list_connected_channels, connect_channel returns a link that connects a YouTube channel or TikTok account in the person's own browser, and publish_asset lays a finished video out for review before it posts. confirm_publish belongs to the publish panel: it runs when the person presses Post there, never from the model
• Budget and access: estimate_run_cost, get_credit_balance, create_api_key (OAuth connections only)

Read-only tools carry readOnlyHint. run_pipeline, publish_pipeline, assemble_video, and edit_asset spend prepaid credits, and run_pipeline and publish_pipeline can post to a connected channel. assemble_video and edit_asset render in the background and return a run to poll with get_run.

In clients that show MCP Apps panels, such as ChatGPT and Claude, results appear as panels: the finished file, the price with a Start render button, a library to pick files from, a map of a pipeline, and the post before it goes out. Other clients get the same answers as text. Posting with publish_asset needs a panel; without one, publish through a pipeline that ends in a youtube-upload or tiktok-upload node.

Cursor without the plugin

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "treza": { "url": "https://www.trezalabs.com/api/mcp" }
  }
}

Runs spend prepaid credits on your Treza account. Agents with a wallet can top up over x402 with no human in the loop.

MIT licensed. Support: hello@trezalabs.com