deployment-mcp
Allows to run git pull on a remote host, enabling automated deployment of code updates from a Git repository.
Enables execution of npm commands (e.g., install, run build) on remote hosts as part of deployment scripts.
Supports restarting PM2 process manager on remote servers, used for managing Node.js application processes during deployment.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@deployment-mcp Pull latest code on my-app server using SSH"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
deployment-mcp
An MCP (Model Context Protocol) server that handles deployment operations over SSH.
Features
ssh_git_pull– SSH into a remote host and rungit pullin a specified repository directory.ssh_run_command– Execute an arbitrary shell command on a remote host and return its stdout, stderr and exit code.ssh_run_script– Upload and execute a multi-line shell script on a remote host (piped to bash; no temporary files created locally).write_ssh_config– Write or update aHostentry in the local~/.ssh/configfile.
All SSH tools support authentication via an inline PEM private key, a path to a key file, or a password.
Related MCP server: MCP SSH Server
Installation
npm install
npm run buildUsage
Run the MCP server over stdio (used by MCP-compatible AI clients):
node dist/index.jsMCP client configuration example
{
"mcpServers": {
"deployment": {
"command": "node",
"args": ["/path/to/deployment-mcp/dist/index.js"]
}
}
}Tool examples
ssh_git_pull
{
"host": "my-server.example.com",
"username": "deploy",
"privateKeyPath": "~/.ssh/id_rsa",
"repoPath": "/var/www/myapp",
"branch": "main"
}ssh_run_command
{
"host": "my-server.example.com",
"username": "deploy",
"privateKeyPath": "~/.ssh/id_rsa",
"command": "systemctl restart myapp"
}ssh_run_script
{
"host": "my-server.example.com",
"username": "deploy",
"privateKeyPath": "~/.ssh/id_rsa",
"workingDirectory": "/var/www/myapp",
"script": "#!/bin/bash\nset -e\ngit pull\nnpm install --omit=dev\nnpm run build\npm2 restart myapp"
}write_ssh_config
{
"alias": "my-server",
"hostname": "my-server.example.com",
"user": "deploy",
"identityFile": "~/.ssh/deploy_key",
"extraOptions": {
"StrictHostKeyChecking": "no",
"ServerAliveInterval": "60"
}
}Development
npm run dev # TypeScript watch mode
npm test # Run tests
npm run build # Compile TypeScriptAvailable Tools
4 toolsssh_git_pullB
SSH into a remote host and run git pull in the specified repository directory. Supports authentication via private key (PEM string or file path) or password.
Inputs: host (required), repoPath (required), username (required), port, +5 more.
ssh_run_commandB
SSH into a remote host and run an arbitrary shell command. Returns stdout, stderr and the exit code.
Inputs: host (required), command (required), username (required), port, +4 more.
ssh_run_scriptA
SSH into a remote host and execute a multi-line shell script. The script content is piped to bash remotely; no temporary files are created locally.
Inputs: host (required), script (required), username (required), port, +5 more.
write_ssh_configA
Write (or update) a Host entry in the local ~/.ssh/config file. If an entry with the same alias already exists it is replaced. Useful for setting up SSH config before running deployment commands.
Inputs: user (required), alias (required), hostname (required), port, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Tools are mostly distinct: git pull, command execution, script execution, and SSH config writing each target different actions. Some overlap between run_command and run_script but descriptions clarify the difference.
All tools use snake_case with ssh_ prefix, following a verb_noun pattern. `ssh_git_pull` is slightly inconsistent (compound verb) but overall pattern is predictable.
Four tools is a reasonable scope for a focused deployment server covering SSH execution and config. Could be expanded but not overly sparse.
Lacks critical deployment operations like file transfer (scp/rsync), service management, or environment setup. The set is too limited for typical deployment workflows.
Related MCP Connectors
Manage servers through SSH.
Manage remote servers, SSH terminals, files, databases and proxies with scoped access and approvals.
Scoped, audited SSH exec, sessions, and SFTP on your saved servers without exposing credentials
Deploy services, add databases, run agents, read logs, check vulnerabilities and publish pages.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables SSH operations including connecting to remote servers, executing commands, and transferring files between local and remote systems. Supports multiple SSH connections with both password and private key authentication methods.18MIT
- AlicenseBqualityDmaintenanceEnables seamless SSH operations including secure connections, file transfers, interactive shell sessions, and Docker container management on remote servers. Supports both password and SSH key authentication with credential management and connection pooling.18MIT
- AlicenseBqualityDmaintenanceEnables secure remote and local command execution via SSH, with session management and environment variable support.145 npm3MIT
- AlicenseCqualityDmaintenanceEnables SSH remote command execution on remote machines with persistent connections, supporting automatic key discovery and connection pooling.2156 npmMIT