Trigger.dev MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Trigger.dev MCP or direct API to inspect task runs, check workflow status, review deployment activity, and trigger background jobs through natural language.

Trigger.dev logoTrigger.dev
Api Key

Trigger.dev is a developer platform for reliable background tasks and workflows. It helps teams deploy, monitor, and manage long-running jobs without glue code.

10 Tools

Try Trigger.dev now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
Trigger.dev
Try asking
TOOLS

Supported Tools

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

Batch Trigger Task

Start multiple runs of one deployed Trigger.

Execute TRQL Query

Run one read-only Trigger.

Get Batch

Retrieve a task batch's status, run IDs, completion counts, and item errors.

Get Batch Results

Retrieve the success or failure outcome and encoded output for every run in a completed task batch.

Get Error

Retrieve one Trigger.

Get Run

Retrieve one run's status, timing, payload, output, attempts, metadata, relationships, schedule, and cost details.

Get Run Result

Retrieve one run's compact success or failure result, including its encoded output or error and usage duration.

List Errors

Return one forward page of Trigger.

List Runs

Return one forward page of runs in the connected environment, optionally filtered by time, status, task, version, tags, schedule, bulk action, test mode, or error.

Trigger Task

Start one run of a deployed Trigger.

SETUP GUIDE

Connect Trigger.dev MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["trigger_dev"],
  mcp: true,
});
Create a session scoped to Trigger.dev and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "List recent failed Trigger.dev task runs in production",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a Trigger.dev request
SETUP GUIDE

Connect Trigger.dev API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["trigger_dev"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to Trigger.dev
3

Run Trigger.dev tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "List recent failed Trigger.dev task runs in production" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the Trigger.dev tool calls through the session, and print the final answer

Why Use Composio?

AI Native Trigger.dev Integration

  • Supports both Trigger.dev MCP and direct API based integrations
  • Structured, LLM-friendly schemas for reliable task and workflow execution
  • Rich coverage for reading, writing, and querying Trigger.dev runs, jobs, and workflow data

Managed Auth

  • Secure API key handling without hard-coding Trigger.dev credentials in your agent code
  • Central place to manage, scope, and revoke Trigger.dev access
  • Per user and per environment credentials, so staging and production stay cleanly separated

Agent Optimized Design

  • Tools are tuned using real error and success rates to improve reliability over time
  • Comprehensive execution logs so you always know what ran, when, and on whose behalf
  • Clear tool schemas help agents inspect failed runs, monitor workflows, and trigger jobs with fewer mistakes

Enterprise Grade Security

  • Fine-grained RBAC so you control which agents and users can access Trigger.dev
  • Scoped, least privilege access to Trigger.dev resources
  • Full audit trail of agent actions to support review and compliance
FAQ

Frequently asked questions

Yes, Trigger.dev requires you to configure your own API key. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your Trigger.dev connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your Trigger.dev account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the Trigger.dev actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside Trigger.dev at any time.

When you connect a Trigger.dev account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in Trigger.dev as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside Trigger.dev. If Trigger.dev lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside Trigger.dev at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each Trigger.dev connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment Trigger.dev rejects the old key. Create a new key in Trigger.dev and reconnect the account from the Composio dashboard or by asking your agent to reconnect Trigger.dev. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal Trigger.dev use. Paid plans add higher limits and team features. Your Trigger.dev plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple Trigger.dev accounts).

With Composio, you connect Trigger.dev once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with Trigger.dev.It takes 30 seconds.

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

Start building