dokploy-dev

v1.7.0

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.

Codex23 Skills1 MCP serverstdio

By AGENTS.STORE0 GitHub starsUpdated 2 weeks ago

Directory evidence

Runtimes: Codex
Parsed components: 24 skill or MCP entries
Source updated: Oct 4, 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 dokploy-dev for Codex

Installs for the current user

codex plugin marketplace add Agents-Store/codex-plugins
codex plugin marketplace upgrade agents-store-codex-plugins
codex plugin add dokploy-dev@agents-store-codex-plugins

Paste and run these commands in a terminal with Codex. They add and refresh the agents-store-codex-plugins catalog, then install this plugin.

Compatibility: the page URL and API slug “dokploy-dev” remain stable.

Codex: dokploy-dev@agent-plugin-marketplace → dokploy-dev@agents-store-codex-plugins

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/codex-plugins

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is dokploy-dev/.

Plugin files

dokploy-dev/

├── .codex-plugin/plugin.json
├── skills/add-domain/SKILL.md
├── skills/ai-assist/SKILL.md
├── skills/analyze/SKILL.md
├── skills/api-reference/SKILL.md
├── skills/cleanup/SKILL.md
├── skills/cli-recipes/SKILL.md
├── skills/compose-logs/SKILL.md
├── skills/create-app/SKILL.md
├── skills/create-db/SKILL.md
├── skills/create-project/SKILL.md
├── skills/debug/SKILL.md
├── skills/debug-deploy/SKILL.md
├── skills/deploy/SKILL.md
├── skills/examples/SKILL.md
├── skills/list-apps/SKILL.md
├── skills/list-projects/SKILL.md
├── skills/logs/SKILL.md
├── skills/mcp-patterns/SKILL.md
├── skills/read-logs/SKILL.md
├── skills/rollback/SKILL.md
├── skills/setup/SKILL.md
├── skills/status/SKILL.md
├── skills/troubleshoot/SKILL.md
└── .mcp.json

Included Skills23

add-domainskills/add-domain/SKILL.md

Add a custom domain to a Dokploy application Arguments: <domain> --app <app-name-or-id> [--port <port>] [--https].

ai-assistskills/ai-assist/SKILL.md

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", "ai analyze logs dokploy", "set up dokploy ai", "configure ai provider in dokploy", "why is dokploy not suggesting fixes", "dokploy ai-analyzeLogs", "dokploy ai-suggest".

analyzeskills/analyze/SKILL.md

AI-summarise a failed Dokploy deployment or a crashing container via the configured ai provider Arguments: deployment-id|app-name-or-id|compose-name-or-id.

api-referenceskills/api-reference/SKILL.md

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".

cleanupskills/cleanup/SKILL.md

Reclaim disk space on the Dokploy server with a guided cleanup chain Arguments: --dry-run.

cli-recipesskills/cli-recipes/SKILL.md

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 auth", "dokploy application deploy", "dokploy read-logs from terminal", "deploy dokploy from terminal".

compose-logsskills/compose-logs/SKILL.md

Read the logs of EVERY container in a Dokploy Docker Compose stack and highlight errors Arguments: <compose-name-or-id> [--tail <N>] [--since <1h>] [--search <term>] [--errors-only].

create-appskills/create-app/SKILL.md

Create a new application in a Dokploy project Arguments: <name> --project <project> [--env <environment>] [--build <nixpacks|dockerfile|static>].

create-dbskills/create-db/SKILL.md

create-projectskills/create-project/SKILL.md

Create a new Dokploy project Arguments: <name> [--description <text>].

debugskills/debug/SKILL.md

Debug a failed or stuck Dokploy deployment with full decision-tree analysis Arguments: app-name-or-id|compose-id.

debug-deployskills/debug-deploy/SKILL.md

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. Triggers: "my dokploy deploy failed", "deployment stuck", "build error in dokploy", "app crashed after deploy", "diagnose failed deployment", "dokploy deploy not working", "why did my deploy fail", "recover from broken deploy".

deployskills/deploy/SKILL.md

Deploy or redeploy a Dokploy application or Docker Compose service Arguments: <app-name-or-id> [--project <project>].

examplesskills/examples/SKILL.md

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", "show me how to use dokploy", "dokploy debug example".

list-appsskills/list-apps/SKILL.md

List all applications and services in a Dokploy project Arguments: <project-name-or-id>.

list-projectsskills/list-projects/SKILL.md

List all Dokploy projects

logsskills/logs/SKILL.md

Read runtime or build logs for a Dokploy application, compose stack, database, or deployment Arguments: <resource-name-or-id> [--type <app|compose|db|deployment>] [--tail <N>] [--since <1h>] [--search <term>].

mcp-patternsskills/mcp-patterns/SKILL.md

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 compose", "manage dokploy".

read-logsskills/read-logs/SKILL.md

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 the dokploy logs", "tail the logs", "compose logs", "all containers' logs", "container logs", "why is my app crashing", "why did my deploy fail — check the logs", "grep the logs for an error", "runtime logs", "build logs". Use it instead of telling the user logs aren't available over the API — since Dokploy v0.29.0 they are.

rollbackskills/rollback/SKILL.md

Roll a Dokploy application or compose stack back to a previous version Arguments: <app-name-or-id|compose-id>.

setupskills/setup/SKILL.md

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.

statusskills/status/SKILL.md

Check Dokploy application or deployment status Arguments: <app-name-or-id> [--project <project>].

troubleshootskills/troubleshoot/SKILL.md

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. Triggers: "dokploy 502", "domain not resolving", "database connection refused", "mcp tools not found", "dokploy api 401", "traefik dashboard".

MCP servers1

dokploystdio

command: npx
args: -y @dokploy/mcp

Plugin manifests1

dokploy-dev/.codex-plugin/plugin.json

{
  "name": "dokploy-dev",
  "version": "1.7.0",
  "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, 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.",
  "author": {
    "name": "AGENTS.STORE"
  },
  "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"
  ],
  "skills": "./skills/",
  "mcpServers": "./.mcp.json",
  "interface": {
    "displayName": "Dokploy Dev",
    "shortDescription": "Dokploy self-hosted PaaS development plugin (aligned with…",
    "longDescription": "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.",
    "developerName": "AGENTS.STORE",
    "category": "infrastructure",
    "capabilities": [
      "Read",
      "Write"
    ],
    "websiteURL": "https://agents.store"
  }
}