Recordful

Recordful MCP

Let any AI app record, upload and read back product demos with Recordful.

Ask your AI to "record how the new sign-up flow works". It plans a short walkthrough, opens the page in a tab of its own, then navigates, clicks and types with a smooth on-screen cursor while Recordful records. When it stops, Recordful's editor opens with the video. With Recordful Pro, it can also upload the video, hand you the link, and read the transcript back.

It ships as an MCP server for AI apps and a CLI for anything with a shell.

Works with Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, opencode, Codex, Gemini CLI, Antigravity and any other app that supports the Model Context Protocol. The AI doesn't need a browser of its own. Everything runs on your computer: nothing to host, no account, no API key.

Install

You need Chrome and Node.js 20.10 or newer. The Claude Desktop bundle includes everything, so it doesn't need Node.

1. Install Recordful from the Chrome Web Store.

2. Add Recordful to your AI app. The fastest ways:

• Let the AI do it. Run npx -y recordful-mcp prompt (or copy it from the help center) and paste the result into your AI app. It installs the server and skill for itself, tells you what needs a restart, and asks what to record first.
• One command. npx -y recordful-mcp install --target claude (also cursor, codex, opencode, vscode, windsurf, gemini, antigravity) shows what it would change; add --yes to apply. It merges into the app's own config and never replaces your other servers.

Or add it by hand:

/plugin marketplace add iKislay/recordful-mcp
/plugin install recordful@recordful

{ "mcpServers": { "recordful": { "command": "npx", "args": ["-y", "recordful-mcp"] } } }

{ "mcpServers": { "recordful": { "command": "npx", "args": ["-y", "recordful-mcp"] } } }

{ "servers": { "recordful": { "type": "stdio", "command": "npx", "args": ["-y", "recordful-mcp"] } } }

{ "mcp": { "recordful": { "type": "local", "command": ["npx", "-y", "recordful-mcp"], "enabled": true } } }

[mcp_servers.recordful]
command = "npx"
args = ["-y", "recordful-mcp"]

npx -y recordful-mcp setup prints all of these.

3. First recording (one-time setup):

1. In Recordful's popup, click More → AI agents and turn it on. Chrome asks to allow screen recording once; click Allow.
2. Ask your AI to record something. When it asks, click the Recordful icon once to connect it.
3. Recordful asks you to approve the app. If the 4-digit code matches the one your AI shows, click Allow.

After that, Recordful connects to your AI app by itself whenever it starts. The agent opens its own tab for page tools and screenshots; the only click left is the Recordful icon on a tab you want recorded (Chrome requires it before an extension can capture a tab). If you turned AI agents on before Recordful 4.7.0, turn it off and on once to allow connecting by itself.

Use it

Ask in plain words:

• "Record a demo of signing up and signing in on localhost:3000."

• "I just built the billing page. Record a short video of how it works."

• "Take a screenshot of the pricing page." / "Screenshot the whole page with a 3D look." Recordful opens it in its screenshot editor, in your usual look unless you ask for another. With no look of your own, it starts on a wallpaper picked to match the screenshot's colours.

• "Screenshot my Figma window." / "Take a screenshot of my whole screen." With the Recordful desktop app, your AI screenshots the desktop too: a screen, a window by name, or an area you drag. Turn it on once in the app: Settings → AI agents → Let AI agents take screenshots. Each screenshot opens in the app's editor, with a notification naming the AI that took it.

• "Upload that and give me the link." / "What did I say in the last recording?" (Recordful Pro)

The AI works out the flow, uses test data (never your real accounts), records with pauses while it thinks, and stops so the editor opens. Apps that support MCP prompts also offer record_feature, a guided version of this workflow. While an app is connected, Recordful's icon shows an AI badge.

Free and Pro

The AI checks your plan first. On the free plan it records as usual and tells you once that links and transcripts come with Pro, instead of failing. Recordings made while signed in to Pro go to the cloud as they record.

From the command line

The same things work from a terminal, for agents with a shell or for you:

npx -y recordful-mcp start        # click the Recordful icon on the tab first
npx -y recordful-mcp stop
npx -y recordful-mcp upload --title "Sign-up demo"
npx -y recordful-mcp transcript > transcript.txt
npx -y recordful-mcp videos

The first command asks you to click the Recordful icon once; a small helper keeps the connection for later commands and exits after 30 idle minutes. Add --json for machine-readable output. All commands: npx -y recordful-mcp --help; npx -y recordful-mcp guide --json lists everything an agent needs to know.

Why the click? Chrome only lets an extension record a tab after you click it there, and no app can click for you. The click also marks the only tab the AI may act in.

Do I need to host anything?

No. The server runs on your computer and talks to Recordful over 127.0.0.1. Recordings stay on your computer unless you, or your AI with Recordful Pro, upload them to recordful.app.

Only cloud-only chat apps (claude.ai or ChatGPT in a browser or on a phone) would need a hosted connector, because they can't run programs on your computer. That's planned.

Privacy and security

• Off until you turn it on, and off again with one switch.
• Local only: the server can't be reached from other devices or from web pages.
• Paired once per computer after you approve a matching code. Every connection proves the pairing, and the secret is never resent.
• Only the official Recordful extension can connect by default.
• One tab: the AI acts only in the tab you handed over.
• Revocable: Paired AI apps → Forget on the AI agents page, or npx -y recordful-mcp unpair --all.

Details: SECURITY.md.

Troubleshooting

Run npx -y recordful-mcp status to see the pairing state.

More

• Tools, CLI and configuration
• How it works: protocol and pairing
• Development and releasing
• Changelog

License

MIT