How do I record an app behind a login?

When the recorder needs authentication, your agent can call authenticate to open a visible browser window. Sign in there, then let the agent continue. The local browser profile keeps the session for later recordings until it expires.

Recording and seats are free, and every workspace gets 30 monthly credits. Additional credits cost $0.02 each. Playback and transcription use one credit per minute; voiceovers and dubs use two per video minute. These features are included on every plan and use the same credit pool.

MCP SETUP & TOOL REFERENCE

Connect your agent.
Give it the tools to record.

Q: Do I need both connections?

Use the hosted connection to search your library, read transcripts, and manage sessions. Use the local recorder when your agent needs Rec to open, drive, and record a browser. They have separate server names in these examples, so you can add both to the same client.

Q: Which clients can record a browser?

The recorder needs an MCP client that can run a local stdio server, such as Claude Code, Claude Desktop, or Cursor. A hosted-only client can access the hosted tools, but that connection does not launch a browser on your computer.

Q: When will the narration be ready?

The share link is returned after upload. The summary and English voiceover are generated afterward from the session notes. Ask your agent to add clear notes for each meaningful step, and review the processed recording before sending it.

Start with your Rec workspace. Add the local recorder when you want your agent to drive a browser and capture a demo.

Connect your workspace Set up browser recording Browse the tools

01 / HOSTED CONNECTION

Connect your Rec workspace.

The hosted server has 9 tools for library search, transcripts, summaries, and recording sessions. It doesn’t launch or drive a browser.

Claude Code

Run this command in your terminal, then complete the Rec sign-in flow in your MCP client. Create a free Rec account if you don’t have one.

Other clients with remote MCP support

Add this server URL in your client’s MCP settings and complete the OAuth sign-in:

https://recapp.dev/api/mcp

02 / LOCAL BROWSER RECORDER

Give your agent a real browser.

The local package opens Chromium on your computer, captures video, and uploads it to your Rec workspace. It needs a Rec API key and a client that supports local MCP servers.

Create a free Rec account

Claude Code

Create an API key in your workspace’s Settings → API Keys.
Replace YOUR_REC_API_KEY with that key in the command below. Run it in your terminal.
Reconnect your client if needed. The first recording downloads Chromium if it isn’t installed.

The name recapp-recorder keeps this connection separate from the hosted recapp server.

Claude Desktop

Download the Rec bundle, open it with Claude Desktop, and enter your Rec API key when prompted. The bundle runs the browser recorder locally.

Download the desktop bundle

Cursor and other local clients

Add this entry to your MCP configuration. Replace the placeholder with your Rec API key.

{
  "mcpServers": {
    "recapp-recorder": {
      "command": "npx",
      "args": ["-y", "@recapp/mcp"],
      "env": {
        "RECAPP_API_KEY": "YOUR_REC_API_KEY"
      }
    }
  }
}

03 / YOUR FIRST RECORDING

Give it a specific brief.

Tell your agent where to go, what to show, and who the demo is for. Clear notes help Rec generate useful narration.

“Record a demo of the new billing flow at my app’s URL. Show how to create an invoice and preview it. Add a narration note at each step. If you need a login, open the sign-in window for me. Return the share link when you’re done.”

Review the video once processing is complete. Then share it with your team or add it to your docs.

WHAT EACH CONNECTION PROVIDES

Two connections. Different jobs.

Hosted: library & sessions

list_recordings: List recordings in your workspace.
search_recordings: Search titles and transcripts.
get_transcript: Read a recording’s transcript.
get_summary: Read the summary and key timestamps.
start_agent_session: Create a recording session.
annotate_session: Add notes and events to a session.
get_session_upload_url: Get a URL to upload captured video.
stop_agent_session: Finish the session and start processing.
search_sessions: Search agent sessions and annotations.

Local: browser & recording

record_start: Open a browser and start capturing video.
authenticate: Open a visible window for you to sign in.
browser_navigate: Navigate to a URL.
browser_snapshot: Read the current page and its controls.
browser_click: Click an element from the snapshot.
browser_type: Enter text into a field.
browser_press_key: Press a keyboard key.
browser_wait: Wait for a page state or a short interval.
record_note: Add a note for the timeline and narration.
record_stop: Upload the recording and return its share link.

Setup questions

Do I need both connections?

Which clients can record a browser?

When will the narration be ready?

What uses credits?

Have a feature ready to show?

Start with one flow. Ask your agent to record it, then review the result.

See the release-demo workflow