# Colossyan MCP connector The Colossyan connector lets Claude, ChatGPT, Cursor and the Elaichi Agent turn scripts and source documents into avatar videos, pick actors and voices, and check on render jobs, all inside each person's own Colossyan access. Source: https://elaichi.ai/connectors/colossyan/ ## Facts | | | | --- | --- | | Application | Colossyan | | Category | Video | | AI tools | 10 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Colossyan is connected - List Colossyan generation jobs created this week - Which Colossyan actors and voices does onboarding use? - Draft a Colossyan video from this policy document ## Connect Colossyan in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Colossyan. 2. Optionally set Share with, then press Connect. 3. Paste a Colossyan API key. One person generates a token in Colossyan and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Colossyan tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Colossyan to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Colossyan to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Colossyan to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Colossyan to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Colossyan tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Colossyan through Elaichi ### Turn a policy document into a training video Learning and development. Paste the new expenses policy and ask for a draft script, then send it to Colossyan as a video job with the presenter your team usually uses. Check back when the render is done and grab the finished video. ### Refresh onboarding videos when the process changes HR. When the first-week checklist changes, ask for an updated draft from the new document and start a fresh Colossyan render from an existing template, so new hires never watch an out-of-date walkthrough. ### Produce a product update video in several voices Marketing. List the Colossyan voices available to you, pick one per market, and queue a video job for each so the same announcement goes out in a voice that fits each region. ### Build a quick pitch explainer from a one-pager Sales enablement. Drop the one-pager into the conversation, get a draft script, and start a Colossyan render from your standard pitch template. Follow the job by its ID until the video is ready to share with reps. ### Make a how-to video for a recurring ticket Support. Take the answer your team keeps writing out and ask for a short Colossyan video of it, choosing an actor from your account. Delete the old version once the new one is generated so the help center stays tidy. ### Keep the render queue clean Internal communications. Ask which Colossyan video jobs are still running, cancel the one that was started with the wrong script, and remove generated videos that were only test runs. ## Frequently asked questions ### How do I connect Colossyan to Claude? First, add Colossyan in Elaichi. Colossyan connects with an API key, so you copy the key from your Colossyan account and paste it into Elaichi; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Colossyan appears in Claude. ### Does Colossyan work with ChatGPT and Cursor as well as Claude? Yes. Once Colossyan is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Colossyan once and every client you use picks it up. ### What can an AI agent actually do with my Colossyan account? With Colossyan connected, an agent can look up the actors and voices in your account, add a new actor, and start a video render either from scratch or from one of your templates. It can also turn a document or set of notes into a draft script, check how a render job is going, fetch the finished video, and delete jobs or generated videos you no longer need. ### Does connecting Colossyan give the AI access to everything in my workspace? No. Everything the agent does in Colossyan runs under the API key of the person who connected it, so it can only reach the actors, voices, templates and videos that key already allows. Elaichi can narrow that further, for example to creating drafts and videos but not deleting them, and it can never widen access beyond what Colossyan itself permits. ### Can my team share one Colossyan connection? Yes. One person connects Colossyan in Elaichi and shares it with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who started a Colossyan render or deleted a video. ### Can I stop an agent from deleting videos or jobs in Colossyan? Yes. In Elaichi you can restrict individual actions on the Colossyan connector, such as deleting generated videos or canceling render jobs, while leaving drafting and video creation available. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it. ### What happens to a Colossyan connection when someone leaves the company? When you offboard someone in Elaichi, their access to Colossyan through every AI client ends at once. If they were using a shared Colossyan connection, it keeps working for everyone else on the team. If you want Colossyan gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time. ## All 10 Colossyan tools Every tool below is callable through https://api.elaichi.ai/mcp once Colossyan is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Colossyan assets actors** (List). List avatars available in your Colossyan workspace. Returns each avatar with id, name, display_name, preview_url, version, type, gender, default_voice, views, features, and other attributes. - **Create a Colossyan assets actor** (Create). Create a new avatar in Colossyan. Returns: name. - **List all Colossyan assets voices** (List). List voices available to the workspace in Colossyan. Returns each voice record with id and voice-specific attributes. - **Create a Colossyan video generation jobs template job** (Create). Create a Colossyan video generation job from a saved template. Returns: id, videoId. Required: templateJobId and the template-specific generation payload. - **Create a Colossyan video generation job** (Create). Create a new Colossyan video generation job. Returns the queued job identifier and provisioned video id. Required: a JSON request body shaped by Colossyan's VideoGenerationJob schema. - **Get single Colossyan video generation job by ID** (Get). Get the status and progress of a Colossyan video generation job by id. Returns: status, videoId, progress, maximumProgress. Required: id. - **Delete a Colossyan video generation job by ID** (Delete). Delete a Colossyan video generation job by id and stop any ongoing processing. Returns an empty 204 response on success. Required: id. - **Get single Colossyan generated video by ID** (Get). Get a generated video from Colossyan by id. Returns: id, jobId, publicUrl, thumbnailUrl, name, createdAt, videoSizeBytes, videoDurationSeconds. Required: id. - **Delete a Colossyan generated video by ID** (Delete). Delete a generated video from Colossyan by id. Returns the deleted video record including id, publicUrl, thumbnailUrl, createdAt, name, jobId, videoSizeBytes, and videoDurationSeconds. Required: id. - **Create a Colossyan knowledge to draft generate draft** (Create). Generate a draft in Colossyan from structured textual data. Returns: url. Requires a request body. Required: summary.