Screen capture that stays on your machineGet the deal
← All posts

6 min readUpdated 20 November 2026

Screen Recording With Claude: How an AI Assistant Made Our Demo Video Over MCP

How Claude Code recorded, zoomed, edited and exported a real walkthrough through FramioCam for Mac's MCP server: every tool call, and what stays manual.

  • screen-recording
  • mac
  • ai
  • how-to
Screen Recording With Claude: How an AI Assistant Made Our Demo Video Over MCP

KEY TAKEAWAYS

  • FramioCam for Mac includes an MCP server. Claude Code, Claude Desktop, Codex, Cursor or any MCP client can capture, record, edit, caption and export through it.
  • The assistant drives the app being filmed with its own tools. FramioCam never clicks or types; it records the window and takes pointer hints so the video gets a cursor, click ripples and zooms.
  • Sign-ins and your licence stay manual. An assistant can make the MP4 and fill in a post, and nothing is published until you press Publish.

The walkthrough clip on our AI assistants guide was not made by a person at a keyboard. An AI assistant, Claude Code, made it through the MCP server built into FramioCam for Mac: it recorded a Chrome window, sent its clicks, zoomed on them, sped up the pauses and exported the MP4.

This post is the record of that session: the tool calls in order, what went wrong on the first take, and where the assistant stops and you take over.

The finished clip. Every step after "start" was a tool call; no hand touched the mouse.

What you need

  • FramioCam for Mac with Mac Pro. AI assistants are a Mac Pro feature. Recording needs macOS 15 or later on Apple silicon.
  • An MCP client on the same Mac. Claude Code, Claude Desktop, Codex, Cursor, or anything else that speaks the Model Context Protocol.
  • AI Assistants switched on. Open Settings → AI Assistants in FramioCam and switch it on. Each client has a Connect row with its setup steps.
  • One approval. The first time an assistant connects, FramioCam asks you in its own dialog. You can revoke it in Settings later.

Ask the assistant to check first. The framiocam_status tool reports whether AI Assistants is on, whether your plan includes it, and whether macOS allows Screen Recording, and gives a sentence to pass on to you for anything missing.

The request

In plain words, the request was:

Record a walkthrough of the FramioCam for Mac page in Chrome: scroll to publishing, open the publishing guide, and show scheduling. Zoom in on each click, speed up the pauses, and export an MP4.

The session, tool by tool

1. Get the screen ready. FramioCam records what is visible on screen, so a headless browser shows it nothing. The assistant opened an ordinary Chrome window in its own clean profile, sized 1440 × 900, and connected to it with its browser tools (Playwright, over Chrome’s debugging port). The browser work is the assistant’s. FramioCam never clicks, types or opens pages.

2. list_targets. This lists every display and window FramioCam can capture, from every app. The assistant picked the Chrome window by its title. Recording one window keeps everything else on the desktop out of the video: the terminal, the email client and the chat app open beside it never appeared.

3. start_recording. It records the window, with a 3-2-1 countdown like a recording you start yourself. Microphone, system sound and camera stay off unless you ask for them.

4. Drive the page, with pointer_hint before each click. Browser automation clicks without moving the real mouse, so without help the video would have no cursor at all. Before each click the assistant worked out the element’s position on screen and sent pointer_hint twice: move to glide the drawn cursor there, then click at the moment it clicked. It did this three times: the “How publishing works” link, the Scheduling chapter, then the AI assistants guide.

5. stop_recording. This saves the recording to the FramioCam library and returns its file, length and size: 24.8 seconds at 2880 × 1800.

6. edit_recording. One call set zoom: "auto", which zooms in on each of the three hinted clicks, chose the Mac cursor with a shadow, and turned click ripples on. The studio window opened with the changes, each one a step you can undo with ⌘Z.

7. describe_recording, then edit_timeline. The assistant read the recording back: every click with its time, every zoom and every clip. Then it split the timeline around two idle stretches, the hero sitting still before the scroll and a pause before the first click, and set those clips to 4× and 3× speed. The video went from 24.8 to 21.3 seconds without a jump cut.

8. export_recording. This writes the MP4 to your exports folder and reports its path. For the website the assistant re-encoded it to 1440 wide with no audio track.

The takes that didn’t make it

The first take had a cookie banner across the bottom of every frame. The assistant found it by pulling one frame per second from the file and looking at them, declined the banner in the browser profile, and recorded again.

The second take was clean until the last second. The page it ends on embeds the previous version of this very clip, and that clip’s poster still showed an old promotion bar. The fix was to put the new clip and poster on the page first, then record a third take, so the video shown inside the video is the new one.

Both mistakes were found the same way an editor finds them: by checking the frames. An assistant gets the same file you would, and it is worth asking it to review its own output before you do.

What the assistant can’t do

These limits are in the server, not in a policy note:

  • Publishing waits for you. Since version 0.2.0 an assistant can prepare a post to YouTube or a Facebook Page: the publish sheet opens filled in and nothing is sent until you press Publish. You can let assistants publish without asking in Settings. No tool uploads to the cloud or makes a share link.
  • No sign-ins, licence or settings. Your accounts, your licence, the AI Assistants switch and macOS permissions are never reachable through a tool.
  • No clicking in other apps. FramioCam captures the screen and edits its own projects. Moving a capture to the Trash still needs your click in FramioCam’s own dialog.
  • Same plan rules as the buttons. Watermarks and limits match what you get by hand, and existing files are never replaced.

Never ask an assistant to type a password into a window that is being recorded. Sign in yourself before the recording starts.

Other things to ask for

The same server handles screenshots and edits as well as recordings. A few requests that map straight onto its tools:

  • “Screenshot the error dialog in Xcode, circle the error in red, blur my email address, and copy it to my clipboard.”
  • “Caption yesterday’s pricing recording and save the subtitles as SRT.”
  • “Crop the onboarding recording to 9:16 for Shorts and export it at 1080.”

Each one runs the same function as the button you would press, in the window you are looking at, so you can step in at any point and carry on by hand. The full list of tools and example prompts is in the AI assistants guide.

Captions come from macOS’s on-device speech recognition, so asking an assistant to caption a recording doesn’t send your audio anywhere.

Try it

Download FramioCam for Mac, switch on AI Assistants with Mac Pro, and ask your assistant for a walkthrough of something you have explained by hand too many times.

SHARE

FramioCam captures screenshots and screen recordings, dresses them, and edits them on a real timeline — in the browser, with nothing uploaded to us.

See what it costs

Your creative workflow starts here

Make your next capture
worth sharing.

From a quick screenshot to a polished walkthrough. Capture, edit, and share with FramioCam.

Add to Chrome

Free to start One-time paid plans

A real FramioCam Studio project, ready to edit and export.
Meet your new creative studio

FramioCam in action

Record, capture, edit, and export in Chrome.

Watch on YouTube ↗