Computer Use

Created By
spencerkinneya year ago
Control virtual computers through the Model Context Protocol (MCP).
Overview

what is Computer Use MCP?

Computer Use MCP is a server that allows users to control virtual computers through the Model Context Protocol (MCP), enabling the creation of cloud desktop environments for Computer Use Agents (CUA).

how to use Computer Use MCP?

To use Computer Use MCP, install the necessary dependencies, obtain API keys from Orgo and Anthropic, and run the server. You can then interact with the server using a test client to perform various actions on the virtual computer.

key features of Computer Use MCP?

  • Control virtual computers via API calls
  • Perform mouse and keyboard actions programmatically
  • Take screenshots and manage computer lifecycle
  • Integrate with Claude AI for advanced computer use

use cases of Computer Use MCP?

  1. Automating tasks on virtual desktops
  2. Running tests on cloud-based applications
  3. Providing remote assistance through virtual environments

FAQ from Computer Use MCP?

  • What programming language is required?

Python 3.8 or higher is required to run the server and client.

  • Do I need API keys?

Yes, you need to sign up for Orgo and Anthropic to obtain the necessary API keys.

  • Can I run this on my local machine?

Yes, the server can be run locally on your machine.

Server Config

{
  "mcpServers": {
    "computer-use-mcp": {
      "command": "python",
      "args": [
        "computer_mcp_server.py"
      ],
      "env": {
        "ORGO_API_KEY": "your_orgo_key_here",
        "ANTHROPIC_API_KEY": "your_anthropic_key_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
spencerkinney
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago