How do I get my Trigger.dev API key?

Log in to your Trigger.dev dashboard at **cloud.trigger.dev**. Open your project, then find the **API Keys** section in the project settings. Copy your **Secret API Key** (it starts with `tr_dev_` for development or `tr_prod_` for production). Paste it into the configuration field below. For Personal Access Tokens (used for admin operations), go to **Profile → Personal Access Tokens** tab instead.

Can my AI agent tell me why a background job failed in production?

Yes. Ask your agent to list failed runs and it returns the task name, error message, stack trace, execution duration, and retry count for each failure. You can then drill into a specific run to see the exact input payload and which step failed — cutting your debugging time from minutes to seconds.

What if I'm on-call and need to check job health at 2 AM?

Just ask your AI agent 'Are there any failed jobs in production?' and get an instant triage report — number of failures, which tasks are affected, when they started failing, and whether retries resolved them. No need to open a browser, log in, or navigate dashboards in the middle of the night.

Does it support multiple environments like dev, staging, and production?

Yes. Each API key is scoped to a specific environment (dev or prod), just like in Trigger.dev itself. You can configure separate integrations for each environment, or switch between them by updating the API key — giving you full control over which environment your AI agent queries.

Trigger.dev MCP Server for Google ADK 8 tools — connect in under 2 minutes

Name: Trigger.dev
Availability: InStock
Author: Vinkius

google.github.io/adk-docs/tools/mcp-tools

Built by Vinkius GDPR 8 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Trigger.dev as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="triggerdev_agent",
    instruction=(
        "You help users interact with Trigger.dev "
        "using 8 available tools."
    ),
    tools=[mcp_tools],
)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Trigger.dev MCP Server

Connect Trigger.dev to your AI agent and manage your background job infrastructure conversationally.

Google ADK natively supports Trigger.dev as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 8 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

What you can do

Job Monitoring — List active, completed, and failed task runs with execution times, statuses, and error details.
Project Overview — Query projects, environments, and their associated job definitions.
Run Inspection — Drill into individual runs to view payloads, outputs, logs, and retry history.
Environment Management — Switch between dev, staging, and production environments to inspect runs across your deployment pipeline.

The Trigger.dev MCP Server exposes 8 tools through the Vinkius. Connect it to Google ADK in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Trigger.dev to Google ADK via MCP

Follow these steps to integrate the Trigger.dev MCP Server with Google ADK.

Install Google ADK

Run pip install google-adk

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Create the agent

Save the code above and integrate into your ADK workflow

Explore tools

The agent will discover 8 tools from Trigger.dev via MCP

Why Use Google ADK with the Trigger.dev MCP Server

Google ADK provides unique advantages when paired with Trigger.dev through the Model Context Protocol.

Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Trigger.dev

Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

Seamless integration with Google Cloud services means you can combine Trigger.dev tools with BigQuery, Vertex AI, and Cloud Functions

Trigger.dev + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Trigger.dev MCP Server delivers measurable value.

Enterprise data agents: ADK agents query Trigger.dev and cross-reference results with internal databases for comprehensive analysis

Multi-modal workflows: combine Trigger.dev tool responses with Gemini's vision and language capabilities in a single agent

Automated compliance checks: schedule ADK agents to query Trigger.dev regularly and flag policy violations or configuration drift

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Trigger.dev

Trigger.dev MCP Tools for Google ADK (8)

These 8 tools become available when you connect Trigger.dev to Google ADK via MCP:

cancel_run

Cancel a running task

get_run

Get run details

list_environments

List deployment environments

list_projects

List all projects

list_runs

List task runs

list_schedules

List cron schedules

replay_run

Replay a completed task

trigger_task

Trigger a background task

Example Prompts for Trigger.dev in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with Trigger.dev immediately.

"Are there any failed background jobs in production?"

"Show me the details of the last 'process-webhook' run."

"How many jobs ran successfully today?"

Troubleshooting Trigger.dev MCP Server with Google ADK

Common issues when connecting Trigger.dev to Google ADK through the Vinkius, and how to resolve them.

McpToolset not found

Update: pip install --upgrade google-adk

Trigger.dev + Google ADK FAQ

Common questions about integrating Trigger.dev MCP Server with Google ADK.

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.