Skip to content

Claude Code Integration

Claude Code Integration

Claude Code (and other MCP-enabled coding environments) can call AutoVio through the AutoVio MCP server.

Configure the MCP server

Claude Code needs to run the AutoVio MCP server as a command and connect over stdio. Use the same entry point and configuration pattern as in other MCP clients:

node /path/to/AutoVio-MCP/dist/index.js \
  --autovio-base-url http://localhost:3001 \
  --autovio-api-token YOUR_API_TOKEN \
  --vision-model gemini-2.0-flash-exp --vision-api-key YOUR_VISION_KEY \
  --llm-model gemini-2.5-flash --llm-api-key YOUR_LLM_KEY \
  --image-model gemini-2.5-flash-image --image-api-key YOUR_IMAGE_KEY \
  --video-model veo-3.0-generate-001 --video-api-key YOUR_VIDEO_KEY

Environment variables (AUTOVIO_BASE_URL, AUTOVIO_API_TOKEN, and the model/key envs) can also be used as described in MCP Setup.

Using tools from the editor

Once Claude Code is connected to the MCP server, it can:

List projects (autovio_projects_list) and works (autovio_works_list).
Create and update works (autovio_works_create, autovio_works_update).
Generate scenarios and scenes (autovio_works_generate_scenario, autovio_works_generate_scene).
Call direct AI tools (autovio_ai_analyze_video, autovio_ai_generate_scenario, autovio_ai_generate_image, autovio_ai_generate_video).

Use MCP Tools Reference for arguments and expected outputs, and Claude Code’s documentation for how to invoke MCP tools from within the editor.

See also