Screenshot Server

Created By
KunihiroSa year ago
Overview

what is Screenshot Server?

Screenshot Server is a modular communication protocol (MCP) server designed to capture screenshots and provide their file paths for use by other processes or AI assistants.

how to use Screenshot Server?

To use the Screenshot Server, an MCP Host (like an AI assistant) calls the take_screenshot_and_return_path tool, which captures the screen, saves it as an image file, and returns the absolute path to that file.

key features of Screenshot Server?

  • Captures screenshots and saves them to a specified location.
  • Returns the absolute file path of the saved screenshot for further processing.
  • Supports custom save locations and filenames through the take_screenshot_path tool.

use cases of Screenshot Server?

  1. Integrating with AI assistants to capture and analyze screen content.
  2. Automating screenshot capture for documentation or reporting purposes.
  3. Facilitating image processing workflows by providing file paths to other tools.

FAQ from Screenshot Server?

  • What programming language is required to run the Screenshot Server?

Python 3.x is required to run the server.

  • How do I install the necessary dependencies?

Use the command uv sync to install required libraries like mcp[cli], pyautogui, and Pillow.

  • Can I specify where to save the screenshots?

Yes! You can use the take_screenshot_path tool to specify the directory and filename for the screenshot.

Server Config

{
  "mcpServers": {
    "Screenshot-server": {
      "command": "powershell.exe",
      "args": [
        "-Command",
        "Invoke-Command -ScriptBlock { cd '<YOUR_WINDOWS_PROJECT_PATH>'; & '<YOUR_WINDOWS_UV_PATH>' run screenshot.py }"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
KunihiroS
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago