Create and manage AI-generated videos with Reelsmith.video through MCP-compatible AI agents. Upload video projects, select editing and caption styles, start video processing, track rendering status, and retrieve finished videos
Visual Studio Code runs MCP servers for Copilot Chat in agent mode, so the model can use external tools while it works on your code.
This guide connects Reelsmith MCP to VS Code through MewCP, so VS Code can use Reelsmith MCP's 8 tools, like reelsmith_create_video, reelsmith_create_music_upload and reelsmith_list_styles, without your Reelsmith MCP credentials ever reaching the app.
Your Reelsmith MCP API key is stored encrypted and injected only at call time. Your agent never holds it, so it can never leak it, log it or paste it into a prompt.
More apps
Manage YouTube content including videos, channels, playlists and creator operations. Search content, organize media, publish updates and interact with YouTube resources programmatically.
Turn your AI agent into a creative studio The world's best image, video, audio and 3D models, inside the AI assistant you already use.
Meta Ads connects AI agents to Facebook and Instagram advertising accounts to analyze campaign performance, create and edit campaigns, ad sets and creatives, manage custom audiences and product catalogs, inspect conversion tracking signals, run A/B tests, and investigate advertising issues.
Give AI coding agents access to a curated library of real-world website designs, screenshots, design systems, and reusable UI components. Search visual references, find similar designs, analyze layouts, extract colors and typography, compare websites, and retrieve copy-ready JSX components for building better interfaces
Other clients
Reelsmith MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Reelsmith MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
A browser window opens the first time the client connects. Sign in and approve access. No API key needed.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
Create a video project and get a presigned upload URL. Upload the source file to upload.url (HTTP PUT), then call reelsmith_finalize_video to start processing. For editingStyle=BEAT_SYNC (b-roll cut to the caller's own song), first call reelsmith_create_music_upload, PUT the song, and pass its key as musicKey plus a one-line brief.
BEAT_SYNC only: get a presigned PUT URL for the caller's own song (MP3, M4A/AAC, WAV, OGG, FLAC; up to 50 MB). PUT the file, then pass the returned key as musicKey to reelsmith_create_video.
List the editing styles you can pass as editingStyle, each with an outcome + best-for hint.
List the caption styles you can pass as captionStyle, each with a label + description.
List the Motion Library FX Packs you can pass as graphicsPack, each with its voice, default styles and elements.
Confirm the upload and start processing (analysis then render).
Get a video's status (DRAFT, ANALYZING, RENDERING, READY, FAILED) and, when READY, its rendered outputs with playback + download URLs.
List the workspace's videos (most recent first).
