
Imanginable
com.imanginablePublished by imanginable.comOfficial publisherv0.4.308Updated Nov 7, 2026
Plan, render, fix and publish multi-scene AI videos: scripts, storyboards, cast, narration, YouTube.
Overview
Remote MCP server for planning, rendering, fixing and publishing multi-scene AI videos, from scripts and storyboards to narration and YouTube.
- What you can do
- Plan multi-scene AI videos, including scripts and storyboards
- Define cast and narration for scenes
- Render and fix video output
- Publish finished videos, including to YouTube
- No tool list is published, so exact commands are not documented
- When to use it
- Useful when you want an assistant to help produce AI-generated video end to end — drafting a script and storyboard, assembling scenes with narration, correcting renders, and publishing the result — rather than editing video by hand.
- Requirements
- A remote MCP endpoint reached over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. A browser-capable client is needed for the OAuth flow.
Installation
In SourceWeft
- Open Imanginable in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.imanginable%2Fimanginable/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"imanginable": {
"type": "http",
"url": "https://mcp.imanginable.com/mcp"
}
}
}Tools
0Version history
16- v0.4.308LatestNov 7, 2026
- v0.4.302Nov 4, 2026
- v0.4.298Nov 4, 2026
- v0.4.296Nov 4, 2026
- v0.4.293Nov 4, 2026
- v0.4.292Nov 3, 2026
- v0.4.288Nov 3, 2026
- v0.4.277Nov 1, 2026
- v0.4.272Nov 1, 2026
- v0.4.270Nov 1, 2026
- v0.4.269Oct 31, 2026
- v0.4.265Oct 31, 2026
- v0.4.263Oct 30, 2026
- v0.4.259Oct 30, 2026
- v0.4.257Oct 30, 2026
- v0.4.254Oct 29, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.