agent-recorder-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_RECORDER_DIR | No | Recording root. Default: ~/.agent-recorder | ~/.agent-recorder |
| AGENT_RECORDER_FFMPEG | No | Explicit ffmpeg binary |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| startRecordingA | Start recording the agent computer display before browser or computer-use actions. Call this before the first browser or computer action. The display is selected from this agent process tree. A display belonging to another session is not used. fps defaults to 5. maxDurationSeconds defaults to 7200. When the limit is reached the capture stops and the file is kept so finishRecording can still share it. If a recording is already active, or is waiting to be shared, that recording is returned and a second recorder is not started. |
| recordingStatusA | Return the recording state, duration, display, and file size. Omit recordingId to ask about the active recording. The state is idle when nothing is recording. |
| finishRecordingA | Stop the recording and hand it to a transfer strategy. delivery defaults to ffl. cleanup defaults to after_download. The local file stays until FastFileLink reports that the download finished, then the share stops and the file is deleted. delivery local with cleanup manual returns a file URI and leaves the file in place. delivery google_drive with cleanup after_upload does not call Google. It returns localPath and uploadStatus pending. Upload that file with the connected Google Drive tool, then call confirmUpload with the Drive link. Put the returned url in the final answer as the operation replay. If this call fails, tell the user that no replay was produced and include the reason. |
| abortRecordingA | Stop a recording without sharing it. deletePartial defaults to true and removes the incomplete file. Use this when the task is cancelled or the capture is the wrong display. |
| confirmUploadA | Store the link from the connected Google Drive tool. Call this after finishRecording(delivery="google_drive") once the Drive tool has uploaded localPath. url is that Drive file link. cleanup after_upload then deletes the local recording. |
| cleanupRecordingB | Delete a local recording and stop any share still serving it. Pass the recordingId. This removes the file even if a recipient has not downloaded it yet. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool maps to a distinct lifecycle stage (start, status, finish, abort, cleanup, confirmUpload), so boundaries are mostly clear. Minor overlap exists between cleanupRecording, abortRecording(deletePartial), and finishRecording(cleanup) since all three can delete the local file, which could cause some hesitation.
Five of six tools use a consistent verb+Recording/Upload camelCase pattern (startRecording, finishRecording, abortRecording, cleanupRecording, confirmUpload). recordingStatus breaks the verb-first convention by being noun-first, a minor deviation.
Six tools is well-scoped for a capture-and-share recorder, with each tool earning its place across the start/stop/abort/share/cleanup lifecycle. No redundant or bloated entries.
The surface covers the full recording lifecycle from start through sharing and cleanup, including the Google Drive handoff path. It lacks discoverability operations like listing past recordings or retrieving an existing file, but core workflows are complete.