TRIGGERcmd

io.github.rvmeyPublished by GitHub account rvmeyv1.0.0Updated Oct 24, 2026

Run commands on your computers remotely with TRIGGERcmd.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

A remote MCP server that lets an assistant run commands on your own computers through TRIGGERcmd.

What you can do
Run commands on your computers remotely through TRIGGERcmd, as described in the registry entry. The manifest lists no individual tools, so the exact set of actions an assistant can take is not documented here. Access is over a remote endpoint with OAuth sign-in.
When to use it
Useful when you want an assistant to trigger commands on machines you have already set up in TRIGGERcmd, for example starting a task on a home or office computer from a conversation.
Requirements
A remote connection to the TRIGGERcmd endpoint over streamable HTTP, an OAuth sign-in, and a TRIGGERcmd account with computers and commands configured there. No packages, environment variables or headers are declared.
Before you install
The server runs commands on your computers, so anything an assistant triggers executes for real on those machines. Grant OAuth access only to an account you control, and review which commands are exposed in TRIGGERcmd before connecting.

Installation

In SourceWeft

  1. Open TRIGGERcmd in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.rvmey%2Ftriggercmd/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "triggercmd": {
      "type": "http",
      "url": "https://www.triggercmd.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.