MCP server
Connect AI agents to ShortFast over the Model Context Protocol, with tools that mirror the REST endpoints one to one.
The same capabilities as the REST API are exposed to AI agents over the Model Context Protocol. Generate an MCP key under Settings > API & Webhooks > MCP Server, then connect any MCP client to the Streamable HTTP endpoint:
https://app.shortfast.com/mcp?key=sf_mcp_xxxxxxxxxxxxxxxxxxxxxxxxThe endpoint speaks JSON-RPC 2.0. Clients that connect by URL alone (Claude,
ChatGPT, n8n, Make, and most others) can paste it as is; a client that prefers a
header may send the key as Authorization: Bearer sf_mcp_... instead.
An MCP key is separate from a REST key and starts with sf_mcp_. There is at
most one per workspace, so regenerating replaces it and invalidates the URL you
handed out before.
The tools mirror the REST API
Every tool is a facade over a /api/v1 route: same handler, same validation,
same error codes. Behaviour matches one to one, so the guides here describe the
tools too. The tool list is deliberately not reproduced on this page: ask the
client to list its tools, and read the endpoint's own page in the
API Reference for what each argument means.
Two consequences are worth knowing before you point an agent at it:
Generation, rendering and publishing spend the workspace's credits, and a publish posts to a real account. Confirm with the user before letting an agent spend on their behalf; the credit costs are readable through the same reference endpoint the API uses.
Generation and rendering are asynchronous over MCP exactly as they are over HTTP.
A create or render tool returns as soon as the job is queued, so the agent must
poll the video (or its render status) until it reads COMPLETED or FAILED, and
must not queue a second render for the same video meanwhile.
The usual flow an agent should follow is the same one the REST guides describe: create a video, poll until generation completes, render, poll until it is ready, then publish. For a recurring one: create an automation, set its schedule, profile and platforms, check its health, then activate it.
Acting as a workspace in your organization
An organization key can act on any workspace inside it by appending
&workspaceId=<workspaceId> to the connection URL, one connection per workspace:
https://app.shortfast.com/mcp?key=sf_mcp_xxxxxxxxxxxxxxxxxxxxxxxx&workspaceId=k9WmT3xR2pQ7nV4bdAn MCP connection is long-lived and carries no per-request headers, which is why
the selector lives in the URL here and in the X-ShortFast-Workspace header on
REST. See Authentication for how workspace scoping works.