creativai-mcp

MCP (Model Context Protocol) server for the CreativAI Video Intelligence Platform.

Connect any MCP-compatible AI assistant (Claude, Cursor, VS Code Copilot, etc.) directly to your CreativAI video library — search, index, extract knowledge, manage collections, run live streams, import from YouTube, and more — all through natural language.

Installation

pip install creativai-mcp

Quick Start

export CREATIVAI_API_KEY=YOUR_API_KEY
creativai-mcp

Or put api_key=YOUR_API_KEY in ~/.creativai/config. Don't pass the key as --api-key: other users of the same machine can read command-line arguments from the process list, so that flag is deprecated.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "creativai": {
      "command": "creativai-mcp",
      "env": { "CREATIVAI_API_KEY": "YOUR_API_KEY" }
    }
  }
}

VS Code / GitHub Copilot

Add to your VS Code settings.json:

{
  "mcp": {
    "servers": {
      "creativai": {
        "type": "stdio",
        "command": "creativai-mcp",
        "env": { "CREATIVAI_API_KEY": "YOUR_API_KEY" }
      }
    }
  }
}

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "creativai": {
      "command": "creativai-mcp",
      "env": { "CREATIVAI_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Hosted by CreativAI (no install)

Web agents — claude.ai custom connectors, Replit Agent, the Claude API's MCP connector — and any client that speaks MCP over streamable HTTP can use the server CreativAI runs, at https://ws.creativai-apis.com/api/v2/mcp. Send your own API key on every request as X-API-Key: YOUR_API_KEY (or Authorization: Bearer YOUR_API_KEY). The hosted server follows the hosting rules below: no delete_* tools and no blocking helpers.

Available Tools

Collections

Media

Search

Indexing

Agentic Chat

Data Plates

Knowledge Extraction

Live Stream

Online Search (Web Video Import)

YouTube

Organizations & Projects

Tasks

Account & Users

Transports

stdio (default — for desktop AI clients). The server uses one key, from CREATIVAI_API_KEY or ~/.creativai/config (or the deprecated --api-key):

CREATIVAI_API_KEY=YOUR_API_KEY creativai-mcp --transport stdio

Streamable HTTP (for hosting — claude.ai custom connectors, Replit Agent, the Claude API MCP connector, other web agents):

creativai-mcp --transport streamable-http --host 0.0.0.0 --port 8090

The MCP endpoint is http://<host>:8090/mcp. SSE (--transport sse, endpoint /sse) is also available for older clients and follows the same rules.

Hosting rules

• Every request brings its caller's own key, as X-API-Key: <key> or Authorization: Bearer <key>, and runs against that caller's account. Requests without a key get 401. The server never uses a key of its own: --api-key and CREATIVAI_API_KEY are ignored on the HTTP transports.
• Not available when hosted: delete_collection, delete_media, delete_data_plate, delete_chat_session (irreversible — delete from the website) and the blocking helpers index_and_wait and search_and_import (they can hold a request for minutes). Agents poll start_indexing → get_indexing_status and start_online_search → get_online_search_status → list_online_search_candidates instead.
• Stateless: run as many replicas as you like behind a load balancer; no sticky sessions needed.
• Bind to 0.0.0.0 (or the pod IP). On 127.0.0.1 the server accepts only Host: localhost requests (DNS-rebinding protection), which breaks behind a reverse proxy.
• Serve it over HTTPS at a public URL, terminating TLS at the load balancer. Web agents connect from their own cloud, not from the user's machine.
• GET /healthz returns 200 ok without a key, for load-balancer health checks.
• Point it at a non-production API with --base-url or CREATIVAI_BASE_URL.

Requirements

• Python 3.10+
• A CreativAI API key — get one at creativ-ai.com

License

Proprietary — © CreativAI