Server profile

wcgw MCP Server

wcgw equips MCP clients with an interactive shell and file-editing tools on a local machine. Developers can share the agent terminal, iterate on code, and save task context between chats.

Server facts

wcgw MCP Server

Project

Author
rusiaaman
License
Apache-2.0

Tech

Runtime / language
pythonPython
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
678
Last commit
Data as of

Tags

  • Claude
  • Code Editing
  • Python
  • Shell
  • Terminal

Overview

wcgw combines an interactive shell with code-reading and editing operations for MCP clients. It is designed for workflows where a conversational assistant runs commands, changes files, and checks results on the user's machine. Unlike a simple command runner, its shell supports interactive input, special keys, background commands, and shared terminal access. A VS Code extension can attach to that terminal, while screen provides another documented way for a person to watch or interact with the same session. Bash and zsh are supported shell choices.

File operations include incremental search-and-replace editing, large-file chunking, and syntax feedback after changes. A file must be read before the assistant can modify it. Initialization returns selected workspace structure and can load project or global instruction files. ContextSave preserves task information for continuation in another chat. Three modes organize usage: architect for investigation, code-writer for path-scoped edits, and the default unrestricted wcgw mode. These features do not turn the tool into a security sandbox. The README warns that shell and filesystem access can execute arbitrary commands, and says command allow-lists in code-writer mode are instructions rather than enforced checks. Installation uses uvx with Python 3.12; Windows operation requires WSL. It suits users who understand and accept the risks of a locally empowered coding agent.

Install & configure

Requirements

  • uv / uvx available to the MCP client
  • Python 3.12 for the documented launch
  • WSL on Windows
Documented launch / install command
uvx --python 3.12 wcgw@latest

The README documents this configuration for Claude Desktop. A --shell argument can select bash or zsh. Understand the unrestricted shell and file-access risks before running it.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.

Claude Desktop configuration
{
  "mcpServers": {
    "wcgw": {
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "wcgw@latest"
      ],
      "env": {}
    }
  }
}

Read the Claude Desktop setup guide

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.

Cursor configuration
{
  "mcpServers": {
    "wcgw": {
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "wcgw@latest"
      ],
      "env": {}
    }
  }
}

Read the Cursor setup guide

Config file · Workspace: .vscode/mcp.json

For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.

VS Code configuration
{
  "servers": {
    "wcgw": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "wcgw@latest"
      ],
      "env": {}
    }
  }
}

Read the VS Code setup guide

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.

Windsurf configuration
{
  "mcpServers": {
    "wcgw": {
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "wcgw@latest"
      ],
      "env": {}
    }
  }
}

Read the Windsurf setup guide

Config file · Project scope: .mcp.json at the repository root

The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.

Claude Code configuration
{
  "mcpServers": {
    "wcgw": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "wcgw@latest"
      ],
      "env": {}
    }
  }
}

Read the Claude Code setup guide

Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.

Tools

Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.

ToolWhat it does
InitializeSet up the shell and workspace, or resume saved task context.
BashCommandRun shell commands or send interactive input to the terminal.
ReadFilesRead one or more files into the assistant context.
WriteIfEmptyWrite a new file or populate an empty one.
FileEditModify a file using search-and-replace blocks.
ReadImageLoad an image file for inspection.
ContextSaveStore task context and relevant files for later continuation.

Names, permissions, and defaults can change. Check the current upstream documentation before granting access.

Use cases

  • Run compiler checks and iterate on code changes.
  • Share an interactive terminal with an assistant.
  • Edit large files through incremental replacements.
  • Save a task checkpoint and resume it in another chat.

Strengths

  • Interactive terminal supports keys and concurrent background commands.
  • File edits provide syntax feedback and require a prior read.
  • Context checkpoints support work across chats.

Limitations

  • Default mode gives unrestricted shell and filesystem access.
  • Code-writer command lists are not enforced allow-lists.
  • Windows requires WSL.

Frequently asked questions

Yes. The README describes VS Code attachment and shared access through screen.

No. The default wcgw mode allows unrestricted operations, and the README warns about arbitrary command execution.

The documented Windows setup requires WSL.

Yes. ContextSave records task information that Initialize can load when resuming a task.

Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.

Related MCP servers

MCP Advisor

Developer Tools

MCP Advisor helps assistants discover MCP servers from natural-language requests and obtain installation guidance. It combines registry providers with offline search and offers optional local Meilisearch integration.

Serena

Developer Tools

Serena gives coding agents symbol-aware retrieval, editing, refactoring, and debugging capabilities through MCP. It uses language servers or a JetBrains plugin to bring IDE-style code understanding to existing AI clients.

Context7

Developer Tools

Context7 retrieves current library documentation and code examples for AI coding assistants. It supports MCP tools or a CLI-and-skills workflow, with library IDs and version-aware requests helping narrow the documentation context.

FastAPI-MCP

Developer Tools

FastAPI-MCP exposes existing FastAPI endpoints as MCP tools while retaining schemas, endpoint documentation, and dependency-based authentication. It is a native extension for developers adding agent access to a FastAPI service.

GitMCP

Developer Tools

GitMCP turns public GitHub repositories and GitHub Pages projects into documentation sources for AI assistants. It offers repository-specific endpoints or a dynamic server for retrieving docs, searching code, and following referenced content.

XcodeBuildMCP

Developer Tools

XcodeBuildMCP provides an MCP server and CLI for AI agents working on iOS and macOS projects. One package supports direct terminal tools, simulator builds, and stateful operations such as debugging and log capture.

DevDocs by CyberAGI

Developer Tools

Crawl technical documentation into organized Markdown, JSON, and MCP-accessible content for development assistants. The public DevDocs repository is marked as not publicly maintained.

JetBrains MCP Proxy Server

Developer Tools

This legacy Node-based proxy connects MCP clients to a JetBrains IDE plugin. The repository is deprecated: IntelliJ-based IDEs include the core functionality from version 2025.2 onward.