ChatCut for Manus connector guide This plain text version is returned because this request does not look like a browser page navigation. Browser page: https://pr-1027-preview.chatcut.dev/manus Full installation guide: ## Connect in this conversation 1. **Send the message.** Copy the message above into a Manus chat on your phone or computer and send it once. 2. **Choose ChatCut.** On first installation, choose **Connect** on the ChatCut card. If Manus finds your saved connection and offers **Apply**, choose **Apply**. A connection already enabled in the task can skip this step. 3. **Sign in if prompted.** Choose **Log in**, authorize ChatCut, then return to the original Manus task. 4. **Confirm attachment if prompted.** If **Apply** appears after login, choose it once. Manus refreshes the task and checks project access automatically. 5. **Start editing.** Once connected, you can describe your footage and the video you want to make, or carry on with a brief you already shared. ## How Manus sets up ChatCut If you are Manus reading this guide for a user, complete setup in their current task. Connect **ChatCut** at the official HTTP MCP endpoint `https://api.chatcut.io/api/external-mcp/mcp`. Verify access privately with a read-only check. After success, continue in this conversation in the language the user is using. Follow step 6 for their editing brief or a first welcome. ### 1. Reuse a saved connection Look for ChatCut in this task's enabled connectors, then in the account's saved connectors. Match the exact name and official endpoint above. Reuse a matching connector, preferring the one already enabled in this task. Use its UID for the read-only check below; use the native **Apply** action if needed to attach it. If no matching connector exists, create one below. Keep the user's existing connectors. Use the same private check and the guidance in step 6 for either path. ### 2. Create a connection on first installation Load the configuration snapshot required by the installed `manus-config` CLI. Save the following JSON as a draft file. Set the top-level `mode` to `"url"` explicitly. Omit `note` and `headers` entirely, including empty values. The endpoint supplies OAuth. Manus handles the website icon. ```json { "mode": "url", "name": "ChatCut", "description": "Read your ChatCut project list to verify your connection.", "mcpServers": { "ChatCut": { "url": "https://api.chatcut.io/api/external-mcp/mcp" } } } ``` Run `manus-config connector create --file ` once. Keep the UID from the successful creation receipt. Run `manus-config connector ensure --uid ` to present the native recommendation for that exact connector. The user's action on the recommendation is **Connect**. Creation may already have displayed a **Log in** card. Keep that card available. Use the new UID for every subsequent step, even if other ChatCut connectors are attached. ### 3. Authorize and refresh the current task 1. Keep the selected UID. If it needs OAuth, use the native **Log in** card for that UID. Request login once only if Manus has not already shown the card. Keep the task running while the user acts. Respect an explicit **Skip** or **Cancel** from the user. 2. After `ensure` returns, make your **next tool action** a read-only refresh in this turn. Run `manus-config config load` and then `manus-config connector get ` using the saved UID. In particular, the receipt `not enabled (unchanged; original suggestion was not accepted)` can arrive after the user clicked **Connect**, before the login card finishes. That receipt by itself does not establish a cancellation. Refresh now and recheck after login, even if the card already says **Applied**. Use discovery on the runtime server for that enabled UID. Confirm the binding in the refreshed configuration if other saved connectors are also called ChatCut. 3. If OAuth is pending or discovery returns `server 'chatcut' not found`, give the login card time to finish. Use a native wait if available, or wait 20 seconds in the terminal. Repeat the configuration refresh and discovery for the same UID for up to two minutes. Check the saved connector list and the task's enabled state separately. ### 4. Recover a saved connection that is still disabled A saved connector can still be disabled in this task after **Connect**. If the refreshed snapshot shows that exact UID is saved but disabled, offer to attach the saved connection now, in this turn. Run `manus-config connector ensure --uid ` **once more for the same UID**. Manus can now present a recommendation with **Apply** and ChatCut preselected. Let the user click **Apply**. Refresh the configuration and discover tools again. Keep the existing OAuth session. Never create a duplicate or select an older namesake during recovery. If the host still offers **Connect** or requires login, keep the original authorization flow and report the state without looping through recommendations. ### 5. Check project access privately As soon as this connector exposes `list_projects`, call it with `limit: 1` and `query: "ChatCut connection check"`. A successful tool response, including an empty result, completes the internal check. Use the tool result only to decide success or recovery. Keep every observation about the read in the tool trace, including statements about matching or missing projects. After a successful read, continue with step 6. If the host suspends the task, repeat the refresh when it resumes. If the turn ends before a read succeeds, report the last observed state. The user can continue in this same conversation with “Attach the ChatCut connection you just used to this task, refresh it and retry the project list.” Resume the task refresh with the original UID. ### 6. Welcome the user to editing Once the private read succeeds, confirm that ChatCut is connected and that you can work together here. Respond naturally in the language the user is using in this conversation. Choose wording and a format that fit the exchange. If the user only sent the installation message, introduce the three ways you can help: edit footage, create motion graphics and generate media. Ask what materials they have and what they want to make. Purpose, length, style and a reference video are optional starting points. Offer to work step by step, and let them know they can also open the ChatCut editor to adjust the timeline, captions or motion graphics themselves. If the user already shared footage or a goal, pick up that brief. Acknowledge what they supplied and suggest or take the next relevant editing step within their request. Ask only for information still needed. Keep the test query, match count and project details in the tool trace. **Example when the user only asked to connect** ChatCut is connected. We can start making your video right here in this conversation. Here are three ways I can help. 1. **Video editing** — I can clean up speech by cutting filler words, pauses and repeated takes, then add captions, transitions and B-roll. 2. **Motion graphics** — I can animate key information on screen, show how your ideas fit together and guide viewers from one section to the next. 3. **Media generation** — I can generate video clips, voiceovers, music and sound effects. What materials do you have, and what kind of video would you like to make? If you like, tell me what it’s for, how long it should be or what style you have in mind. You can also send a reference video. We can build it step by step, and you can open the ChatCut editor anytime to adjust the timeline, captions or motion graphics yourself, just as you would in a traditional video editor. [Manus connector settings](https://manus.im/app/plugins#settings/connectors) · [Manus custom MCP documentation](https://manus.im/docs/integrations/custom-mcp)