
Longtake
io.github.svatrousPublished by GitHub account svatrousv1.0.2Updated Oct 24, 2026
Drive Longtake Studio from an agent: AI video takes on your own API key, characters, drafts, costs
Overview
Drives Longtake Studio from an agent: set up productions, cast characters, shoot AI video takes on your own provider keys, and read back render costs.
- What you can do
- Survey projects, episodes, scenes, characters and assets across the studio
- Create the production structure (projects, folders, scenes) and cast characters with portraits and locked voice samples
- Generate four-view character sheets and upload reference images, audio and video clips
- Estimate the cost of a take, then shoot it with named characters and assets, optionally as a cheap draft
- Finish drafts in 1080p, check take status and spend, list scene takes, and cancel or delete takes
- When to use it
- Useful when you want an assistant to plan and produce AI video in Longtake Studio — building a production, casting characters, drafting and finishing takes — and to see the price of each render before committing.
- Requirements
- Runs locally over stdio via npx from the npm package longtake-mcp (Node.js). Needs a studio address in STUDIO_URL and a personal agent token in STUDIO_TOKEN, created in the studio under API keys → Agent access. The token is sent over HTTPS, or plain HTTP only to a studio on localhost.
Installation
In SourceWeft
- Open Longtake in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
longtake-mcp
MCP server for Longtake Studio — an AI video studio that runs on your own API key. With this server an AI agent (Claude Code, Codex, Cursor, any MCP client) can set up a production, cast characters with a locked voice, shoot takes on Seedance 2.0 / 2.5, Veo 3.1, Gemini Omni or Kling 3.0, draft cheaply and finish in 1080p, and read back the cost of every render.
Renders launched by an agent are billed exactly like clicks in the studio: the model provider (BytePlus, Google, Kling, fal.ai) charges your own key at its list price. Agent access itself is neither metered nor marked up.
Longtake is the name of the software. It is not the cinematography term "long take" — though that is where the name comes from: one take of one scene is the unit of work.
What the agent gets — 13 tools
Setup
-
Issue a token. In the studio: account menu → API keys → Agent access — MCP → create. It is shown once and can be revoked alone.
-
Register it with your agent. The package is on npm as
longtake-mcp, sonpxfetches it — nothing to clone. For Claude Code:Any other MCP client takes the same command and the same two environment variables. As JSON (Cursor, Codex, Claude Desktop):
Prefer a checkout?
git clone https://github.com/svatrous/longtake-mcp.git && cd longtake-mcp && npm install, then point the command atnode mcp-server.js.
The full guide, with what the token can and cannot do, is at longtake.studio/mcp. Prompt-writing skills for the same agent (Seedance 2.0, Seedance 2.5, Gemini Omni, character sheets) are at longtake.studio/skills.
Safety
The token acts as your account for the work: it shoots takes on your provider keys, inside your rate limits. It cannot read or change those keys, issue or revoke tokens, or touch billing — those routes turn an agent token away. Everything else you can do it can do too, including deleting a project, so keep it out of shared configs and revoke it in the same dialog if it leaks.
Local files. Three tools read a file from this machine: upload_asset; create_character, when given a portrait or a voice sample by path; and generate_mocap, for its reference photos. They take only media — jpg, png, webp, gif, mp3, wav, m4a, ogg, mp4, mov — and only a regular file whose first bytes really are that format, up to 89 MB. A directory, a device, a pipe or a text file renamed to .png is refused before anything is read or sent. What does go goes to your studio (STUDIO_URL), into the account the token belongs to, and nowhere else.
HTTPS only. The token travels over https://, or over plain http:// to a studio on this machine (localhost, 127.0.0.1, [::1]). Any other http:// address is refused before a request is made.
License
MIT. This file is a copy of the studio's own mcp-server.js; the studio also serves it as longtake.studio/mcp-server.cjs.
Source: README.md at commit b8d31f0
Tools
0Version history
3- v1.0.2LatestOct 10, 2026
- v1.0.1Oct 9, 2026
- v1.0.0Sep 25, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts