Vidmoat
Voting openAI video editor your agents can drive over MCP
From the maker
Hosted AI video editor with an MCP server: agents import footage, run 65+ timeline commands, preview frames and render MP4s. Browser and Telegram too. MCP endpoint (Streamable HTTP, OAuth/API key): https://api.vidmoat.com/api/mcp. Setup: claude mcp add --transport http vidmoat https://api.vidmoat.com/api/mcp. Registry name com.vidmoat/vidmoat. Example tools: list_projects, create_project, import_media, edit_project, preview_frame, render_project, transcribe. Free Hobby plan; paid plans from $19/month.
How to connect
Streamable HTTP endpoint:
https://api.vidmoat.com/api/mcp
What happened when we asked
We asked on 15 October 2026 and it challenged us for credentials. That is a working server guarding itself: it answered, and it wants an account we do not hold. A tool count and a response time come from a tools/list we were never served, so this listing carries neither.
How it asks you to sign in
Its refusal named a public document describing how to authenticate, which is what the MCP authorization spec asks a guarded server to publish. We read that document on 15 October 2026. Everything below is what it says; we have still not been inside this server.
- It calls itself
- Vidmoat MCP
- Sign in through
- api.vidmoat.com
- Token accepted in
- header
- Its own docs
- https://www.vidmoat.com/mcp
- Read
- 2026-10-15 10:22 UTC
The 18 permissions it declares
These are the scopes the document lists, verbatim. They describe what an account can grant this server, not what it will do with the grant, and we have not audited either.
- account.read
- projects.read
- projects.write
- media.read
- media.write
- render.read
- render.write
- ai.transcribe
- ai.speech
- ai.image
- ai.video
- ai.agent
- ai.analyze
- stock.read
- webhooks.manage
- plugins.invoke
- telegram.users.read
- telegram.users.write
Anything above describes one moment on the date shown. We do not re-test on a schedule, so nothing here says what this server is doing now. We have not audited its code, its data handling or its permissions, and this is not a safety rating.
Comments
What readers said about this product. Comments are people's own opinions and are not part of anything we checked.
Sign in to comment. Same account that votes.
Comments are written by readers, not by us, and we do not endorse them. Nothing here is held back or approved first: a comment goes up when it is posted, and you can edit or delete your own at any time. Report anything illegal or abusive with the link on each comment, or by email from our contact page if you do not have an account.