X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Triggercmd to Claude

Connect Claude Web, Desktop and Cowork to Triggercmd MCP. List all computers linked to your account, show available commands for your desktop pc, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Triggercmd logoTriggercmd
Api Key

TRIGGERcmd is a cloud service for securely running commands on your computers from anywhere. It streamlines automation by letting you trigger scripts and tasks remotely, right from the cloud.

5 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Triggercmd account to Claude via Composio Connect, enabling it to list all computers linked to your account, show available commands for your desktop PC, run nightly backup script on home server, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Triggercmd with

OpenAI Agents SDKClaude Agent SDKClaude CodeCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

Connecting Triggercmd to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Triggercmd account

Back in Claude, ask it to connect to Triggercmd or give it any Triggercmd-related task.

For example, ask Claude to:

  • "List all computers linked to your account"
  • "Show available commands for your desktop PC"
  • "Run nightly backup script on home server"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Triggercmd account is ready to use.

What is the Triggercmd Claude Connector, and what's possible with it?

The Triggercmd MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Triggercmd account. It provides structured and secure access to your registered computers and custom commands, so your agent can list connected machines, discover available commands, and execute remote actions on your behalf.

  • Remote command execution: Ask your agent to trigger any pre-configured command on any of your linked computers from anywhere, instantly.
  • Computer management and discovery: Effortlessly list all computers registered under your Triggercmd account, so you always know what machines are available for automation.
  • Command inventory browsing: Retrieve a full list of commands set up across all your connected devices, helping you decide what to automate next.
  • Context-aware command selection: Let your agent browse available commands before execution, ensuring the right action runs on the right computer each time.

Troubleshooting

1. Why does Claude not use the Composio connector for Triggercmd?

The connector can show as connected, but Claude must use it in each Triggercmd conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Triggercmd again.

2. Why does Claude show an MCP server error before Triggercmd connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Triggercmd.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Triggercmd.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Triggercmd authorization link not work?

The Composio connector is one server. Your Triggercmd account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Triggercmd connection.
  • Composio creates a fresh Triggercmd authorization link.
  • Open that link in your browser and finish the Triggercmd sign-in.

4. Why do Triggercmd actions fail after they worked before?

The Triggercmd connection can expire or lose permission.

  • Ask Claude to inspect the Triggercmd connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Triggercmd account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Triggercmd.
  • If the action still fails with a permission error, check that the connected account has that permission in Triggercmd itself.

5. How do I switch to a different Triggercmd account?

Claude can manage the Triggercmd connection for you.

  • Ask Claude to disconnect or delete the current Triggercmd account.
  • Ask Claude to connect Triggercmd again.
  • Open the new Composio authorization link for Triggercmd.
  • Sign in with the other Triggercmd account in the browser.
  • After the account connects, ask Claude to retry the Triggercmd task.

6. Why is my Triggercmd connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Triggercmd connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Triggercmd tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Triggercmd.
TOOLS

Supported Tools

Every Triggercmd action and event your agent gets out of the box.

List TriggerCMD Commands V2

Tool to list all available commands for the authenticated user.

List TriggerCMD Computers

Tool to list all computers associated with your TriggerCMD account.

List TriggerCMD Panel Buttons

Tool to retrieve all panel buttons configured in your TriggerCMD account.

Trigger Command

Tool to trigger a specified command on a target computer.

Trigger Panel Button

Tool to trigger a specific panel button.

FRAMEWORKS

How to build Triggercmd MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Triggercmd MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Triggercmd MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Triggercmd MCP with Claude Code

Codex logo

Codex

Use Triggercmd MCP with Codex

OpenClaw logo

OpenClaw

Use Triggercmd MCP with OpenClaw

Hermes logo

Hermes

Use Triggercmd MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Triggercmd MCP with Atomic Agent

Google ADK logo

Google ADK

Use Triggercmd MCP with Google ADK

LangChain logo

LangChain

Use Triggercmd MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Triggercmd MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Triggercmd MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Triggercmd MCP with LlamaIndex

CrewAI logo

CrewAI

Use Triggercmd MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Triggercmd MCP with Pydantic AI

AutoGen logo

AutoGen

Use Triggercmd MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Triggercmd MCP server, the agents and LLMs can only access a fixed set of Triggercmd tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Triggercmd and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Triggercmd tools.

Yes, absolutely. You can configure which Triggercmd scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Triggercmd data and credentials are handled as safely as possible.

Start with Triggercmd.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Triggercmd tool your agent needs.Free to start.

Start building