Recordful MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusA | Report whether the Recordful extension is connected and what the recorder is doing (idle, starting, recording, paused), the selected recording mode, the active tab, and which capture permissions are granted. Safe to call any time. |
| start_recordingA | Start a Recordful recording on the target tab using the user's saved Recordful settings (mode, microphone, camera, countdown). Resolves once capture is live, or reports why it could not start. Navigate to the page you want to show before calling this. |
| stop_recordingA | Stop the current Recordful recording. Recordful then opens its editor with the recording, exactly as when the user clicks Stop. Returns the editor tab ID when it is known. |
| pause_recordingA | Pause the current recording. Use it while you plan the next step so the video has no dead air. No-op if already paused. |
| resume_recordingA | Resume a paused recording. No-op if not paused. |
| probe_captureA | Diagnostic: check, without recording, whether the extension can capture the target tab right now with no user click, and which optional Chrome permissions are granted. Refuses while a recording is running. |
| navigateA | Open an http(s) URL in the tab the user handed to Recordful and wait for it to load. Returns the final URL and title. Refs from earlier snapshots stop working. |
| snapshotA | List the interactive elements (links, buttons, fields, checkboxes, tabs, menu items) and headings in the recorded tab, each with a ref to pass to click/type/scroll/wait_for, its role, accessible name, current value or state, and bounding box in CSS pixels. Refs stay the same for an element while it stays on the page. |
| clickA | Move Recordful's visible cursor to the element, scrolling it into view if needed, and click it, with a click highlight in the video. Reports a navigation the click started. Fails with ELEMENT_OBSCURED (naming what is on top, with its ref) if something covers it. |
| typeA | Click the field, then type the text at a human pace (text inputs, text areas, content-editable areas). Set clear to replace what is already there. Use press for Enter, Tab and other keys. |
| pressA | Press a key in the focused element, e.g. Enter to submit a form, Tab to move focus, Escape to close a dialog, ArrowDown in a menu, Shift+Tab, Control+a. Recordful also performs the key's usual effect (submitting, moving focus, deleting), since pages ignore synthetic keys otherwise. |
| scrollA | Scroll smoothly: either bring an element (ref) into view, or scroll the page in a direction, by amount pixels or most of a screen. |
| wait_forA | Wait until text appears on the page or an element (ref) becomes visible, or with state "hidden" until it goes away. Keeps waiting across navigations. Fails with WAIT_TIMEOUT if it doesn't happen in time. |
| screenshotA | Capture what the recorded tab shows right now, as an image, to check the page looks right. The tab must be the active tab of its window. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| record_feature | Plan and record a short product demo of a feature with Recordful: work out the user-facing flow, get the app running with test data, record a clean walkthrough, and open it in the editor. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool maps to a distinct action within its domain: recording lifecycle (start/stop/pause/resume), browser control (navigate/click/type/press/scroll/snapshot/wait_for), and diagnostics. The only mild overlap is get_status vs probe_capture, which both report connection and permission state, but their descriptions distinguish state reporting from a pre-capture diagnostic check.
All names are lowercase snake_case, which is consistent, and the recording tools follow a clean verb_noun pattern (start_recording, stop_recording, pause_recording, resume_recording). However, browser tools mix single verbs (click, type, press, scroll, snapshot) with verb_noun forms (get_status, probe_capture, wait_for), a minor deviation from a single predictable pattern.
14 tools is well within the ideal range and each earns its place: a full recording lifecycle, a coherent browser-automation set, and two diagnostics. Nothing feels redundant or padded for the server's stated scope.
The surface covers recording control and the core automation primitives (navigate, snapshot, click, type, press, scroll, wait_for) with file editing via navigate. Minor gaps exist, such as no dedicated hover or select-option helper, but these are largely workable via click/type/press.