# exec MCP server

> Provides bounded remote command execution and file transfer over SSH for trusted MCP clients.

- Repository: https://github.com/3011/exec-mcp
- Page: https://hostedmcp.org/servers/3011/exec-mcp
- Transport: —
- Stars: 0
- License: MIT

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `ALLOWED_CWDS` | no | no |  |
| `DEFAULT_CWD` | no | no |  |
| `NO_COLOR` | no | no |  |
| `REMOTE_HOST` | no | no |  |
| `REMOTE_KEY_PATH` | no | no |  |
| `REMOTE_KNOWN_HOSTS_PATH` | no | no |  |
| `REMOTE_STRICT_HOST_KEY_CHECKING` | no | no |  |
| `REMOTE_USER` | no | no |  |

## Tools (8)

- `begin_task`
- `exec`
- `start_exec`
- `list_active_execs`
- `get_exec_status`
- `cancel_exec`
- `import_chatgpt_file`
- `export_remote_file`

## FAQ

### Is this service secure for public networks?

No, it has no built-in user authentication or TLS termination and is designed for a trusted, single-tenant connection. You should put it behind an authenticated transport or reverse proxy.

### What shells are supported for command execution?

The service only supports 'sh' and 'bash'. No default shell is applied, and login or interactive shells are not used.

### When should I use 'exec' versus 'start_exec'?

Use 'exec' for short, deterministic commands that need immediate results (roughly five seconds or less). Use 'start_exec' for longer tasks like builds, tests, or scripts where work can continue in parallel.
