Skip to main content
Glama
Sign In
QEMU Screenshot MCP Server

QEMU Screenshot MCP Server

by veighnsche
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to QEMU Screenshot MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-incus-vm

      RAGton
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control and automate Incus/QEMU virtual machines via SSH, supporting mouse/keyboard, screenshots, commands, and lifecycle management.
      MIT

    • nido-mcp

      Josepavese
      A
      license
      B
      quality
      A
      maintenance
      Nido is a local QEMU VM manager. Install it on your computer from https://github.com/Josepavese/nido and run nido mcp via stdio, or use npx -y nido-mcp@latest mcp with QEMU installed locally. It manages VMs on that same computer; a server hosted by Glama cannot access your local VM inventory.
      6
      2
      MIT

    • lume-vnc-mcp

      Blackphi6
      A
      license
      B
      quality
      C
      maintenance
      Enables an AI agent to see and control the screen of an already-running macOS virtual machine over VNC, exposing four tools: screenshot, click, type_text, and key_press. This lets the agent drive a disposable VM's UI directly with its own model, without touching the real desktop or running a separate agent loop.
      4
      MIT

    • PeepIt MCP

      MantisWare
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to capture and analyze screenshots of macOS applications, windows, or the entire screen using local (Ollama) or cloud-based AI vision models, with non-intrusive, fast screen capture via Apple's ScreenCaptureKit.
      3
      5 npm
      2
      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

    A3.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose of capturing screenshots from QEMU instances.

    Naming Consistency5/5

    With only one tool, naming consistency is inherently perfect. The tool name 'capture_screenshot' follows a clear verb_noun pattern and sets a consistent standard, though there are no other tools to compare it against.

    Tool Count2/5

    A single tool is too few for most server purposes, as it severely limits functionality and scope. While it may be appropriate for a minimal utility, it feels thin and incomplete for a server named 'QEMU Screenshot MCP Server', which suggests broader screenshot-related capabilities.

    Completeness2/5

    The tool surface is severely incomplete for a screenshot server. It only captures screenshots from the first running QEMU instance, with no tools for listing instances, selecting specific ones, managing captures, or handling errors, leading to significant gaps that will cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources