🚀 DesktopCommanderMCP: Terminal Control for Claude

Created By
wtftya year ago
This is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities
Overview

What is DesktopCommanderMCP?

DesktopCommanderMCP is a server application designed for Claude that provides terminal control, file system search, and diff file editing capabilities, enhancing the coding experience and workflow efficiency.

How to use DesktopCommanderMCP?

To use DesktopCommanderMCP, download the latest release from the GitHub repository, install it, launch the application, connect it to Claude, and start executing commands or editing files through the terminal interface.

Key features of DesktopCommanderMCP?

  • Terminal Control: Execute commands directly from Claude.
  • File System Search: Quickly locate files within your system.
  • Diff File Editing: Compare and edit files with ease.
  • AI Integration: Utilize AI capabilities to enhance your coding.
  • Automation: Automate repetitive tasks with simple commands.

Use cases of DesktopCommanderMCP?

  1. Automating coding tasks through terminal commands.
  2. Searching for and managing files efficiently.
  3. Comparing and editing code files to track changes.

FAQ from DesktopCommanderMCP?

  • Is DesktopCommanderMCP free to use?

Yes! DesktopCommanderMCP is free to use for everyone.

  • What programming languages does it support?

DesktopCommanderMCP is designed to work with any programming language as it operates at the terminal level.

  • How can I contribute to the project?

You can contribute by forking the repository, making changes, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wtfty
Star
0
Language
TypeScript
License
MIT license

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)

a day ago