Clawd Cursor
About
The local MCP server that gives any AI agent safe desktop control. Drives Windows, macOS, and Linux GUIs through accessibility, OCR, or vision fallback. 6 compact compound tools covering 97 primitives. Model-agnostic. Local-only by default; bearer-token auth on HTTP; every tool c
Details
- Author
- AmrDab
- Downloads
- 525
- Categories
- Other, Automation, Developer Tools
Jump to
- Two MCP transports: stdio for editors, HTTP for daemons.
- Six compound tools (Anthropic computer_20250124-style) plus granular tools.
- Cheapest-tier-first pipeline: accessibility → OCR → screenshot → vision.
- Ground-truth verification with six independent signals and weighted voting.
- Reflector loop that emits structured failure causes and suggested strategies.
- Single safety chokepoint (safety.evaluate()) on every tool call.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Clawd CursorCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install via curl (macOS/Linux) or PowerShell (Windows). Run clawdcursor consent --accept for one-time desktop-control consent, then clawdcursor status to verify. For editor hosts (Claude Code, Cursor, Windsurf, Zed), use clawdcursor mcp as a stdio MCP server. For headless daemons, run clawdcursor agent (HTTP MCP on 127.0.0.1:3847). Wire the command into your host’s MCP configuration.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"clawd cursor": {
"clawdcursor": {
"command": "clawdcursor",
"args": [
"mcp",
"--compact"
]
}
}
}
}McpServers
{
"clawdcursor": {
"command": "clawdcursor",
"args": [
"mcp",
"--compact"
]
}
}Why Clawd Cursor
- Works where APIs don't exist. Native apps. Legacy enterprise tools. Web portals behind SSO that block headless browsers. Anything inside Citrix or RDP. If pixels reach the screen, your agent can drive it.
- Model-agnostic. Claude, GPT, Gemini, Llama, Kimi, anything local via Ollama — any tool-calling LLM. Text and vision can be different models from different vendors.
- App-agnostic. No per-app plugins, no per-service auth. The same six compound tools drive Outlook, Figma, your bank, and that 2003-era ERP.
- Cheapest-tier-first pipeline (for natural-language tasks). When you hand a whole instruction to the autonomous agent via task({...}) / submit_task, the planner starts at accessibility (free), escalates to OCR (cheap), then screenshot (medium), then vision (expensive). The Reflector feeds verifier signals back so the loop doesn't keep paying for vision when text would work. Direct tool calls (when your own agent loop drives the compound or granular tools) skip the pipeline and go straight to the requested tool — you bring the planning, clawdcursor brings the primitives.
- Local-only by default. Server binds to 127.0.0.1. Screenshots stay in RAM unless you point a cloud model at them. No telemetry.
- One protocol, two transports. MCP over stdio for editor hosts; MCP over HTTP for daemons. Same tool catalog, same JSON-RPC envelope.
When NOT to use it
Clawd Cursor is GUI control. It's slower than an API, less reliable than a script, and burns more tokens than a direct file edit. If a better path exists, take it:
| Better option | When |
|---|---|
| Native API (Gmail API, GitHub API, Stripe API, …) | The service has one. Use it. |
| CLI (git, gh, aws, npm, curl, sqlite3) | The work fits a shell tool. Use it. |
| Direct file edit | The data lives in a file you can write. Edit it. |
| Browser automation already wired up (Playwright, Puppeteer) for this exact site | Faster, more deterministic. Use it. |
Reach for Clawd Cursor when none of those apply — the legacy ERP with no REST, the Electron app whose dialog can't be scripted, the Excel macro behind a Citrix session. The pipeline pays the cheap costs first; if structured paths work it never escalates to vision. But the design point is the last mile, not the first call.
(SKILL.md enforces this as a hard 4-gate rule for AI agents calling the tool surface. Humans get the softer table above.)
---
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
