CapCut Codex plugin plus Sume hosted MCP in one session

You can run both in one Codex task as two separate tools. CapCut's plugin is a CapCut product; Sume is a remote MCP server at https://mcp.sume.com/mcp, which the docs say works in Codex among other clients. Neither page documents an integration between them, so plan on moving anything from Sume to CapCut as a file you hand over.

CapCut's page says the plugin is "now available outside the U.S." with a U.S. launch coming soon, and that it brings generation, drafting and detailed editing into a chat workflow. Sume facts are from Sume hosted MCP docs and MCP tools and gates, read 2026-09-30. The pages I read do not describe a connection between the two.

What does each side do?

How do Sume results get into the editor?

Ask Sume for the asset's download URL with assets_download_url (a read tool), fetch the file in your session, and give it to the CapCut plugin. CapCut's page says you can generate images and videos or upload an existing one, so an upload is the path CapCut's page describes. Whether the plugin can take a URL directly is not stated there, so check before relying on it.

Why can't Sume read my local clip?

The docs say "Hosted MCP cannot read files from your laptop." The route for a local file is: create an upload URL, have the client PUT the bytes, then call assets_complete. Our guide on uploading a local file over MCP walks through it. If CapCut produced the edit, upload the export that way before asking Sume to caption or extend it.

What happens when the agent calls a paid tool?

Paid writes such as generate_video need an idempotency_key. Long video jobs take time, so wait with jobs_wait rather than resubmitting; see MCP jobs_wait for long video jobs. For the broader question see can Codex make videos.