Kiridot MCP

Connect AI agents to Kiridot video creation.

Kiridot exposes a remote Model Context Protocol server for agents that need to create, manage, and inspect AI video workflows through a governed Kiridot account connection.

Connector URL

https://api.kiridot.com/mcp

Add this URL as a custom remote MCP connector in compatible agent clients. Kiridot uses Streamable HTTP and OAuth-backed workspace authorization, so each connected user works with their own Kiridot account, credits, media, and permissions.

Setup

Add Kiridot as a custom connector

Open your MCP client

Use a client that supports remote MCP connectors with OAuth.

Add a custom connector

Name it Kiridot and set the URL to https://api.kiridot.com/mcp.

Connect your account

Approve the requested scopes and let the agent list Kiridot tools.

Tools

Agent-native video workflows

AI Dance

Turn a subject image into a template-first dance video without exposing raw prompt controls.

Brand Campaigns

Store reusable brand memory and product truth, then pin each campaign to exact revisions.

UGC Campaign Workflow

Move from concepts to a reviewed storyboard and final video with confirmation at every paid stage.

Narrated & Cinematic Video

Create structured video projects that Kiridot can continue inside the app.

Captions & Dubbing

Start dynamic caption, voice-over, and translation dubbing jobs from uploaded media.

Durable Operations

Upload media directly, resume tasks, provide review input, cancel work, receive notifications, and retrieve final results.

Access

OAuth, scopes, and discovery

Kiridot MCP uses OAuth with scoped bearer tokens. Clients should discover authorization metadata from the protected-resource metadata document, send the canonical resource value throughout the OAuth flow, and request only the scopes needed for the workflow.

Protected resource metadata: https://api.kiridot.com/.well-known/oauth-protected-resource/mcp
Authorization server metadata: https://api.kiridot.com/.well-known/oauth-authorization-server or https://api.kiridot.com/.well-known/oauth-authorization-server/mcp
Token revocation: https://api.kiridot.com/mcp/oauth/revoke
Client registration: Client ID Metadata Documents preferred. Dynamic Client Registration is supported for fallback with application_type set to web or native; Kiridot accepts public clients only and issues refresh tokens by default unless a client registers a narrower grant set.

Permissions

Scopes

kiridot.read

Read workspace templates, jobs, and generated videos.

kiridot.media.write

Create direct upload URLs for media used by generation tools.

kiridot.generate

Create credit-consuming AI video generation jobs.

kiridot.billing.read

Read credit balance and compare it to proposed generation estimates.

kiridot.context.write

Create reusable brand, product, and campaign context with immutable revisions.

Governance

Operational safeguards

Paid tools require explicit confirmation and a stable idempotency key.
Campaign UGC pauses for concept selection and storyboard approval before later paid stages begin.
Brand snapshots and product and campaign revisions keep generation context reproducible.
Durable MCP Tasks support status, review input, cancellation, results, and task notifications.
Tool outputs use public API response shapes with signed media URLs.
AI Dance is template-first and does not accept agent-supplied prompts.
OAuth tokens are bearer-only, refreshable by default, resource-bound, and scoped to the MCP endpoint.
OAuth clients can revoke MCP access tokens when a user disconnects Kiridot.
Modern clients must send per-request MCP metadata headers and matching request _meta values.
The MCP transport validates browser Origin separately from Kiridot app CORS for hosted MCP clients.
Dynamic Client Registration supports web and native application types, with public clients only.
MCP responses are private/no-store at the HTTP layer; cacheable results still include ttlMs and cacheScope for clients.
Tool calls are audited for workspace, client, scope, latency, and credit reconciliation.

Support

Integration help

For MCP access, security reports, or integration questions, contact [email protected].