triggercmd-mcp-stdio
Verified Safeby rvmey
Overview
Enables AI-driven control of TRIGGERcmd commands on remote computers via a Model Context Protocol (MCP) stdio server.
Installation
docker run --rm -i -e TRIGGERCMD_TOKEN='your-actual-token' triggercmd-mcp:latestEnvironment Variables
- TRIGGERCMD_TOKEN
Security Notes
The server retrieves the TRIGGERcmd token from environment variables or a file, avoiding hardcoded secrets. It employs robust Docker security practices like running as a non-root user, using a read-only filesystem, preventing privilege escalation, and utilizing a minimal Alpine Linux base image. The core Go application does not use eval or similar dangerous functions. A minor discrepancy exists where `docker-compose.yml` includes `network_mode: none` and `tty: true`, which would prevent API calls and interfere with stdio respectively, making the container dysfunctional for its intended purpose; however, the `docker run` examples for MCP clients correctly omit these potentially problematic settings, and generally, network access to triggercmd.com is required for functionality.
Similar Servers
ha-mcp
Provides AI agents with complete control over Home Assistant via REST and WebSocket APIs, offering a comprehensive suite of tools for smart home management, automation, and debugging.
tmux-mcp
Enables AI assistants (like Claude Desktop) to interact with, control, and observe tmux terminal sessions by providing tools for session management and command execution.
advanced-homeassistant-mcp
A powerful, secure, and extensible Model Context Protocol (MCP) server that enables AI assistants like Claude, GPT, and Cursor to seamlessly interact with Home Assistant. Control your lights, climate, automations, and more through natural language commands.
mcp-ssh-manager
Manages remote SSH servers via the Model Context Protocol (MCP), enabling AI assistants like Claude Code and OpenAI Codex to execute commands, transfer files, monitor health, and automate DevOps tasks.