Skip to content
Back to the index

Screen Control

github.comInfrastructure

PulseGate's liveness check found it on 18 Sep 2026; it has been in the index since 18 Sep 2026. How this is checked

Screen Control is a developer tool that exposes local screen perception and computer interaction capabilities to AI agents. It supports OCR, vision frames, MJPEG streaming, mouse and keyboard input, window and virtual-desktop control, game mode, a local HTTP API, and MCP integration.

Inferred · not functionally tested

CLIWindowsSelf-hostedAPI
Screen Control preview
Visit github.com

Overview

6 features

Purpose: Giving AI agents safe, general-purpose control of a local computer through screen perception and input automation.

Inferred · not functionally tested

Audience: AI agent developers

Inferred · not functionally tested

Functions: browser_automation, agents, data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: unknown · license: Proprietary · platforms: DESKTOP, API, CLI · deployment: cli, windows, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

Screen Control is a Browser DevTools & extensions project. Inferred · not functionally tested: It focuses on giving AI agents safe, general-purpose control of a local computer through screen perception and input automation. Inferred · not functionally tested: It is built as an open-source project for AI agent developers. Basis unknown · not verified: It ships for the command line, Windows, and API, and it can be self-hosted.

Xeakaes builds and maintains Screen Control. Inferred · not functionally tested: Among its 6 catalogued features are screen perception, OCR, and vision frames. Inferred · not functionally tested: Catalogued interfaces include a public API and an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Screen perception
  • OCR
  • Vision frames
  • MJPEG streaming
  • Mouse control
  • Keyboard control

Topics: Inferred · not functionally tested

Tags
computer-use-agentsscreen-perceptionmouse-keyboard-controlsafety-gated-automationlocal-mcp-server
AI capabilities
MultimodalStructured
Inference: Local

JSON profile · Text profile · Access guide

Built with & integrations

Connectors
APIMCP
Runs on
CLIWindowsSelf-hostedAPI-only

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed18 Sep · 06:04 UTC
    Screen Control seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about Screen Control

What does Screen Control do?
Inferred · not functionally tested: Screen Control focuses on giving AI agents safe, general-purpose control of a local computer through screen perception and input automation. It is catalogued under Browser DevTools & extensions on PulseGate.
Who is Screen Control for?
Inferred · not functionally tested: Screen Control is an open-source project built for AI agent developers.
What platforms does Screen Control run on?
Basis unknown · not verified: Screen Control runs on the command line, Windows, and API. It can also be self-hosted.
Is Screen Control still active?
PulseGate's liveness check found it on 18 Sep 2026.
Who develops Screen Control?
Screen Control is developed by Xeakaes.
Does Screen Control have an API or integrations?
Inferred · not functionally tested: Yes — Screen Control exposes a public API and an MCP server.

Similar projects

Closest matches by what these projects do

Submit to the index
Apps, agents and models — free, no signup.