Desktop Commander

Created By
wonderwhy-era year ago
Run & Manage Long Processes - install, scrap, encode video, compile Search & Read & Edit files - including diff editing for speed and precision
Overview

what is Claude Computer Commander?

Claude Computer Commander is a terminal server that allows the Claude AI to execute commands on your local computer and manage system processes through the Model Context Protocol (MCP).

how to use Claude Computer Commander?

To use the server, clone the repository and run the setup script. Start the Claude application to gain access to terminal command execution.

key features of Claude Computer Commander?

  • Execute terminal commands with output streaming and configurable timeouts
  • Background execution support for long-running processes
  • Process and session management including listing and killing processes

use cases of Claude Computer Commander?

  1. Automating command executions on your local machine
  2. Monitoring and managing system processes using AI
  3. Facilitating complex workflows that require command line interactions

FAQ from Claude Computer Commander?

  • Can Claude execute any command?

Yes, Claude can execute any terminal command that the current user has permissions for.

  • Is Claude Computer Commander open source?

Yes, it is available on GitHub under the MIT license.

  • How does it integrate with Claude’s desktop application?

The server communicates with Claude through the Model Context Protocol, enabling local command executions.

Project Info
Created At
a year ago
Updated At
9 months ago
Author Name
wonderwhy-er
Star
58
Language
TypeScript
License
MIT license
Category

Recommend Servers

View All
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)

2 days ago