Skip to main content
Glama
Sign In
screen-capture-mcp

screen-capture-mcp

by matthewpugsley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to screen-capture-mcp

No user-submitted related servers found.

    Related Servers

    • Desktop MCP

      budaesandrei
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to capture and analyze screen content across multi-monitor setups with smart image optimization. Provides screenshot capabilities and detailed monitor information for visual debugging, UI analysis, and desktop assistance.
      -

    • GetScreen MCP Server

      Kirchlive
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables capturing screenshots of all connected monitors with automatic JPEG compression and multi-platform support including WSL environments. Supports quality adjustment and image resizing through simple natural language commands.
      2 npm
      ISC

    • screenagents

      Parithosh-Varma
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to capture the actual desktop screen as base64 PNG images, with optional region, monitor, display, backend, and path targeting. Also exposes a tool for listing which native capture backends are available in the current environment.
      2
      MIT

    • Desktop MCP

      machine202502
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes two tools over stdio or HTTP that let AI agents read display geometry and capture full-screen, per-display, or region screenshots in PNG or JPEG. Runs as a VS Code extension or a standalone MCP server usable by Claude Code, Cursor, Cline and other clients.
      489 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: list_monitors enumerates displays, while capture_screen takes a screenshot. There is no overlap or chance of misselection.

    Naming Consistency5/5

    Both names follow the same verb_noun snake_case convention (list_monitors, capture_screen), making the set highly predictable.

    Tool Count4/5

    Two tools is on the lean side, but for a tightly scoped screen-capture server they cover the essential list-then-capture workflow. A minor addition could enrich it, but nothing feels extraneous.

    Completeness4/5

    The core lifecycle of discovering monitors and capturing them is covered, with thoughtful options for monitor selection, sizing, and format. Gaps remain around region/window capture or recording, but the stated purpose is well served.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources