io.github.jaimenbell/desktop-mcp MCP Server
io.github.jaimenbell/desktop-mcp
What this kind of tool is for
- Chain multi-step workflows across the other tools in this directory.
- Run a scheduled or triggered job instead of retyping the same request.
- Have your agent watch a feed, queue, or repo and act on new items.
How to compare servers like this
- Trigger model:
- Understand what starts the automation — a command, a schedule, or an event — before relying on it.
- Blast radius:
- Prefer tools that hand you a review point before an irreversible action runs.
- Chaining cost:
- Each chained step adds a failure point; keep critical paths on the fewest tools.
- Maintenance signal:
- Automations break quietly; a maintained tool is the difference between repair and rediscovery.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.jaimenbell/desktop-mcp MCP server?
Windows desktop-control MCP server: screenshot, window mgmt, mouse/keyboard input, recording.
How to install io.github.jaimenbell/desktop-mcp
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"desktop-mcp": {
"command": "uvx",
"args": [
"desktop-mcp"
]
}
}
}Related MCP servers

MCP server for the Discord REST API: 5 read tools always on, 7 write tools env-gated, default off.

MCP server for the GitHub REST API: issues, PRs, repos; read always on, write env-gated.

Manifest-driven MCP server scaffolder and runtime hub for tool integrations.

Minimal RAG-over-a-corpus MCP retrieval: search_knowledge returns cited chunks. Local embeddings.

Default-deny action registry, append-only spend ledger, and human sign-off audit trail (MCP tools).
Read-only ops/health MCP server for a local vLLM instance: health tiers, GPU/VRAM, service status.