The commands you already set up — a script, a reboot, the office lights — become things you ask for by name, with the parameter said in words. Describing a command in TRIGGERcmd turns it into its own tool, which is what makes the model pick the right one.
A local stdio server in front of your TRIGGERcmd account. It lists the commands registered across your computers and runs them, and it builds a dedicated tool for every command that carries an mcpToolDescription.
- Every TRIGGERcmd command on the account, across every computer
- Any of them run by naming the computer and the command
- Parameters passed through to commands that accept them
- One tool per described command, named run_{computer}_{command}, carrying that command's own description
A TRIGGERcmd account and its token. The server takes the token from the environment when one is set there, otherwise it reads ~/.TRIGGERcmdData/token.tkn from your home directory. Adding an mcpToolDescription to a command takes effect after a server restart.
One command plus a key — docker run --rm -i -e TRIGGERCMD_TOKEN=your-token-here triggercmd-mcp:latest, then supply credentials