CONNECT TO CHUCKSI

Connect with MCP

Let a compatible assistant discover Chucksi tools and prepare a studio workflow.

Server address

https://console.chucksi.com/mcp

Transport: Streamable HTTP. Authentication: none for public discovery. Add this URL in your client’s remote MCP server settings. This is a live MCP server, not a normal web page.

Claude Code

claude mcp add --transport http chucksi https://console.chucksi.com/mcp
claude mcp list

Clients using an mcpServers configuration

{
  "mcpServers": {
    "chucksi": {
      "url": "https://console.chucksi.com/mcp"
    }
  }
}

Configuration names and remote-server support vary by client. Use its documented HTTP connection flow; do not select legacy SSE or add /sse. There is no Chucksi marketplace plugin or OAuth account connection in this release.

Available tools

Tool	What it returns
get_help	Connection details, supported actions and limits.
list_tools / get_tool	Studio features, inputs, outputs and links.
list_presets / get_preset	Video effects and camera moves, with exact settings.
list_workflows / get_workflow	Workflow recipes with ordered studio steps.

List tools accept optional q and category. Detail tools require an exact id. The older list_templates and get_template tools remain for compatibility with Website integrations; browsing and editing those designs belongs in Website Studio.

What happens next

Ask your assistant to find the right effect or workflow, then open the returned studio link. These calls read public recipes. They do not upload your files, render media, access your library or publish websites.