Skip to main content
Glama
screen-record-mcp

screen-record-mcp

by strubedo

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
start_recordingB

Start a screen recording (with system audio by default, or video-only) to a given output .mp4 path. The first call on a fresh system may require the user to approve a one-time KDE screen-share permission dialog on their desktop - this cannot be approved programmatically.

stop_recordingA

Stop the current recording so the output file is properly finalized and playable. No-op (returns stopped=False) if no recording is in progress.

check_recording_statusA

Check whether a recording is currently in progress, and if so, its output path.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool maps to a distinct phase of the recording lifecycle: start begins capture, stop finalizes the file, and check_recording_status is a read-only query. There is no plausible confusion between starting, stopping, and inspecting a recording.

Naming Consistency5/5

All three tools use snake_case with a verb_noun pattern (start_recording, stop_recording, check_recording_status). The convention is uniform and immediately readable.

Tool Count5/5

Three tools exactly cover the lifecycle of a single-domain screen recorder, and each one earns its place with no filler. The surface is lean but appropriately scoped for a narrowly focused server.

Completeness4/5

Start, stop, and status form a complete lifecycle with no dead ends, and status even exposes the output path. Minor gaps exist: no pause/resume and no way to enumerate or manage prior recordings, though these are easily worked around.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues