dokploy-dev

What dokploy-dev does, in the publisher's words

From the project README, punctuation lightly normalized · Open the README on GitHub →

Links

• github.com/Agents-Store/agentplugins
• dokploy-dev/plugin.json (manifest)

Skills · 9

ai-assist

This skill should be used when the user wants AI-powered deployment debugging on Dokploy, wiring up an LLM provider (OpenAI, Anthropic, Gemini, Ollama, OpenRouter, etc.), summarising build logs with AI, or asking Dokploy for a next-step suggestion. Triggers: \"analyze my failed deploy with AI\", \…

api-reference

This skill should be used when making direct HTTP/curl calls to the Dokploy API, looking up endpoint parameters, or building integrations that bypass the MCP server. Triggers: \"dokploy API\", \"curl dokploy\", \"REST endpoint\", \"HTTP request to dokploy\".

cli-recipes

This skill should be used when running Dokploy operations from the terminal with the @dokploy/cli, authenticating, creating projects/apps, deploying, managing environment variables, provisioning databases, or reading logs via command line. Triggers: \"dokploy cli\", \"dokploy command\", \"dokploy…

debug-deploy

This skill should be used when a Dokploy deployment fails, gets stuck, or behaves incorrectly after deploying, provides an end-to-end decision tree that locates the failed run, reads the right logs, inspects the container and Traefik state, summarises root cause with AI, and recovers safely. Trigg…

examples

This skill should be used when learning how to deploy apps, provision databases, set up Docker Compose stacks, or debug a failed deployment on Dokploy. Provides end-to-end workflow walkthroughs. Triggers: \"dokploy example\", \"how to deploy on dokploy\", \"dokploy tutorial\", \"dokploy walkthrough…

mcp-patterns

This skill should be used when deploying applications, managing projects, provisioning databases, configuring domains, working with Docker Compose, or performing any Dokploy operation via MCP tools. Triggers: \"deploy app\", \"create project\", \"add domain\", \"provision database\", \"dokploy comp…

read-logs

This skill should be used whenever the user wants to read, tail, stream, or search Dokploy logs, application runtime logs, Docker Compose stack logs (every container), database logs, or deployment build logs, and especially to diagnose why something failed. Triggers: \"read the logs\", \"show me…

setup

This skill should be used when verifying Dokploy MCP connection, CLI installation, and API access. Use when user says \"set up dokploy\", \"verify dokploy connection\", \"check dokploy\", \"test dokploy access\", or enables the dokploy-dev plugin for the first time.

troubleshoot

This skill is the symptom-to-cause lookup reference for Dokploy problems, domains, databases, Docker, Traefik, MCP connection. Use for known-symptom diagnosis. For an end-to-end failed-deploy workflow, the canonical entry point is the `debug-deploy` skill and the `/dokploy-dev:debug` command. Trig…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

MCP servers · 1

dokploystdio

npx -y @dokploy/mcp

env vars: DOKPLOY_URL · DOKPLOY_API_KEY

Read from the plugin's own mcp.json. We list environment variable names, never values.

Category

DevOps & Cloud. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.

Keywords

dokploy · paas · deployment · docker · self-hosted · applications · databases · domains · compose · traefik · backups · infrastructure · debugging · ai-analysis · log-analysis · runtime-logs · compose-logs · dokploy-v0.30 · dev · agents-store

Related by publisher and keywords

• restic-devAgents-Store

  restic backup plugin for Agents Store. Set up encrypted daily backups on any Linux server to S3-compatible storage (Cloudflare R2): server recon + restic install, auto-discovery of all Docker volumes/mounts and databases, R2 repository init, a partial-failure-tolerant backup script with logical DB dumps and retention, timezone-aware systemd/cron scheduling, verification, monitoring/dead-man's-switch, and disaster recovery. File-based knowledge, no MCP, no stored credentials.

• openclaw-opsAgents-Store

  Operations plugin for a fleet of self-hosted OpenClaw gateway instances running as Docker Compose projects on one host. Discovers every instance from the live Docker state (never from hard-coded paths), classifies it ok/degraded/down/alien, and runs day-two maintenance: health and liveness reporting, provider-auth triage (expired, emptied and shadowed OAuth profiles, shared-credential token sink), config surgery with snapshot and executable rollback, memory/embedding repair and reindexing, shared skills and plugins consolidation, Infisical secret-delivery audit by key name only, security audit, version-drift and channel-aware upgrades, and reference-instance cloning. Mutations are dry-run by default behind an eight-block plan, need --yes, and need a typed confirmation when irreversible. Secrets are reported as fingerprints, presence and expiry, never as values. File-based knowledge: no MCP server, no required environment variables, no stored credentials; the single optional variable OPENCLAW_OPS_CONFIG is an escape hatch for the fleet-config path, and deployment specifics live in that operator-owned config outside the repository. Also carries the workspace persona guides (AGENTS.md, SOUL.md, USER.md, IDENTITY.md, standing orders, bootstrap, memory, session analysis) taken over from the retired openclaw-configurator.

• payloadcms-devAgents-Store

  PayloadCMS dev plugin for Agents Store. Covers collections, fields, globals, hooks, access control, authentication, queries, data management (trash/query presets/folders), localization, adapters, Lexical rich text, admin customization, jobs queue, plugin development, official plugins, Next.js integration, deployment, CLI, migrations, and end-to-end scenarios for TypeScript developers building with Payload v3.

• trigger-devAgents-Store

  Trigger.dev dev plugin for Agents Store. Comprehensive development knowledge for building background tasks, AI agent workflows, and durable execution on self-hosted Trigger.dev v4 (baseline server 4.4.4; newer features are marked with the server version they need), SDK patterns, CLI recipes, deployment, full 41-tool MCP reference, TRQL queries and dashboards, managed prompts, chat agents, dev-server control, realtime API, and troubleshooting.

• vercel-devAgents-Store

  Vercel ecosystem plugin. Deployment, AI SDK, Edge Functions, storage, routing, performance optimization. Includes CLI deploy troubleshooting for non-Git projects, Hobby plan fixes, standalone output handling. Based on official vercel-plugin v0.53.0 by Vercel Labs; telemetry is opt-in (VERCEL_PLUGIN_TELEMETRY=on).

• chatwoot-devAgents-Store

  Chatwoot dev plugin for Agents Store. Full REST API coverage (Application, Platform, and Public/Client APIs) with bundled OpenAPI specs, official chatwoot CLI recipes, webhook & agent-bot automation, and troubleshooting for developers building on Chatwoot. Authenticates with the api-access-token header (hyphenated, proxy-safe) via CHATWOOT_API_KEY against CHATWOOT_BASE_URL.