stack-directus-nextjs-trigger
v3.0.0Directus + Next.js + Trigger.dev architecture plugin. How Directus (content, files, access), a Next.js App Router frontend and self-hosted Trigger.dev (durable and scheduled work) fit together: who holds which token, how the cache is invalidated, how a Directus change reaches a task and the result reaches the page, who owns the session, and a production checklist. Tool knowledge comes from its dependencies.
By Agents Store0 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 8 skill or MCP entries
- Source updated
- Oct 7, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install stack-directus-nextjs-trigger for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install stack-directus-nextjs-trigger-3@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/Agents-Store/claude-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/stack-directus-nextjs-trigger/.
Plugin files
├── .claude-plugin/plugin.json├── skills/authentication/SKILL.md├── skills/background-tasks/SKILL.md├── skills/deployment/SKILL.md├── skills/directus-to-trigger/SKILL.md├── skills/examples/SKILL.md├── skills/full-feature/SKILL.md├── skills/init-project/SKILL.md└── .mcp.json
Included Skills7
This skill should be used when the user wants to "add authentication to Directus + Next.js", "implement Directus login in Next.js", "use NextAuth with Directus", "use Better Auth with Directus", "protect Next.js pages with Directus auth", "choose an auth approach for Directus and Next.js", "decide who owns the session", "act as the signed-in user inside a trigger.dev task", or needs to decide who owns the end-user session and the tokens across Directus and Next.js.
This skill should be used when the user wants to "offload work to trigger.dev from next.js", "run a background job from a server action", "trigger a task from a route handler", "delegate slow work to trigger.dev", "decide what runs in a Server Action and what in a task", "show a task's progress in next.js", "give the browser a token for a trigger.dev run", "keep task environment variables apart from next.js", "fix a TRIGGER_SECRET_KEY build error", or needs the rules where a Next.js App Router app hands work to Trigger.dev and gets the result back.
This skill should be used when the user wants to "run the Directus Next.js Trigger.dev stack locally", "deploy trigger.dev tasks next to a Next.js app", "set environment variables for trigger.dev tasks", "configure content-change webhooks with trigger.dev", "revalidate the site when a task changes Directus content", "CI/CD for trigger tasks", "production checklist for directus + nextjs + trigger.dev", or needs the pipelines that connect the three services and the checks before production. For platform-specific hosting (Vercel, Dokploy, etc.), see the respective deployment plugin.
This skill should be used when the user wants to "trigger a task from a directus flow", "run a background task when a directus item is created or updated", "forward directus webhooks to trigger.dev", "process directus items asynchronously", "build a directus flow to next.js to trigger pipeline", "have a task write back to directus", "stop a directus flow and task from looping", "read and write directus from a trigger.dev task", or needs the pattern for wiring Directus Flow events through Next.js into Trigger.dev tasks and back.
End-to-end scenario walkthroughs for the Directus + Next.js + Trigger.dev stack. This skill should be used when the user asks for "directus nextjs trigger.dev examples", "how to build a blog with directus + next.js", "ai enrichment pipeline example", "scheduled data sync example", "show me a complete example with background tasks", or needs implementation references for common application types on this stack.
This skill should be used when the user wants to "build a complete feature with directus nextjs and trigger.dev", "create an end-to-end feature with background tasks", "implement a full crud feature with async processing", "build a new section of the site that uses background jobs", "add a page backed by directus with a background task", or needs a step-by-step recipe for building features that span Directus, Next.js, and Trigger.dev.
This skill should be used when the user asks to "set up Directus + Next.js + Trigger.dev project", "initialize directus nextjs trigger.dev stack", "bootstrap the 3-service stack", "configure directus next.js and trigger.dev together", "connect trigger.dev to a directus nextjs app", "scaffold stack with background tasks", "start a new project with background jobs", or needs to set up environment variables, versions and verify connections for the Directus + Next.js + Trigger.dev stack.
MCP servers1
- command
- npx
- args
- trigger.dev@${TRIGGER_CLI_VERSION:-latest} mcp --dev-only --project-ref ${TRIGGER_PROJECT_REF}
- env.TRIGGER_ACCESS_TOKEN
- ${TRIGGER_ACCESS_TOKEN}
- env.TRIGGER_API_URL
- ${TRIGGER_API_URL}
Plugin manifests1
{
"name": "stack-directus-nextjs-trigger",
"version": "3.0.0",
"description": "Directus + Next.js + Trigger.dev architecture plugin. How Directus (content, files, access), a Next.js App Router frontend and self-hosted Trigger.dev (durable and scheduled work) fit together: who holds which token, how the cache is invalidated, how a Directus change reaches a task and the result reaches the page, who owns the session, and a production checklist. Tool knowledge comes from its dependencies.",
"author": {
"name": "Agents Store",
"url": "https://github.com/agents-store"
},
"mcpServers": "./.mcp.json",
"keywords": [
"stack",
"directus-nextjs-trigger",
"architecture",
"agents-store",
"directus",
"nextjs",
"trigger.dev",
"background-jobs",
"scheduled-tasks",
"self-hosted",
"durable-execution",
"app-router"
],
"dependencies": [
"directus-dev",
"nextjs-dev",
"trigger-dev"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[stack-directus-nextjs-trigger on Agent Plugins Marketplace](https://pluginsmp.com/plugins/stack-directus-nextjs-trigger-3)