Record a Demo Video of Your Localhost App

The problem with demoing what you just built #

The best time to record a feature demo is the moment it works: the details are fresh and the release notes are due. But the feature only exists on your laptop at localhost:3000. Most demo tools need a public URL, so you'd deploy to staging, set up a tunnel, or record your screen by hand and edit it afterwards.

DemoReady records the app on your machine directly. Your AI coding agent directs the demo, and a small connector securely shares the one address the agent opened.

How it works #

Add DemoReady to your agent (Claude Code, Codex, Cursor or any MCP client). It's one command, npx -y demoready-mcp, and the setup guide covers every client. You can also tell your agent: "Read https://demoready.ai/docs.md and set up DemoReady for me."
Sign in once with npx -y demoready-mcp login. You paste your API key in your own terminal, so it never appears in the chat.
Ask for a demo: "Record a 3-scene demo of localhost:3000 showing how to invite a teammate. Log in off camera first."
The connector opens an encrypted, outbound-only connection to DemoReady. The recording browser runs in the cloud and reaches only localhost:3000 through it. DemoReady adds the cursor, captions and voice-over, and the finished video lands in your library.

What stays private #

Only the addresses your agent opened are shared. If your app calls an API on another port, the agent names it (for example localhost:8000). Every other port and every other device on your network is refused, on your machine.
Only your own recordings can use the connection; it's signed in with your API key.
Only while recording. Sharing stops when the demo finishes or is discarded, and whenever the connector exits.
No public URL and no open ports. Your computer dials out; nothing dials in.

What works through the connector #

Cookies and logins, API calls to other local ports you name, WebSockets (including dev-server live reload) and normal page assets all work. A few limits:

Responses over 25 MB, or requests slower than 120 seconds, fail.
Streamed responses, such as token-by-token AI answers, arrive all at once rather than streaming.
localhost over HTTPS with a self-signed certificate isn't supported yet; use plain http://localhost.
Service workers are turned off during recording, so offline caching and mock-API service workers (such as MSW) don't run.

Pricing #

Localhost recording is part of every plan that includes MCP: MCP at $4.99/month for 10 agent-directed demos, MCP Plus at $9.99/month for 30, or Pro and Studio. Your agent does the directing, so there's no per-demo AI charge. See pricing.

FAQ #

Do I need to deploy my app first? #

No. That's the point: record it on localhost the moment it works.

Does DemoReady see the rest of my computer? #

No. The connector forwards only requests for the exact local addresses your agent opened, and refuses everything else before it leaves your machine.

Which agents work? #

Any MCP client whose model can read screenshots: Claude Code, Codex, Cursor, Claude Desktop, Windsurf and VS Code with Copilot agent mode. See demo videos from AI agents.

Can I record a public site the same way? #

Yes. Give your agent any public URL, or use the web app without an agent at all.

Record a demo video of your localhost app, before it ships.