Skip to content

Add ScreenHand — desktop + browser automation MCP server#21

Open
manushi4 wants to merge 1 commit intojmanhype:mainfrom
manushi4:add-screenhand
Open

Add ScreenHand — desktop + browser automation MCP server#21
manushi4 wants to merge 1 commit intojmanhype:mainfrom
manushi4:add-screenhand

Conversation

@manushi4
Copy link
Copy Markdown

@manushi4 manushi4 commented Mar 7, 2026

Adds ScreenHand to the MCP Servers section.

ScreenHand gives Claude Code native desktop control + browser automation via 82 MCP tools:

  • Accessibility APIs (macOS Swift / Windows C#)
  • Chrome DevTools Protocol with anti-detection
  • Memory, jobs, supervisor, and reusable playbooks for 10 platforms

GitHub | npm

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@qodo-code-review
Copy link
Copy Markdown

Review Summary by Qodo

Add ScreenHand MCP server to documentation

📝 Documentation

Grey Divider

Walkthroughs

Description
• Add ScreenHand MCP server to documentation
• Highlights desktop automation and browser control capabilities
• Lists 82 available tools and supported platforms
Diagram
flowchart LR
  README["README.md"] -- "Add ScreenHand entry" --> MCP["MCP Servers List"]
  MCP -- "Desktop + Browser Automation" --> Tools["82 Tools Available"]
Loading

Grey Divider

File Changes

1. README.md 📝 Documentation +1/-0

Add ScreenHand MCP server documentation entry

• Added ScreenHand entry to MCP Servers section
• Describes native desktop and browser automation capabilities
• References GitHub repository and npm package
• Highlights accessibility APIs and Chrome DevTools Protocol support

README.md


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Copy Markdown

qodo-code-review bot commented Mar 7, 2026

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider


Remediation recommended

1. Verbose README bullet 🐞 Bug ⛯ Reliability
Description
The new ScreenHand MCP Servers bullet uses a two-sentence, comparatively long description, which
conflicts with the repo’s guidance to keep descriptions “short and simple” and may increase the
chance of awesome-lint/maintainer feedback on formatting consistency.
Code

README.md[27]

+- [ScreenHand](https://github.com/manushi4/Screenhand) - Native desktop + browser automation MCP server with 82 tools. Gives Claude Code eyes and hands on the desktop via accessibility APIs (macOS/Windows) and Chrome DevTools Protocol.
Evidence
Contribution guidelines explicitly request the [Title](link) - Description. format and ask to keep
descriptions short/simple; the added entry is noticeably longer and is the only MCP Server bullet in
this snippet that is two sentences. CI also runs npx awesome-lint, so formatting consistency
matters for PR acceptance.

contributing.md[7-10]
README.md[22-28]
.github/workflows/ci.yml[6-12]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The ScreenHand entry’s description is longer than surrounding entries and is written as two sentences, which conflicts with the repository guidance to keep descriptions short and simple.

### Issue Context
This repo runs `npx awesome-lint` in CI and has contribution guidelines that specify a standard bullet format and concise descriptions.

### Fix Focus Areas
- README.md[27-27]

Suggested rewrite (example):
`- [ScreenHand](https://github.com/manushi4/Screenhand) - Native desktop + browser automation MCP server (82 tools) via macOS/Windows accessibility APIs and Chrome DevTools Protocol.`

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant