ChatCut for Muse connector guide This plain text version is returned because this request does not look like a browser page navigation. Browser page: https://pr-933-preview.chatcut.dev/muse Full installation guide: Send this message to Muse, Meta's personal AI agent, on your phone or computer: ```text Read ChatCut.io/muse to connect ChatCut ``` Muse adds ChatCut, asks you to sign in to ChatCut, then saves the ChatCut skill and checks the connection. Nothing is installed on your phone or computer: ChatCut runs through Muse's own cloud computer. You need a ChatCut account, and you can create one when you sign in. ## Or add it in Settings ChatCut is not in Muse's connector directory yet, so it is added as a custom connector. 1. In Muse, open **Settings → Connectors** and tap **Add custom connector**. 2. Enter the name `ChatCut` and this URL: ```text https://api.chatcut.io/api/external-mcp/mcp ``` 3. Save. When the ChatCut sign-in page opens, sign in to ChatCut and allow access. Use the URL exactly as shown, with nothing added to it. Sign-in uses OAuth, so there is no API key or header to enter. Then send Muse the message above so it also saves the ChatCut skill. Some versions of Muse may not show **Add custom connector** yet; if you don't see it, use the message instead. ## Things to ask Muse Once ChatCut is connected, try: - "Use ChatCut to turn the 5 clips from my bakery into a 30-second vertical 9:16 Reel with captions." - "Use ChatCut to cut my 10-minute talking video into three 45-second vertical clips with captions, and remove the filler words." - "Use ChatCut to trim my product demo to the best 20 seconds, add bold captions, and send me the 1080p MP4 here." Attach the videos in the chat. If an attachment does not come through, Muse gives you a ChatCut upload link that works in your phone's browser. Muse opens your project in a browser on its cloud computer, which ChatCut signs in for you, and sends the finished video back in the chat. Your projects are saved to your ChatCut account, so you can also keep editing them at app.chatcut.io. AI generation and cloud exports use the credits on your ChatCut account. ## For Muse: connect ChatCut If you are Muse reading this page for a user, set ChatCut up now; do not only describe the steps. This page applies to Muse with its own cloud computer. If you are another assistant, tell the user that this page is for Muse and stop. This setup adds ChatCut as a custom connector and saves one private skill. Keep the user's other connectors, skills and ChatCut projects. Do not 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 connector named `ChatCut` or `chatcut`. - If one exists and its tools answer, reuse it and go to step 4. - If ChatCut now appears in Muse's connector directory, add it from there instead of a custom connector, then go to step 4. - If a ChatCut connector exists but is disconnected, go to step 3. ### 2. Add ChatCut as a custom connector Use your native operation for adding a custom remote MCP connector by URL: ```text Name: ChatCut URL: https://api.chatcut.io/api/external-mcp/mcp Auth: OAuth ``` Use the URL exactly, with no query parameters and no extra headers. ChatCut recognizes Muse from its own OAuth sign-in. Do not add an `Authorization` header, an API key or a token. If Muse shows the name and URL and asks the user to confirm, tell the user to approve it. ### 3. Have the user authorize ChatCut Tell the user, in their language: > Open the ChatCut sign-in page, 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 authorization fails, remove the connector once and add it again. If it fails again, report the exact error and stop. Authorization is finished only when the ChatCut tools are listed. An anonymous HTTP 401 from the URL is expected before sign-in and is not success. ### 4. Check the connection with one read Call the ChatCut `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 The connector brings ChatCut's tools but not its workflow guides. Install them in two parts. First, put the latest 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/refs/heads/main | tar -xz -C ~/.chatcut ls ~/.chatcut/agent-plugin-main/grok/skills/*/SKILL.md | wc -l ``` The last command prints the number of guides (19 today); any number above zero means the download worked. If the download is blocked, say so and continue: the skill below falls back to reading the same files from GitHub. Then save the text between the two `chatcut-muse-skill` markers below, exactly, so it applies to later conversations: - If you can save a skill, save it as a private skill named `chatcut` with the description `Use for any ChatCut request in Muse: creating or editing ChatCut video projects, importing media, transcripts and captions, motion graphics, AI video, image, voice and music generation, and export.` - Otherwise, save the same text to your memory (for example your Memory.md). If a skill or memory entry named `chatcut` already exists, read it first. Replace it only if it starts with a `chatcut-muse-skill` marker; otherwise keep it, tell the user about the conflict, and save this one as `chatcut-muse` instead. Read the saved text back and confirm it matches. If you can save neither, tell the user that ChatCut's tools are connected but its skill could not be saved. ```markdown # ChatCut in Muse ChatCut's tools come from the custom connector named `ChatCut` (`chatcut` in older setups). The full ChatCut workflow guides are on your computer at `~/.chatcut/agent-plugin-main/grok/skills/`. They were written for Grok Bot, another agent with its own cloud computer: where they say Grok Bot, read Muse, and where they name Grok Bot's settings, use Muse's **Settings → Connectors**. 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` - checking frames, comparing shots or locating visual changes: `visual-analysis` - 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/refs/heads/main | tar -xz -C ~/.chatcut`. If that fails, read the same files from `https://raw.githubusercontent.com/ChatCut-Inc/agent-plugin/main/grok/skills//SKILL.md`. 4. Bring in the user's media from their attachments first, following `asset-import`. 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. When a ChatCut result includes a `Host browser handoff` line (`browserHandoff.url`), open that URL once in your own browser on your cloud computer and keep the tab open for previews and exports. It signs that browser in to the user's ChatCut account. Never show that URL to the user, and never ask them for a ChatCut sign-in code. 6. Export with `submit_export` as the `export` guide says. When it reports `delivery: host`, the file is uploaded for you: once `track_export` shows it ready, download `delivery.downloadUrl` with `curl -fL` and send the file to the user in this conversation. Without `delivery: host`, the file downloads inside your own browser, not on the user's device; if you cannot send it from there, offer a cloud export with its quote, then send the file from `track_export`'s `downloadUrl`. 7. If ChatCut tools are missing or report an authorization error, ask the user to reconnect ChatCut in **Settings → Connectors**. Never ask for passwords or codes. 8. Paid generation and cloud exports use the user's ChatCut credits. Confirm the choices and the cost with the user before starting them. ``` ### 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 the examples from "Things to ask Muse" above. On a phone, add: attach the videos here; if an attachment does not come through, ask for a ChatCut upload link and open it in the phone's browser. ## Troubleshooting - **The sign-in page doesn't open, or ChatCut shows as disconnected.** In Muse, open **Settings → Connectors**, reconnect ChatCut and sign in again. - **Muse asks you for a ChatCut sign-in code.** Don't send it. Ask Muse to read chatcut.io/muse again: ChatCut gives Muse a link that signs its own browser in. - **Opening the URL shows HTTP 401.** That is expected before sign-in. The connector works once you authorize it on the ChatCut sign-in page. - **There is no Add custom connector button.** Send Muse the message at the top of this page instead. To update ChatCut's guides later, send Muse the message at the top of this page again: it downloads the latest package and replaces the skill. To disconnect, remove ChatCut in **Settings → Connectors**, and delete the `chatcut` skill or memory entry if it is no longer wanted. Review ChatCut's [Privacy Policy](https://pr-933-preview.chatcut.dev/privacy) and [Terms of Service](https://pr-933-preview.chatcut.dev/terms).