connect_to_deviceLABSCO SUMMARY
A shell on a remote machine, opened without opening a port.
The usual price of letting an agent touch a remote box is SSH keys, a VPN or an exposed port. Here the device connects out through awaBerry and the session runs over that, so nothing on your side has to listen.
What it is
A remote-access server for machines enrolled in the awaBerry platform. Your client talks to awaBerry, awaBerry talks to the device, and the terminal session stays open across calls so state survives between commands.
What you get
- A connection to a named Mac, Linux, Windows or Docker device in your project, returning a session token and the device's status
- Terminal commands executed on that device inside one long-running session
- File management and database access on the connected machine over the same session
- Generated results written back to the device, not just read from it
- Demo credentials and a demo device, so the connection can be tried before anything of yours is enrolled
Requirements
An awaBerry account with at least one device registered to a project, plus that project's key and secret — supplied in the environment, or passed on the call. Node.js runs the server.
Setup effort
Build from source — git clone https://github.com/awaberry/mcp_server_awaberry.git
USE CASES
01
Pulling data off a machine that is not on your network
Connect by device name and read what you need from a shell that keeps its working state between calls.
02
Letting an agent operate a fleet machine
A named device, a session token, and commands that run in sequence rather than each in a fresh shell.
03
Writing generated results back to the device
The same session that reads can write, so an analysis can leave its output where it belongs.
04
Trying the connection before you enrol a machine
Demo credentials and a demo device ship with the server, so the flow can be tested against something that is not yours.
2 tools
Listed in project docs. Your client may show a different list.
execute_terminal_commandBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- Node.js >= 18
- An awaBerry project key and secret, set in mcpclients/awaberry-config.json
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/awaberry/mcp_server_awaberry.git
cd mcp_server_awaberry
npm install
cd mcpclients
cp awaberry-config.json.example awaberry-config.jsonEdit awaberry-config.json: set serverUrl to the awaBerry MCP server you use (the one your company runs, or http://localhost:3000/mcp for a local one), and AWABERRY_PROJECT_KEY and AWABERRY_PROJECT_SECRET to your project's key and secret
Only for a local server — start it from the repository root:
TERMINAL
cd ..
npm run start:mcp:jsonMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"awaberry": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_SERVER_AWABERRY>/mcpclients/start-awaberry-mcp.js"
]
}
}
}
