ChatCut for Grok Bot install guide This plain text version is returned because this request does not look like a browser page navigation. Browser page: https://chatcut.io/grok Full installation guide: Send this message to Grok Bot, on your computer or in the iPhone or Android app: > Read ChatCut.io/grok to connect the ChatCut app Grok Bot connects ChatCut, asks you to tap **Authorize** and sign in to ChatCut, then saves the ChatCut skill and checks the connection. Nothing is installed on your phone or computer: ChatCut runs through Grok Bot's cloud computer. You need a Grok Bot plan and a ChatCut account. ## For Grok Bot: connect ChatCut If you are Grok Bot reading this page for a user, set ChatCut up now; do not only describe the steps. This page applies to the Grok Bot app with its own cloud computer. If you are Grok on grok.com, X or the Grok app instead, tell the user that this page is for Grok Bot and stop. ChatCut is not yet listed in Connect apps, so this setup adds it as a custom remote MCP server and saves one private skill. Keep the user's existing apps, skills and ChatCut projects. Do not install ChatCut Desktop, create an empty project, or start paid generation as part of setup. Work through these steps in order and tell the user briefly what you are doing at each one. ### 1. Reuse a working connection Check whether this account already has a ChatCut connection: a verified ChatCut app in Connect apps, or a custom MCP server named `chatcut` or `ChatCut`. - If one exists and its tools answer, reuse it and go to step 4. - If a verified **ChatCut** app now appears in the Connect apps catalog, add it with its normal Add and Authorize flow instead of a custom server, then go to step 4. - If a ChatCut server exists but needs authorization, go to step 3. ### 2. Add ChatCut as a custom MCP server Use your native operation for adding a custom MCP server by URL (remote HTTPS), not a command server, and inspect its current fields first. Ask for a **custom server** by name so the host does not substitute a catalog plugin. ```text Name: ChatCut URL: https://api.chatcut.io/api/external-mcp/mcp Header: x-chatcut-mcp-client: grok ``` If the operation cannot store headers, use this URL instead and no header: ```text https://api.chatcut.io/api/external-mcp/mcp?chatcutMcpClient=grok ``` The header only tells ChatCut the calls come from Grok Bot; it is not a credential. Do not add an `Authorization` header, an API key or a token: the server uses OAuth. It is a public HTTPS server, so it should not need private-network or certificate approval. The host may show the name and URL and ask the user to confirm; tell the user to approve it. ### 3. Have the user authorize ChatCut The host posts a connect card for ChatCut. Tell the user, in their language: > Tap **Authorize** on the ChatCut card. A ChatCut sign-in page opens (on iPhone > it can open inside the Grok Bot app). Sign in to your ChatCut account, or create > one, and allow access. Then come back here and say "done". - Never ask for a password, a one-time code or a cookie in chat, and do not sign in on the user's behalf in your computer's browser. - If the card stays on **Waiting for authorization**, ask the user to tap **Reopen** on the card, or **Reconnect** on ChatCut in Connect apps. - If authorization fails before the sign-in page with a redirect or resource error, remove the server once and add it again with the other form from step 2 (headers instead of URL parameters, or the reverse). If it fails again, report the exact error and stop. Authorization is finished only when the `chatcut` server reports its tools. An anonymous HTTP 401 from the URL is expected before OAuth and is not success. ### 4. Check the connection with one read Call the `chatcut` server's `list_projects` tool once, using its live schema. An empty list is a valid result. Do not create, copy or edit a project to prove the installation. ### 5. Save the ChatCut skill Connecting by URL brings ChatCut's tools but not its workflow guides. Install them in two parts. First, put the pinned ChatCut package on your computer. It contains the workflow guides and the import helpers they run: ```sh mkdir -p ~/.chatcut curl -fsSL https://codeload.github.com/ChatCut-Inc/agent-plugin/tar.gz/c9be51d7a93302f02923c1d4950d7327c01a4f5f | tar -xz -C ~/.chatcut ls ~/.chatcut/agent-plugin-c9be51d7a93302f02923c1d4950d7327c01a4f5f/grok/skills/*/SKILL.md | wc -l ``` The last command prints `18`. If the download is blocked, say so and continue: the skill below falls back to reading the same files from GitHub. Then save one private skill with your native skill operation (create or update a skill with a name, description and Markdown body; inspect its current schema). - **Name:** `chatcut` - **Description:** `Use for any ChatCut request in Grok Bot: creating or editing ChatCut video projects, importing media, transcripts and captions, motion graphics, AI video, image, voice and music generation, and export.` - **Body:** the text between the two `chatcut-grok-skill` markers below, exactly. If a private skill named `chatcut` already exists, read it first. Replace it only if its body starts with a `chatcut-grok-skill` marker; otherwise keep it, tell the user about the conflict, and save this one as `chatcut-grok` instead. Load the saved skill by name and confirm its body matches. If this host has no native skill operation, tell the user that ChatCut's tools are connected but its skill could not be saved, and keep the package from the first part for reference. ```markdown # ChatCut in Grok Bot ChatCut's tools come from the custom MCP server named `ChatCut` (`chatcut` in older setups). The full ChatCut workflow guides are on your computer at `~/.chatcut/agent-plugin-c9be51d7a93302f02923c1d4950d7327c01a4f5f/grok/skills/`. 1. Before the first ChatCut tool call in a conversation, read `chatcut-plugin-basics/SKILL.md` in that folder and follow it. 2. Before each workflow, read its guide in the same folder, including the files it links to, and follow it: - importing or relinking media: `asset-import` - exporting or delivering a finished video: `export` - speech-led edits such as talking-head, interview, podcast or tutorial cleanup: `talking-head-guide` - transcripts, captions and subtitles: `transcription` - motion graphics, titles and animated overlays: `create-motion-graphics` - video effects, transitions, masks and color: `shader-gen` - AI video generation: `video-gen` - voiceover, text-to-speech, voice cloning and sound effects: `voice` - music and songs: `music` - AI avatar presenters: `digital-human` - lip sync to supplied audio: `lipsync` - translating or dubbing a video: `video-translation` - syncing several cameras or recorders: `multicam-sync` - asking the user to choose, or showing previews: `widget-forms` - checking that an edit is visible in the editor: `verification` - tool errors and blocked operations: `known-errors` - questions about ChatCut itself, plans or credits: `product-help` 3. If that folder is missing, download it again: `mkdir -p ~/.chatcut && curl -fsSL https://codeload.github.com/ChatCut-Inc/agent-plugin/tar.gz/c9be51d7a93302f02923c1d4950d7327c01a4f5f | tar -xz -C ~/.chatcut`. If that fails, read the same files from `https://raw.githubusercontent.com/ChatCut-Inc/agent-plugin/c9be51d7a93302f02923c1d4950d7327c01a4f5f/grok/skills//SKILL.md`. 4. Bring in the user's media from their attachments first, following `asset-import`; a photo or video attached from a phone works the same way. Only if there is no attachment you can read (the file is still only on their phone, it never reached your computer, or the import fails), call `import_media` with `{"action":"create_session"}` and give the user its `userUploadFallback.url`: a ChatCut upload page that works in a phone browser. 5. If ChatCut tools are missing or report an authorization error, ask the user to tap **Reconnect** on ChatCut in Connect apps, or **Reopen** on the in-chat card. Never ask for passwords or codes. 6. Paid generation uses the user's ChatCut credits. Confirm the choices and the cost with the user before starting it. ``` ### 6. Tell the user it is ready Report, in the user's language: ChatCut is connected to their ChatCut account, the read check succeeded, and the `chatcut` skill was saved (or which part could not be completed). Then offer two or three things they can say next, for example: - "Use ChatCut to turn the video I'm attaching into a 30-second vertical clip with captions." - "Make a 10-second animated title for my channel in ChatCut." - "Clean up the pauses and filler words in this interview, then export it." On a phone, add: to bring in a video from the phone, attach it here. If the attachment does not come through, ask for a ChatCut upload link and open it in the phone's browser. ## Notes - To disconnect, remove ChatCut in Connect apps (or the `chatcut` custom server), and delete the `chatcut` private skill if it is no longer wanted. - ChatCut projects stay editable in the ChatCut editor at app.chatcut.io; every change the Bot makes can be adjusted by hand. - Review ChatCut's [Privacy Policy](https://chatcut.io/privacy) and [Terms of Service](https://chatcut.io/terms).