Mcp Window Screenshooter

MCP其他

提供方 Tiartyos

其他 stdio · 本地进程 会话登录 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

A cross-platform Model Context Protocol (MCP) server that enables AI agents to capture screenshots of specific application windows!

一句话选型结论

按资料字段整理

Mcp Window Screenshooter 属于其他类 MCP 服务器,stdio · 本地进程,会话登录,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类其他 传输方式stdio · 本地进程 鉴权会话登录 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

其他
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

screenshot capture ai integration

支持客户端

适用场景

screenshot captureai integration

安装与配置

stdio · 本地进程 会话登录
客户端在本机拉起子进程,数据不出本机
python server.py

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
接入外部数据

把外部系统的数据接进对话。

自动化重复操作

把固定步骤交给模型跑。

补充工具能力

给模型补上它原本没有的能力。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在其他场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Mcp Window Screenshooter当前 未标注 stdio · 本地进程 本地部署 有 未标注
gemini-cli 未标注 stdio · 本地进程 本地部署 有 2026-04-13
ext-apps 未标注 stdio · 本地进程 本地部署 有 2026-04-19
northcinder 未标注 stdio · 本地进程 本地部署 有 2026-08-23
fastctx 未标注 stdio · 本地进程 本地部署 有 2026-08-23
quickstart-resources 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

其他
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Tiartyos上游标注的维护方 Tiartyos
分类其他本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

7.1 KB
来自项目仓库与上游目录的原文,未做删改

Window Screenshooter MCP Server 🖼️

A cross-platform Model Context Protocol (MCP) server that enables AI agents to capture screenshots of specific application windows! (≧◡≦)

Overview

Window Screenshooter is an MCP server built in Python that provides AI agents with the capability to take targeted screenshots of specific application windows across Windows and Linux platforms. Unlike traditional screen capture solutions that only capture the entire screen, this server allows precise window-based capture for AI verification workflows, automated testing, and application monitoring.

✨ New Feature: Smart Window State Restoration & Focus Management!

The latest version now includes automatic window state restoration and intelligent focus handling! 🎉

When capturing windows, the server will:
- 📸 Save the original window state (minimized, maximized, position, etc.)
- 🔄 Temporarily modify the window if needed for capture
- ✨ Restore the window to its exact original state after capture
- 🎯 Auto-detect your editor (Cursor, Trae, Windsurf, VS Code, etc.) and restore focus to it
- 📉 Minimize captured windows if the calling application can't be found
- 💫 Work seamlessly across all supported platforms

This means your workflow stays smooth - focus returns to your editor and windows don't get left in unexpected states!

Key Features

  • 🖼️ Window-Specific Capture: Target individual application windows by name or title
  • 🌐 Cross-Platform Support: Works on Windows and Linux with platform-optimized backends
  • 🔧 MCP Integration: Seamless integration with AI agents through Model Context Protocol
  • 📡 STDIO Transport: Uses standard input/output for reliable communication
  • ⚡ Performance Optimized: Platform-specific implementations for maximum efficiency

Installation & Setup

Prerequisites

  • Python 3.12+
  • Windows or Linux

Quick Start

  1. Clone or download this repository:bash git clone <your-repo-url> cd window-screenshooter

  2. Install dependencies:bash pip install pywinctl pillow pywin32 # Or use the project file pip install -e .

  3. Test the server:bash python test-mcp.py

  4. Run the MCP server:bash # STDIO mode (for MCP clients) python server.py

MCP Tools

The server exposes three main MCP tools:

1. capture_window

Captures a screenshot of a specific window by title or identifier.

Parameters:
- windowTitle (string): Exact or partial window title to match
- outputPath (string, optional): Save location for screenshot
- format (string, optional): Image format (PNG, JPEG) - default: PNG
- quality (int, optional): JPEG quality (1-100) - default: 85

Returns: Base64-encoded image data or file path confirmation

Example:```python

Save to file

await capture_window("Notepad", "screenshot.png", "PNG")

Get base64 data

await capture_window("Calculator")


### 2. `list_windows`
Enumerates all available windows on the system.

**Returns:** Array of window objects with ID, title, position, and size information

**Example:**```python
await list_windows()

