Before you start
To use the Clueso MCP server, you’ll need:- An AI assistant that supports MCP servers, such as:
- ChatGPT
- Claude
- Claude Code
- OpenAI Codex CLI
- Gemini CLI
- Cursor
- VS Code (with GitHub Copilot or a compatible MCP extension)
- A Clueso account
The Clueso MCP server is available on all Clueso plans. Some tools — such as video export and advanced branding - require a paid plan.
Connect your AI assistant
- ChatGPT
- Claude
- Claude Code
- Codex
- Gemini CLI
- Cursor
- VS Code
This setup requires a ChatGPT paid plan (Plus, Pro, Team, Enterprise, or Edu). A paid ChatGPT plan is recommended for better outputs
- Open ChatGPT and go to Settings.
- Click Apps, then enable Developer Mode.
- Click Add (or Create) and enter the following URL: https://connect.clueso.io/mcp
- Name it
Cluesoand save. - A browser window will open — sign in to Clueso and click Allow to authorize.
- In the chat, click the + icon below the chatbox, hover over More, and select Developer mode to activate Clueso for that chat.
“Create a Clueso guide from this PPT, add a voiceover to each slide explaining the key point, and export it as a video.”
Verify the connection
After setup, confirm the Clueso MCP server is working:- Look for the Clueso tool in your AI assistant’s tools or connectors panel.
- Run a test prompt, for example:
“Show me my most recently updated Clueso project.”
- Your AI assistant should ask you to approve a tool call. Click Allow (or Approve) and wait for the response.
What you can do with Clueso MCP
Once connected, you can ask your AI assistant to:Create projects
“Create a new video called ‘How to reset your password’.”
Add voiceovers
“Add a voiceover to the first clip of my onboarding guide.”
Export videos
“Export my ‘Getting Started’ project as a video.”
Update articles
“Update the article in my ‘API Docs’ project with this new content.”
Tools available
Your AI assistant can call the following Clueso tools once connected. You don’t need to memorize them — just describe what you want and your assistant will pick the right ones. This list is provided as a reference for what’s possible.Find and browse
Two things
find reaches beyond your own workspace:
- Stock libraries. Media searches cover both your saved library and stock providers, and your assistant picks the library with
provider: Pexels for realistic photos and real-world footage (the default), Pixabay for illustrations, vectors, icons and motion graphics (narrowed withimage_typeorvideo_type), Clueso’s curated catalog for brand-safe music and sound effects, and Freesound for niche tracks and a vast sound-effect library. Scope the search withsource('org','stock', or'all'), and narrow stock results by orientation, color, size, or clip length. - The community clueprint library. Searching clueprints ranks matches across your workspace and the public community library, so your assistant can start from a template someone else published.
Projects
Clips
Elements (everything layered onto a clip)
Ten element types are available: text, callout, rectangle, arrow, image, video (picture-in-picture, b-roll or a background loop over an existing clip), animation, plus three built for demo footage — zoom, spotlight and blur (for masking sensitive data on screen).
For AI-generated visuals,
generate_media covers both directions: text-to-image (optionally steered by one of your workspace’s generation style presets, or grounded on a reference image) and prompt-to-animation, which can reuse a saved animation as its starting point and time itself against a voiceover script. Generation runs in the background — the element appears immediately and fills in once rendered.
Voiceover and audio
Generating speech re-times the clip to the length of the spoken audio. Ask for the voiceover before placing time-sensitive elements, or use
estimate_duration first, so your timings match the final length.Sync (for video clips with source recordings)
Articles
Recording
record_screen uses Clueso’s auto-recording agent, which requires a specific plan. If it isn’t part of your plan yet, reach out to our team — via the in-app chat, email, or your shared channel — or visit clueso.io/agents to explore it.Files and assets
There are three ways to get a file in, and your assistant picks whichever fits where the file lives:
- A file on your machine — Clueso returns an upload link and a one-line command; a coding assistant can run it for you.
- A file already on the web — pass the URL and Clueso fetches it directly, no interaction needed.
- Several files at once — Clueso returns a shareable upload page you open in your browser and drop files onto, then
check_uploadscollects them all.
Clueprints and design reference
Collaboration
Export
Exports run in the background — your assistant hands back straight away, and the finished video appears in the Exports tab of the editor.
Alongside these tools, the Clueso MCP server publishes reference material your assistant can pull in on demand — how to author a clueprint, how to write animation prompts, how sync points work, how generation styles steer images, and the full property schema for every element type. You don’t need to request these; the assistant reads them when relevant.
Combine tools for end-to-end workflows
The real power of Clueso MCP comes from chaining these tools together. Your AI assistant can call several tools in sequence to complete a full workflow — no manual hand-offs, no copying assets between tools. Just describe the outcome you want, and the assistant figures out which tools to call and in what order. A few examples:- “Turn this slide deck into a narrated explainer video.” Uploads the PPTX (
upload_file), creates a project (create_project), imports each slide as a clip (add_clipswithkind=pptx), generates AI narration per slide (voiceover_batch), then renders the final video (export_project). - “Build a product release video from this changelog.” Creates a project (
create_project), adds blank clips (add_clipswithkind=blank), drops in headlines and AI illustrations (add_elements,generate_media), generates a voiceover from the script (voiceover_batch), and exports it (export_project). - “Convert this Loom recording into a polished Clueso guide.” Uploads the recording (
upload_file), adds it as a clip (add_clipswithkind=video), detects steps automatically (auto_sync), layers titles and zoom callouts (add_elements), regenerates cleaner narration (voiceover_batch), and exports the result (export_project). - “Make five persona-specific versions of this video from our base template.” Reads the template’s design (
get_clueprint), spawns five copies of a base project (duplicate_project× 5), tweaks the voiceover script per persona (voiceover_batch), and exports all five (export_project). - “Repurpose this landscape explainer as a vertical short for Reels.” Clones the project (
duplicate_project), switches it to a 9:16 aspect ratio so elements reflow onto the portrait canvas (update_project), nudges any callouts that drift off-frame (update_elements), and exports the vertical cut (export_project). - “Refresh every onboarding video with our new brand colors.” Walks your workspace (
findwithtype=projects→get_project), updates each clip background and element style in place (update_clips,update_elements), and re-exports the affected videos (export_project).
Troubleshooting
The Clueso connector doesn't appear in my AI assistant
The Clueso connector doesn't appear in my AI assistant
- Make sure you’ve restarted your AI assistant after saving the configuration.
- For MCP server setups (Cursor, VS Code, and Claude code), verify Node.js 22.16+ is installed by running
node --version. - Check that the MCP server URL
https://connect.clueso.io/mcpis correct in your config file.
Tool calls time out or return errors
Tool calls time out or return errors
- Confirm your Clueso account is active and your workspace is accessible.
- Check your internet connection and any firewall rules that might block
connect.clueso.io. - Try removing and re-adding the MCP server, then re-authorizing.
MCP tools don't appear in Cursor or VS Code
MCP tools don't appear in Cursor or VS Code
- In Cursor, make sure you’re in Agent mode, not normal chat.
- In VS Code, make sure GitHub Copilot is active and you’re in an Agent chat (
@workspaceor the agent panel). - Restart the editor after any config changes.