Skip to main content

Quick setup

We provide multiple tools to help AI coding assistants write correct Trigger.dev code. Use one or all of them for the best developer experience.
1

Install the MCP Server

Give your AI assistant direct access to Trigger.dev tools — search docs, trigger tasks, deploy projects, and monitor runs. Works with Claude Code, Cursor, Windsurf, VS Code (Copilot), and Zed.
Learn more →
2

Install Skills

Portable instruction sets that teach any AI coding assistant Trigger.dev best practices: writing tasks, realtime frontends, and chat.agent AI agents. They install with the CLI into Claude Code, Cursor, VS Code (Copilot), and AGENTS-compatible tools such as Codex via .agents/skills/, and draw their API guidance from a version-pinned reference shipped in @trigger.dev/sdk.
Learn more →

Skills and the MCP server

Skills and the MCP server do different jobs and work best together. Here’s how they compare:
SkillsMCP Server
What it doesDrops skill files into your project that teach Trigger.dev patternsRuns a live server your AI connects to
Installs to.claude/skills/, .cursor/skills/, .github/skills/, .agents/skills/mcp.json, ~/.claude.json, etc.
UpdatesRe-run npx trigger.dev@latest skills, or auto-prompted on trigger devAlways latest (uses @latest)
Best forTeaching patterns and best practicesLive project interaction (deploy, trigger, monitor)
Works offlineYesNo (calls Trigger.dev API)
Our recommendation: Install both. Skills teach your AI how to write Trigger.dev code; the MCP Server lets it do things in your project.

Project-level context snippet

If you prefer a lightweight/passive approach, paste the snippet below into a context file at the root of your project. Different AI tools read different files:
FileRead by
CLAUDE.mdClaude Code
AGENTS.mdOpenAI Codex, Jules, OpenCode
.cursor/rules/*.mdCursor
.github/copilot-instructions.mdGitHub Copilot
CONVENTIONS.mdWindsurf, Cline, and others
Create the file that matches your AI tool (or multiple files if your team uses different tools) and paste the snippet below. This gives the AI essential Trigger.dev context without installing anything.

llms.txt

We also publish machine-readable documentation for LLM consumption: These follow the llms.txt standard and can be fed directly into any LLM context window.

Troubleshooting

Install Skills; they override the outdated patterns in the AI’s training data. The context snippet above is a quick alternative.
  1. Make sure you’ve restarted your AI client after adding the config
  2. Run npx trigger.dev@latest install-mcp again — it will detect and fix common issues
  3. Check that npx trigger.dev@latest mcp runs without errors in your terminal
  4. See the MCP introduction for client-specific config details
Both if possible:
  • Skills to teach your AI how to write Trigger.dev code (tasks, realtime, chat.agent)
  • MCP Server if you need to trigger tasks, deploy, and search docs from your AI

Next steps

MCP Server

Install and configure the MCP Server for live project interaction.

Skills

Install Trigger.dev agent skills into any AI coding assistant.

Writing tasks

Learn the task patterns your AI assistant will follow.