home / mcp / mcp pc control server
A powerful Model Context Protocol (MCP) server that provides comprehensive PC control capabilities including file operations, directory management, and command execution.
Configuration
View docs{
"mcpServers": {
"koopatroopa787-first_mcp": {
"command": "node",
"args": [
"/absolute/path/to/first_mcp/build/index.js"
]
}
}
}You can leverage the MCP PC Control Server to perform comprehensive PC management tasks over MCP. It enables file and directory operations, along with executing shell commands, all accessible through an MCP client for automation and remote control.
This MCP server exposes a set of tools for file, directory, and system operations. Use your MCP client to call these tools by name and pass the required parameters. The server runs as a local process and communicates via stdio, so you typically start it on your machine and connect with the client. You can run the server directly or point your MCP client at a prebuilt build to begin issuing operation requests.
Prerequisites: ensure you have Node.js installed on your system. You also need npm to install dependencies and build the project.
Clone or download the project to your workstation.
Navigate to the project directory and install dependencies.
npm installBuild the project to produce the runnable build artifacts.
npm run buildStart the server using the standard startup command shown by the build configuration.
npm startTo integrate with Claude Desktop, add the MCP server configuration into the Claude Desktop configuration file. You can run the server locally via stdio with a direct Node.js command or use npx for a quick inline start.
{
"mcpServers": {
"pc-control": {
"command": "node",
"args": ["/absolute/path/to/first_mcp/build/index.js"]
}
}
}This server provides powerful filesystem and command execution capabilities. Use it with trusted MCP clients only, run with the minimal necessary permissions, and consider additional access controls for production environments. Exercise caution with commands that execute in a shell, and audit operations in sensitive contexts.
If the server does not appear in your MCP client, ensure the configuration path is absolute and correct, confirm the build directory contains the expected index or entrypoint, and restart the client after changes. Check permissions on the filesystem and verify the working directory for shell commands exists and is accessible.
If you prefer running the server via npx, you can use a configuration like this in Claude Desktop:
{
"mcpServers": {
"pc-control": {
"command": "npx",
"args": ["-y", "mcp-pc-control-server"]
}
}
}Read complete file contents with proper encoding.
Create new files or overwrite existing ones.
Make precise line-based edits with diff output.
Remove files from the filesystem.
Move or rename files and directories.
Get detailed file metadata (size, timestamps, permissions).
Create directories (supports nested creation).
List directory contents with detailed information.
Recursively delete directories and their contents.
Recursively search for files matching patterns.
Execute shell commands with optional working directory.