Frapea

{
  "mcpServers": {
    "com.frapea/editor": {
      "url": "https://app.frapea.com/mcp"
    }
  }
}

Indexed tools

Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.

25 shown · authentication unknown

• Add clips

  add_clips

  Places media segments on a timeline. Each clip: mediaRef (from get_media, 'timeline:<id>' to NEST another timeline as a clip, 'solid:#rrggbb' , 'motion:<id>' for a MOTION composition (create_motion_composition) for a generated solid-colour matte, 'adjustment:' for an adjustment clip — no picture of its own, its effects/masks/opacity grade everything below it — or 'text:' for a title, restyled via set_clip_properties' `text`), atFrame (timeline position), sourceInSec/sourceOutSec (the segment of the source to use — align these with transcript words or sceneSamples), and optional trackId (from get_timeline) to target a specific same-kind track — without it clips land on V1/A1 with overwrite semantics. A spare empty track always exists above the highest used one, so V2/A2 is available before anything sits on it. Video sources with audio get a linked audio clip automatically (on the matching A track: V2 ⇒ A2). Returns the created clip ids in order. Frames are in the target timeline's fps.

  Schema valid · SHA-256 7235e8221a39…

  View input schema

  {
    "type": "object",
    "properties": {
      "projectId": {
        "type": "string",
        "description": "Project id from get_projects."
      },
      "timelineId": {
        "type": "string",
        "description": "Target timeline id from get_timeline."
      },
      "clips": {
        "type": "array",
        "description": "[{mediaRef, atFrame, sourceInSec, sourceOutSec, trackId?}] — segments in playback order; trackId targets a specific track (default V1/A1)."
      },
      "token": {
        "type": "string",
        "description": "The session token `connect` returned. Pass it on every call — it says which browser to drive."
      }
    },
    "required": [
      "projectId",
      "timelineId",
      "clips",
      "token"
    ]
  }

• Wait for the user

  await_user_action

  Waits (up to ~45 s per call) for the user to resolve a pending Frapea prompt — e.g. the folder-permission dialog another tool just opened. The dialog waits for the user in the Frapea tab; the tool that opened it returned what they need to click. Returns {status: 'granted' | 'denied' | 'pending'}: 'pending' means they have not acted yet (call again to keep waiting), 'denied' that they declined.