Agent API And MCP Setup

Fraime.it can expose open projects to local agents through a local bridge and MCP helper. The app stays in control of project files, preview, undo, save, and export while agents propose structured edits.

When to Use Agents

Use the Agent API when you want help with structured timeline work:

• Inspect open projects and timeline state
• Create a working copy before broad changes
• Add or update annotations, subtitles, overlays, and visual assets
• Suggest trims, filler-word cuts, or speed-ups
• Preview an edit plan before applying it
• Export a project after review

Do not use agents as the final privacy reviewer. Always manually check redactions and exported videos.

Setup From the App

Open Fraime.it and use the Agent API controls in the app settings or menu.

• Copy MCP Config gives the configuration snippet for compatible local agent clients.
• Copy Helper Path gives the local helper executable path.
• Keep the Fraime.it app open while agents inspect or edit projects.
• Open the project you want the agent to work with before asking for project-specific actions.

If an agent cannot find the project, confirm the project window is open and the local bridge is running.

Working Copies

Use working copies for experiments, aggressive trims, launch clips, and alternate exports.

Agent-created working copies use a visible .agent naming convention so the original recording stays separate. Keep the original project as source material and apply broad agent edits to a copy.

Review Before Apply

Agents can dry-run edits and describe what would change before applying the plan. Review the summary carefully, especially changes that affect:

• Project timing and clip ranges
• Redactions and text replacements
• Subtitle timing
• Export settings
• Large sections of the timeline

Apply only the edits you understand. If the plan is too broad, ask for a smaller one, such as only title cards, only filler cuts, or only overlay suggestions.

Available Operation Types

The bridge is designed around structured project operations, including:

• Listing open projects
• Opening projects
• Reading project summaries and timeline data
• Creating working copies or duplicates
• Previewing edit plans
• Applying edit plans
• Undoing and redoing edits
• Saving projects
• Capturing frame snapshots
• Exporting projects
• Running transcription, OCR redaction analysis, smart trim, and filler-word analysis
• Importing image assets into the project and placing them on the canvas
• Renaming or deleting project packages

Recording control tools currently report capability status rather than starting capture, because recording is still owned by the interactive macOS capture window and ScreenCaptureKit permission flow.

Exact tool names depend on the MCP client, but the workflow should stay review-first: inspect, preview, apply, verify, save or export.

Safe Prompting

Good prompts are specific:

• "Create a 30 second launch clip from this project, but preview the plan first."
• "Add title cards at the major section changes."
• "Suggest filler-word cuts from the transcript without applying them."
• "Find places where a zoom or callout would help explain the UI."
• "Prepare a vertical Short as a working copy."

Avoid vague prompts like "make it better" when you care about timing, privacy, brand tone, or export format.

Troubleshooting

If the MCP client cannot connect, copy the config again from the current app build and verify the helper path. If project actions fail, make sure the project is open in Fraime.it. If edits apply but the result is not useful, undo in the app or return to the original project/working copy.