---
title: "dokploy-dev"
description: "Dokploy self-hosted PaaS development plugin (aligned with Dokploy v0.30.x). Deploy applications, provision 6 database types (Postgres, MySQL, MariaDB, MongoDB, Redis, LibSQL), manage domains and Docker Compose stacks, AN"
canonical: https://agentpluginsdirectory.com/plugins/dokploy-dev
last-updated: 2026-11-13
---

# dokploy-dev
Dokploy self-hosted PaaS development plugin (aligned with Dokploy v0.30.x). Deploy applications, provision 6 database types (Postgres, MySQL, MariaDB, MongoDB, Redis, LibSQL), manage domains and Docker Compose stacks, AND debug failed deployments end-to-end, reads runtime logs of every container (including each container in a Docker Compose stack) over the API/MCP with tail/since/search, plus AI-powered log analysis (ai-analyzeLogs), Docker container and host introspection (server health, events, disk usage, images, volumes), Traefik diagnosis, and a guided recovery chain. Complete MCP/REST coverage: all 604 operations across 57 categories indexed with params, covers per-service Docker network management, vault (external secrets) providers, DNS providers, forward-auth SSO domain protection, SCIM provisioning, build concurrency, and the auto-generated @dokploy/cli (604 commands incl. read-logs). Uses the official @dokploy/mcp server (secret fields are redacted by default since 0.30.0) plus debugging-focused slash commands including /compose-logs.
## Package we checked
The manifest we fetched is dokploy-dev/plugin.json in Agents-Store/agentplugins. The plugin root is the directory that holds that file. Its $schema is https://agent-plugins.org/schemas/1.0.0/plugin.schema.json. The manifest lists 9 skills and 1 MCP server (dokploy). Extension keys: com.anthropic.claude-code. Stored mcp.json transports: dokploy stdio.
- Slug: dokploy-dev
- Publisher: AGENTS.STORE
- Repository: https://github.com/Agents-Store/agentplugins
- Manifest: dokploy-dev/plugin.json
- Version: 1.7.4
- Category (editorial): devops-cloud
- Skills: 9 (ai-assist, api-reference, cli-recipes, debug-deploy, examples, mcp-patterns, read-logs, setup, troubleshoot)
- MCP servers: 1 (dokploy)
- Stars: 0
- Repository created: 2026-08-18
- Repository last pushed: 2026-11-05
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/dokploy-dev
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

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

Dokploy self-hosted PaaS development plugin (aligned with Dokploy v0.29.14). Deploy applications, provision 6 database types (Postgres, MySQL, MariaDB, MongoDB, Redis, LibSQL), manage domains and Docker Compose stacks, AND debug failed deployments end-to-end, reads runtime logs of every container (including each container in a Docker Compose stack) over the API/MCP with tail/since/search, plus AI-powered log analysis (ai-analyzeLogs), Docker container introspection, Traefik diagnosis, and a guided recovery chain. Complete MCP/REST coverage: all 546 v0.29.14 operations across 50 categories indexed with params, covers forward-auth SSO domain protection, SCIM provisioning, build concurrency, and the rewritten @dokploy/cli (546 auto-generated commands incl. read-logs). Uses the official @dokploy/mcp server plus debugging-focused slash commands including /compose-logs.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/Agents-Store/agentplugins/HEAD/dokploy-dev/README.md

## Skills

- 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

- dokploy: transport: stdio; command: npx -y @dokploy/mcp; env: DOKPLOY_URL, DOKPLOY_API_KEY

Read from the plugin's own mcp.json. Environment variable names only, never values.
