MCP Remote Access
This server provides SSH and serial/UART remote access to embedded devices, exposing 24 tools for AI agents, IDEs, and terminals to control lab equipment programmatically.
SSH Capabilities
Connect to remote hosts using password or private key authentication
Execute commands synchronously (stdout, stderr, exit codes) or asynchronously in the background
Poll background job status/output via job IDs; list all active background tasks
Upload and download files via SFTP
List and disconnect active SSH connections
Serial/UART Capabilities
List available serial ports with VID/PID, serial number, and description metadata
Connect by port name (e.g.,
/dev/ttyUSB0,COM3) or by matching VID/PID/serial/description to avoid hardcoded pathsESP32-aware connection with automatic BOOT/RESET sequencing and auto-baud handling
Send data with configurable line endings; read incoming data with configurable timeout and byte limits
Wait for specific patterns in the serial output stream (
serial_wait_for)Run expect/send sequences for login prompts, AT command flows, and bootloader handshakes (
serial_expect)Set DTR/RTS line states; reset devices using ESP32, STM32, or generic DTR/RTS pulse methods
Send break signals (e.g., to interrupt U-Boot) and flush serial buffers
List and disconnect active serial connections
Security & Integration
SSH credentials held in memory only — no persistent on-disk session store
Communicates via stdio, accepting connections from the local MCP client only
Designed for lab-automation and embedded-bringup workflows (bootloader interaction, image flashing, device bring-up)
Enables SSH connections to Raspberry Pi devices for remote command execution and file transfers via SFTP
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., "@MCP Remote Access connect to my Raspberry Pi at 192.168.1.100 with username pi"
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.
Authorized security testing only. See DISCLAIMER.md.
SSH and serial-port control for embedded devices, exposed as MCP tools. Log into a Raspberry Pi, talk to a UART, drive a USB-CDC console from your assistant.
Quick start · Tools · Workflows · Documentation
What is mcp-remote-access?
mcp-remote-access is an MCP server that exposes SSH (over paramiko)
and serial / UART (over pyserial) as MCP tools. Once it's running,
an agent can log into a host over SSH, run commands, transfer files,
open a serial console, send AT-style command sequences, and reset a
device over DTR/RTS.
It's deliberately thin: 26 tools, two transports, no orchestration language. Higher-level workflow logic lives in the agent's prompts, not in this server.
A few things it handles that are easy to get wrong by hand:
Connect to a serial port by VID/PID/serial number/description instead of guessing
/dev/ttyUSB0vs/dev/ttyUSB1(serial_connect_match).Long-running SSH commands (builds,
tcpdump, test runs) don't block the MCP channel:ssh_execute_backgroundreturns a task ID,ssh_check_backgroundpolls it.serial_expect/serial_wait_forwait for a real pattern in the stream instead of a fixedsleep(), which avoids the usual "sent before the prompt was ready" race on login prompts and AT flows.DTR/RTS control for hard-resetting MCUs over USB-serial, plus break-signal support.
SSH passwords are held in memory only and cleared on disconnect; no on-disk session store.
Related MCP server: MCP SSH Server with Streamable HTTP
Quick start
Install
git clone https://github.com/RFingAdam/mcp-remote-access.git
cd mcp-remote-access
uv pip install -e .Run it
The server speaks MCP over stdio:
uv run --directory /path/to/mcp-remote-access mcp-remote-accessAdd it to an MCP client
Codex CLI:
codex mcp add remote-access -- \
uv run --directory /path/to/mcp-remote-access mcp-remote-accessClaude Code:
claude mcp add remote-access -- \
uv run --directory /path/to/mcp-remote-access mcp-remote-accessOr add it to a client config file directly:
{
"mcpServers": {
"remote-access": {
"command": "uv",
"args": ["run", "--directory", "/path/to/mcp-remote-access", "mcp-remote-access"]
}
}
}Then, from the assistant:
"Connect to my Pi at vpn-ap.local as
pi(passwordraspberry), rununame -a, thendmesg | tail -20."
That's ssh_connect followed by two ssh_execute calls.
Tools
26 MCP tools across two transports. Full reference in docs/tools.md.
SSH (9)
Tool | Purpose |
| Connect to a host via SSH (password or key auth) |
| Run a command on a connected host (sync) |
| Run a long-running command async, returns |
| Check status / collect output of a background command |
| List all active background commands |
| Upload a file via SFTP |
| Download a file via SFTP |
| Close an SSH connection |
| Show active SSH connections |
Serial / UART (17)
Tool | Purpose |
| List available serial ports (with VID/PID, description, serial #) |
| Connect by port name |
| Connect by VID / PID / serial / description match |
| ESP32-aware connect (BOOT/RESET sequence, auto-baud) |
| Send text data (with optional response read + configurable line ending) |
| Send raw bytes as hex (binary protocols: Nordic DTM, HCI, etc.) |
| Read available data |
| Read raw bytes back as hex |
| Wait for a pattern in the incoming stream |
| Wait/send step sequences (login prompts, AT flows) |
| Send a break signal |
| Set DTR line state |
| Set RTS line state |
| Reset device via DTR/RTS sequence |
| Flush serial buffers |
| Close a serial connection |
| Show active serial connections |
Workflows
mcp-remote-access fits in the following eng-mcp-suite
workflow bundles:
lab-automation: pair withmcp-rs-spectrum-analyzer,mcp-rs-siggen,copper-mountain-vna-mcpto fully script a bench (DUT login over SSH or UART, lab gear over SCPI).embedded-bringup:serial_connect_match+serial_expect+ssh_uploadfor boot-loader interaction and image flashing.
Part of eng-mcp-suite.
Use in the lab-automation workflow bundle.
See the suite manifest for the full list of sibling MCPs and bundle definitions.
Documentation
Quick Start: install through first call.
Tool reference. Every MCP tool, every argument.
Usage examples: practical end-to-end walkthroughs.
Architecture: how this MCP fits in eng-mcp-suite.
Part of eng-mcp-suite
This server is one piece of eng-mcp-suite, an umbrella of engineering MCP servers covering RF, EMC, PCB, signal integrity, EM simulation, and lab test. See the full catalog or jump to a sibling:
Domain | Sibling MCPs |
RF / Transmission lines | |
EMC regulatory | |
PCB / SI | mcp-pcb-emcopilot (private: public soon) |
EM simulation | mcp-openems, mcp-nec2-antenna (private: public soon) |
Diagrams | |
3D / rendering | |
Remote access | mcp-remote-access (this repo) |
Lab gear | copper-mountain-vna-mcp, mcp-rs-spectrum-analyzer, mcp-rs-siggen, mcp-rs-cmw500 |
Security notes
SSH passwords are kept in memory only and cleared on server restart.
Connections are session-scoped; the server does not persist a session store on disk.
Use SSH keys where possible.
The MCP server runs over stdio. It only accepts connections from the local MCP client, never from the network.
Troubleshooting
SSH connection issues: verify the host is reachable
(ping vpn-ap.local), that SSH is listening on the target
(ssh pi@vpn-ap.local from the same shell), and that credentials are
correct.
Serial port issues. Check port permissions
(ls -la /dev/ttyUSB*), add your user to the dialout group
(sudo usermod -a -G dialout $USER and re-login), and confirm the
device is present (dmesg | tail).
VID/PID match selects wrong device: serial_connect_match returns
the first hit; pair the match on description or serial_number to
disambiguate.
Contributing
Contributions are welcome.
Pick a GitHub issue.
Fork + branch (
feature/your-thingorfix/your-bug).Run tests (
uv run pytest) if present.Open a PR: link the issue, request review.
License
AGPL-3.0-or-later. Relicensed from Apache-2.0 in v0.2.0 to align with the eng-mcp-suite toolkit-wide AGPL move.
Brand assets
The project name and the logo files in this repository are not part of the licensed work. The licence above grants no permission to use them, except as needed to describe the origin of the work.
Acknowledgments
paramiko: SSH transport.
pyserial: serial / UART transport.
The MCP working group: for the Model Context Protocol specification.
Part of eng-mcp-suite.
Available Tools
24 toolsserial_connectC
Connect to a serial port. Returns a connection ID.
Inputs: port (required), baudrate, timeout.
serial_connect_matchB
Connect to a serial port by matching VID/PID/serial/description. Returns a connection ID.
Inputs: vid, pid, serial_number, description_contains, +4 more.
serial_disconnectC
Close a serial port connection.
Inputs: connection_id (required).
serial_esp32_connectA
Connect to ESP32 with automatic reset and boot wait. Handles the ESP32 boot sequence (74880 baud boot messages, then app at 115200). Resets the device and waits for it to be ready.
Inputs: port (required), baudrate, reset, wait_for_boot, +2 more.
serial_expectC
Wait for patterns and optionally send responses. Useful for login prompts and AT flows.
Inputs: connection_id (required), steps (required), flush_input, default_timeout, +1 more.
serial_flushA
Flush serial buffers (clear pending input/output data).
Inputs: connection_id (required), input, output.
serial_list_connectionsB
List all active serial connections.
Inputs: no named parameters.
serial_list_portsB
List available serial ports on the system.
Inputs: no named parameters.
serial_readC
Read available data from a serial port.
Inputs: connection_id (required), timeout, bytes.
serial_reset_deviceA
Reset an embedded device using DTR/RTS sequence. Supports ESP32, STM32, and generic reset.
Inputs: connection_id (required), method.
serial_sendB
Send data to a serial port. Optionally wait for and return response.
Inputs: connection_id (required), data (required), raw, line_ending, +2 more.
serial_send_breakA
Send a serial break signal. Used to interrupt U-Boot, enter debug modes.
Inputs: connection_id (required), duration.
serial_set_dtrB
Set DTR (Data Terminal Ready) line state. Used for device reset on many boards.
Inputs: connection_id (required), state (required).
serial_set_rtsB
Set RTS (Request To Send) line state. Used for bootloader entry on ESP32/STM32.
Inputs: connection_id (required), state (required).
serial_wait_forB
Wait for a specific string/pattern in serial output. Useful for boot messages, prompts.
Inputs: connection_id (required), pattern (required), timeout.
ssh_check_backgroundA
Check status and get output from a background command. Returns whether it's still running and the latest output.
Inputs: task_id (required), tail_lines.
ssh_connectA
Connect to a remote host via SSH. Returns a connection ID for subsequent commands.
Inputs: host (required), username (required), password, key_path, +1 more.
ssh_disconnectC
Close an SSH connection.
Inputs: connection_id (required).
ssh_downloadB
Download a file from the remote host via SFTP.
Inputs: local_path (required), remote_path (required), connection_id (required).
ssh_executeB
Execute a command on a connected SSH host. Returns stdout, stderr, and exit code.
Inputs: connection_id (required), command (required), timeout.
ssh_execute_backgroundA
Execute a long-running command in the background. Returns a task ID and output file path. Use ssh_check_background to monitor progress.
Inputs: command (required), connection_id (required).
ssh_list_backgroundB
List all background tasks and their status.
Inputs: no named parameters.
ssh_list_connectionsB
List all active SSH connections.
Inputs: no named parameters.
ssh_uploadB
Upload a file to the remote host via SFTP.
Inputs: local_path (required), remote_path (required), connection_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 24 tools
The SSH and serial tool groups are clearly separated by prefix, and within each group the actions are distinct (connect, execute, disconnect, list, etc.). The only minor ambiguity is between serial_expect and serial_wait_for, which both wait for patterns, though expect adds optional response sending.
Most tools follow a consistent transport_verb pattern (ssh_connect, serial_send, serial_disconnect). Minor deviations include serial_connect_match and serial_esp32_connect, which are more specific but still readable and consistent with the overall convention.
24 tools is on the higher end but justified by covering two distinct transports (SSH and serial) with connection lifecycle, data operations, and device-specific helpers. A few tools like serial_flush and serial_read could potentially be merged, but the count is not excessive for the scope.
The tool set covers the full lifecycle for both SSH (connect, execute, background, upload/download, disconnect) and serial (connect, send, read, expect, reset, disconnect). Minor gaps include no SSH port forwarding or serial line settings (baud/parity) configuration, but core remote access workflows are well covered.
Maintenance
Related MCP Connectors
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Use your Mac, Windows or Linux computer from ChatGPT, Claude or Codex: files, commands, documents.
Give your AI hands on every computer you own. Remote control of your Windows, Mac and Linux machines from one ChatGPT, Claude or Cursor chat — even from your phone. Ask it to find out why the office server is crawling, update every PC in the house, sort out your mom's laptop from another city, or ship the site from your work machine while you're on a train. It runs commands, reads files and takes a screenshot when it needs to see the screen. You decide what each computer allows, and you can cut any of them off in a second.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables SSH remote access to servers through Claude, allowing users to execute commands, transfer files via SFTP, and manage multiple remote connections using natural language.129MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables remote server control via SSH through Claude, supporting command execution, file transfers, and multi-server management with both standard and streamable HTTP protocols.-
- AlicenseAqualityDmaintenanceEnables Claude to connect to servers via SSH, execute commands, transfer files, and manage connections through natural language.916 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to interact with network devices over serial and SSH with command safety classification and a persistent knowledge base.MIT