Board Terminal Skill
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., "@Board Terminal Skill run 'cat /proc/cpuinfo' on the dev board"
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.
Board Terminal Skill
MCP server exposing one tool, board_terminal, for running shell commands on a Linux development board through a controlled executor.
The first backend is UART serial. SSH is represented by a placeholder interface so it can be added without changing the MCP tool contract.
Tool
Input:
{
"command": "cat /proc/cpuinfo"
}Output:
{
"success": true,
"stdout": "processor : 0\n...",
"stderr": "",
"exit_code": 0,
"elapsed_ms": 135
}For serial shells there is no reliable process exit status unless the command wrapper reports it. This implementation wraps every command and captures a marker containing $?, so exit_code is the command exit code when the shell supports standard POSIX syntax. If the marker cannot be parsed but the prompt returns, exit_code defaults to 0.
Related MCP server: mcp-micropython-bridge
Configuration
Environment variables:
Variable | Default | Description |
|
| Backend name. Currently only |
|
| Serial device path, for example |
|
| UART baud rate. |
|
| Per-read timeout in seconds. |
|
| Command completion timeout in seconds. |
|
| Stable shell prompt used to detect completion. |
|
| Serial text encoding. |
Run
Install dependencies:
python3 -m pip install -e .Start the MCP server over stdio:
board-terminal-skillExample MCP client configuration:
{
"mcpServers": {
"board-terminal": {
"command": "board-terminal-skill",
"env": {
"BOARD_SERIAL_PORT": "/dev/ttyUSB0",
"BOARD_SERIAL_BAUDRATE": "115200"
}
}
}
}Available Tools
1 toolboard_terminalC
Run a shell command on the connected Linux development board.
Inputs: command (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap, so disambiguation is perfect.
The single tool name 'board_terminal' is clear and follows a consistent style, making it predictable.
One tool is minimal but appropriate for a focused 'Board Terminal Skill' that only needs to run shell commands. However, it is on the thin side.
The tool fully covers the stated purpose of running shell commands on a board, with no obvious missing operations for that narrow scope.
Maintenance
Related MCP Connectors
Linux server administration over OAuth MCP: shell, Docker, systemd, files and monitoring.
MCP server for Klever blockchain smart contract development.
Related MCP Servers
- AlicenseBqualityBmaintenanceMCP server that lets LLMs talk to serial devices: microcontrollers, routers, modems, embedded Linux, anything with a UART.2461 PyPI7MIT
- FlicenseBqualityDmaintenanceMCP server for controlling MicroPython devices (ESP32, RP2040, etc.) via USB Serial or WebREPL, enabling code execution, file operations, and device management from MCP clients.299-
- FlicenseAqualityCmaintenanceHeadless local stdio MCP server for board-debug operations, allowing compatible clients to use tools for firmware debugging and board management.204-
- AlicenseBqualityCmaintenanceMCP server for embedded board debugging, providing structured serial capture, crash decoding, and flash-safe port arbitration via bounded CLI and MCP tools.102MIT