Screenshot vs Ui.Vision MCP

A side-by-side look at the Screenshot and Ui.Vision MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

S
ScreenshotBrowser Automation
Screenshot any URL/HTML as PNG/JPEG/WebP, or read it as clean Markdown/text for LLMs.12EmergingAuth: not declared
Ui.Vision MCP logoUi.Vision MCPBrowser Automation · Local subprocess (stdio)MCP server for browser and desktop automation: OCR, image recognition, real mouse and keyboard input52GoodAuth: not declared

Verdict: choose Screenshot for browser automation work; choose Ui.Vision MCP for browser automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

S
Choose Screenshot when

  • You need dedicated capabilities in the Browser Automation domain.
Explore Screenshot

Ui.Vision MCP logoChoose Ui.Vision MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
Explore Ui.Vision MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
S
Screenshot
Ui.Vision MCP logoUi.Vision MCP
CategoryBrowser AutomationBrowser Automation
Quality signal12/100 · Emerging52/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—2,086
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Screenshot tools

No tool names declared yet. Check the project README from the listing page.

Ui.Vision MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Screenshot

No confirmed install command for Screenshot yet — follow the setup steps linked from its listing page rather than a guessed package name.

Ui.Vision MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ui-vision-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "uivision-mcp-bridge"
      ]
    }
  }
}

Frequently asked questions

Screenshot is categorized under Browser Automation and uses an install path we have not confirmed yet. Ui.Vision MCP belongs to Browser Automation and uses a local stdio subprocess. Pick Screenshot for browser automation work and Ui.Vision MCP for browser automation.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Screenshot has no confirmed install command yet — follow its own setup instructions.

Screenshot has no declared pricing — check the project's own site. Ui.Vision MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add screenshot and ui-vision-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Screenshot has a quality signal of 12/100 (Emerging) with 1 views, 0 installs and 0 GitHub stars. Ui.Vision MCP has 52/100 (Good) with 2 views, 0 installs and 2,086 GitHub stars.