Mcpcontrol Ae8b5b37

MCPAI代理

提供方 未标注

AI代理 stdio · 本地进程 未标注 社区 / 第三方
查看接入方式

全面解析McpcontrolMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,Mcpcontrol能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

Mcpcontrol Ae8b5b37 属于AI代理类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
npx mcp-control\"

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

  1. 1
    准备运行环境

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Mcpcontrol Ae8b5b37当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

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

详细介绍

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

MCPControl

Windows control server for the Model Context Protocol, providing programmatic control over system operations including mouse, keyboard, window management, and screen capture functionality.

> Note: This project currently supports Windows only.

🔥 Why MCPControl?

MCPControl bridges the gap between AI models and your desktop, enabling secure, programmatic control of:

  • 🖱️ Mouse movements and clicks
  • ⌨️ Keyboard input and shortcuts
  • 🪟 Window management
  • 📸 Screen capture and analysis
  • 📋 Clipboard operations

🔌 Quick Start

Prerequisites

  1. Install Build Tools (including VC++ workload)powershell # Run as Administrator - may take a few minutes to complete winget install Microsoft.VisualStudio.2022.BuildTools --override "--wait --passive --add Microsoft.VisualStudio.Workload.VCTools --includeRecommended"

  2. Install Python (if not already installed)powershell # Install Python (required for node-gyp) winget install Python.Python.3.12

  3. Install Node.jspowershell # Install latest LTS version winget install OpenJS.NodeJS

Installation

  1. Install MCPControl Packagepowershell npm install -g mcp-control

Configuration

MCPControl works best in a virtual machine at 1280x720 resolution for optimal click accuracy.

Configure your Claude client to connect to MCPControl via SSE transport:

Option 1: Direct SSE Connection

For connecting to an MCPControl server running on a VM or remote machine:```json
{
"mcpServers": {
"MCPControl": {
"transport": "sse",
"url": "http://192.168.1.100:3232/mcp"
}
}
}


Replace `192.168.1.100:3232` with your server's IP address and port.

#### Option 2: Local Launch with SSE

To launch MCPControl locally with SSE transport:```json
{
  "mcpServers": {
    "MCPControl": {
      "command": "mcp-control",
      "args": ["--sse"]
    }
  }
}

Starting the Server

First, start the MCPControl server on your VM or local machine:```bash
mcp-control --sse


The server will display:
- Available network interfaces and their IP addresses
- The port number (default: 3232)
- Connection status messages

### VM Setup Example

1. **Start your Windows VM** with 1280x720 resolution
2. **Install MCPControl** on the VM:```bash
   npm install -g mcp-control
   ```
3. **Run the server** with SSE transport:```bash
   mcp-control --sse
   ```
4. **Note the VM's IP address** (e.g., `192.168.1.100`)
5. **Configure Claude** with the SSE URL:```json
   {
     "mcpServers": {
       "MCPControl": {
         "transport": "sse",
         "url": "http://192.168.1.100:3232/mcp"
       }
     }
   }
   ```
6. **Restart Claude** and MCPControl will appear in your MCP menu!

## 🔧 CLI Options

MCPControl supports several command-line flags for advanced configurations:```bash
# Run with SSE transport on default port (3232)
mcp-control --sse

# Run with SSE on custom port
mcp-control --sse --port 3000

# Run with HTTPS/TLS (required for production deployments)
mcp-control --sse --https --cert /path/to/cert.pem --key /path/to/key.pem

# Run with HTTPS on custom port
mcp-control --sse --https --port 8443 --cert /path/to/cert.pem --key /path/to/key.pem

Command Line Arguments

  • --sse - Enable SSE (Server-Sent Events) transport for network access
  • --port [number] - Specify custom port (default: 3232)
  • --https - Enable HTTPS/TLS (required for remote deployments per MCP spec)
  • --cert [path] - Path to TLS certificate file (required with --https)
  • --key [path] - Path to TLS private key file (required with --https)

Security Note

According to the MCP specification, HTTPS is mandatory for all HTTP-based transports in production environments. When deploying MCPControl for remote access, always use the --https flag with valid TLS certificates.

🚀 Popular Use Cases

Assisted Automation

  • Application Testing: Delegate repetitive UI testing to Claude, allowing AI to navigate through applications and report issues
  • Workflow Automation: Have Claude operate applications on your behalf, handling repetitive tasks while you focus on creative work
  • Form Filling: Let Claude handle data entry tasks with your supervision

AI Experimentation

  • AI Gaming: Watch Claude learn to play simple games through visual feedback
  • Visual Reasoning: Test Claude's ability to navigate visual interfaces and solve visual puzzles
  • Human-AI Collaboration: Explore new interaction paradigms where Claude can see your screen and help with complex tasks

Development and Testing

  • Cross-Application Integration: Bridge applications that don't normally communicate
  • UI Testing Framework: Create robust testing scenarios with visual validation
  • Demo Creation: Automate the creation of product demonstrations

⚠️ IMPORTANT DISCLAIMER

THIS SOFTWARE IS EXPERIMENTAL AND POTENTIALLY DANGEROUS

By using this software, you acknowledge and accept that:

  • Giving AI models direct control over your computer through this tool is inherently risky
  • This software can control your mouse, keyboard, and other system functions which could potentially cause unintended consequences
  • You are using this software entirely at your own risk
  • The creators and contributors of this project accept NO responsibility for any damage, data loss, or other consequences that may arise from using this software
  • This tool should only be used in controlled environments with appropriate safety measures in place

USE AT YOUR OWN RISK

🌟 Features

🪟 Window Management

  • List all windows

  • Get active window info

  • Focus, resize & reposition

🖱️ Mouse Control

  • Precision movement

  • Click & drag operations

  • Scrolling & position tracking

⌨️ Keyboard Control

  • Text input & key combos

  • Key press/release control

  • Hold key functionality

📸 Screen Operations

  • High-quality screenshots

  • Screen size detection

  • Active window capture

🔧 Automation Providers

MCPControl supports multiple automation providers for different use cases:

  • keysender (default) - Native Windows automation with high reliability
  • powershell - Windows PowerShell-based automation for simpler operations
  • autohotkey - AutoHotkey v2 scripting for advanced automation needs

Provider Configuration

You can configure the automation provider using environment variables:```bash

Use a specific provider for all operations

export AUTOMATION_PROVIDER=autohotkey

Configure AutoHotkey executable path (if not in PATH)

export AUTOHOTKEY_PATH="C:\Program Files\AutoHotkey\v2\AutoHotkey.exe"


Or use modular configuration for specific operations:```bash
# Mix and match providers for different operations
export AUTOMATION_KEYBOARD_PROVIDER=autohotkey
export AUTOMATION_MOUSE_PROVIDER=keysender
export AUTOMATION_SCREEN_PROVIDER=keysender
export AUTOMATION_CLIPBOARD_PROVIDER=powershell

See provider-specific documentation:
- AutoHotkey Provider

🛠️ Development Setup

If you're interested in contributing or building from source, please see CONTRIBUTING.md for detailed instructions.

Development Requirements

To build this project for development, you'll need:

  1. Windows operating system (required for the keysender dependency)
  2. Node.js 18 or later (install using the official Windows installer which includes build tools)
  3. npm package manager
  4. Native build tools:
    - node-gyp: npm install -g node-gyp
    - cmake-js: npm install -g cmake-js

The keysender dependency relies on Windows-specific native modules that require these build tools.

📋 Project Structure

  • /src
  • /handlers - Request handlers and tool management
  • /tools - Core functionality implementations
  • /types - TypeScript type definitions
  • index.ts - Main application entry point

🔖 Repository Branches

  • main - Main development branch with the latest features and changes
  • release - Stable release branch that mirrors the latest stable tag (currently v0.2.0)

Version Installation

You can install specific versions of MCPControl using npm:```bash

Install the latest stable release (from release branch)

npm install mcp-control

Install a specific version

npm install mcp-control@0.1.22
```

📚 Dependencies

  • @modelcontextprotocol/sdk - MCP SDK for protocol implementation
  • keysender - Windows-only UI automation library
  • clipboardy - Clipboard handling
  • sharp - Image processing
  • uuid - UUID generation

🚧 Known Limitations

  • Window minimize/restore operations are currently unsupported
  • Multiple screen functions may not work as expected, depending on setup
  • The get_screenshot utility does not work with the VS Code Extension Cline. See GitHub issue #1865
  • Some operations may require elevated permissions depending on the target application
  • Only Windows is supported
  • MCPControl works best at 1280x720 resolution, single screen. Click accuracy is optimized for this resolution. We're working on an offset/scaling bug and looking for testers or help creating testing tools

👥 Contributing

See CONTRIBUTING.md

⚖️ License

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

📖 References

  • Model Context Protocol Documentation

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Mcpcontrol Ae8b5b37 怎么安装?

在客户端按下面的安装命令接入:npx mcp-control\"。装完在客户端配置里引用同一个包或端点。

Mcpcontrol Ae8b5b37 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Mcpcontrol Ae8b5b37 收费吗?

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

Mcpcontrol Ae8b5b37 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Mcpcontrol Ae8b5b37 能提供哪些能力?

资料显示能力标签包括 JavaScript、AI自动化、AI代理。具体工具清单以官方文档为准。

Mcpcontrol Ae8b5b37 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

Mcpcontrol Ae8b5b37 是本地还是远程?

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

热门专题

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

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