Categories

  • Announcements regarding TRIGGERcmd

    78
    Topics
    222
    Posts

    RussR

    The Streamable HTTP MCP URL for TRIGGERcmd is https://triggercmd.com/mcp

    You can use this TRIGGERcmd MCP server with online tools like Mistral AI.

    To set it up in Mistral AI, go here: https://chat.mistral.ai/connections

    Then click + Add Connector and fill in this form:

    42237914-cf5f-47db-a2eb-8218f6ca1f88-image.png

    It works just like the local stdio MCP server used with local AI tools like Claude desktop. Click here for an example of that.

    4f337be5-d297-44d6-8082-85790907a551-image.png

    You can also use it with Open AI's agent builder tool at https://platform.openai.com/agent-builder

    904b7cf2-fbba-453d-9a88-187c0d71ff77-image.png

  • A place to talk about TRIGGERcmd

    702
    Topics
    3.4k
    Posts

    RussR

    @jett, you'll need to cancel your subscription from your Paypal account.

  • A place to share commands you like to trigger remotely.

    Raspberry Pi Mac Windows Linux
    397
    Topics
    1.5k
    Posts

    RussR

    Thanks @Xander .

  • Instructions for each operating system, and various scenarios.

    MCP Home Assistant API Google Home Alexa Mac Linux Raspberry Pi Windows
    284
    Topics
    1.3k
    Posts

    RussR

    @mega_big, on a Raspberry Pi, assuming you installed the agent using these instructions, your commands are in this file:

    /root/.TRIGGERcmdData/commands.json

    You'll see the default commands in there.

    You can run these commands to edit it:

    sudo su - cd /root/.TRIGGERcmdData nano commands.json

    While the agent is running, it will detect changes in that commands.json file and create/remove triggers for those commands in your TRIGGERcmd account. If you mess up the json at all (an extra comma even), the agent will restore the last backup it took. You'll see that in your debug.log.

    If you don't want to deal with editing text, you could create a command on your Windows PC using the "GUI Command Editor" then copy/paste the json text of that command from the "Text Command Editor" into your commands.json file.