3. get_window_info

Retrieves detailed information about a specific window.

Parameters:
- windowIdentifier (string): Window title or ID

Returns: Window metadata including position, size, visibility state, and process information

Example:```python
await get_window_info("Visual Studio Code")


## Platform-Specific Features

### Windows Implementation
- Utilizes `win32gui` with BitBlt API for robust window capture
- Can capture minimized, hidden, or overlapped windows
- High-performance Graphics Capture API integration
- Provides Windows handle (HWND) and process information

### Linux Implementation
- X11-based window capture using native protocols
- Direct window buffer access for efficient capture
- Support for common Linux desktop environments

## MCP Client Configuration

### For Cursor IDE
Add to your MCP configuration file:```json
{
  "mcpServers": {
    "window-screenshooter": {
      "command": "python",
      "args": ["server.py"],
      "cwd": "/path/to/window-screenshooter",
      "transport": "stdio"
    }
  }
}

For Claude Desktop

Add to your claude_desktop_config.json:```json
{
"mcpServers": {
"window-screenshooter": {
"command": "python",
"args": ["server.py"],
"cwd": "/path/to/window-screenshooter"
}
}
}


## 💡 IDE Configuration Tip

> **📝 Note:** For optimal workflow integration, consider adding this rule to your IDE configuration:
>
> *"Before capturing windows or screens with the MCP screenshooter, ALWAYS list windows first to get correct names. If working on a Web project, the default browser is Brave. If working on a Unity project, the user wants the Unity game scene window. After you make a screenshot or capture a screen, ALWAYS use vision."*
>
> This helps ensure accurate window targeting and proper follow-up analysis of captured content! ✨

## Usage Examples

### AI Development Workflows
- **Code Verification**: AI takes Unity editor screenshots to verify game object placement
- **UI Testing**: Capture application states during automated testing sequences
- **Documentation**: Generate visual documentation of application interfaces
- **Debugging**: Visual confirmation of application behavior changes

### Automation Scenarios
- **Quality Assurance**: Screenshot comparison for regression testing
- **Process Monitoring**: Capture application states for workflow verification
- **Training Data**: Generate labeled screenshots for computer vision training

## Error Handling

The server implements robust error handling for:
- Window not found scenarios
- Permission-denied capture attempts
- Cross-platform compatibility issues
- Invalid parameter validation
- Graceful degradation when platform-specific features are unavailable

## Development & Contributing

### Project Structure```
window-screenshooter/
├── server.py              # Main MCP server implementation
├── windows_capture.py     # Windows-specific capture logic
├── linux_capture.py      # Linux-specific capture logic
├── test-mcp.py           # Test script for functionality
├── mcp-config-example.json # Example MCP configuration
├── pyproject.toml        # Project dependencies
└── README.md            # This file

Testing

Run the test script to verify functionality:bash python test-mcp.py

Common Issues

  1. "Window not found" errors:
    - Check exact window title with list_windows
    - Try partial title matching
    - Ensure window is visible and not minimized

  2. Permission errors on Windows:
    - Run as administrator if needed
    - Check Windows security settings

  3. Import errors:
    - Ensure all dependencies are installed: pip install pywinctl pillow pywin32
    - Check Python version (requires 3.12+)

Platform Compatibility

  • Windows: Full support with native Win32 API
  • Linux: Basic support with X11 integration

License

This project is licensed under the MIT License - see the LICENSE file for details.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Mcp Window Screenshooter 怎么安装?

在客户端按下面的安装命令接入:python server.py。装完在客户端配置里引用同一个包或端点。

Mcp Window Screenshooter 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Mcp Window Screenshooter 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Mcp Window Screenshooter 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Mcp Window Screenshooter 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Mcp Window Screenshooter 能提供哪些能力?

资料显示能力标签包括 screenshot capture、ai integration。具体工具清单以官方文档为准。

Mcp Window Screenshooter 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

Mcp Window Screenshooter 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。