CLI & MCP
thinr is the command-line pillar of ThinRemote: one Node.js tool that drives your whole fleet from the terminal, and doubles as an MCP server so AI assistants can drive it too. Same credentials, same capabilities, two faces.
What you can do with it
| Workflow | Commands |
|---|---|
| Shells | thinr device console, or tunneled SSH with your own client |
| Run commands | thinr device exec, fleet-wide with thinr product exec |
| Move files | push, pull, ls, read, write, mkdir, rm, mv |
| Tunnels | tcp, tls and http proxies to anything the device reaches |
| Fleet operations | thinr fleet upgrade, playbooks, product fan-out |
| Automation | --json envelopes, stable error codes, real exit codes |
Everything is built to be scripted: data-producing commands emit a JSON envelope, errors carry stable codes, and exit codes compose with set -e and CI pipelines.
The MCP server
The same binary, started with thinr mcp, exposes the platform as typed tools for Claude Code, Claude Desktop, Cursor, or any MCP client: devices, exec, files, tunnels, monitoring, products, playbooks and alarms. One running server reaches any device in any of your configured environments.
Start with the MCP overview, or jump straight to the hands-on Drive your fleet with AI.
Where to go
- Install it: Install the CLI (npm, two minutes).
- Use it: the workflows in the sidebar, starting with SSH and console.
- Script it: JSON and automation.
- Look something up: the reference covers every command, flag and contract.