Dokploy Mcp

Created By
Alexey Elizarov8 months ago
A comprehensive Model Context Protocol (MCP) server for Dokploy, providing type-safe access to the complete Dokploy API with extensive tool coverage across all available endpoints.
Overview

What is Dokploy MCP?

Dokploy MCP is a comprehensive Model Context Protocol (MCP) server that provides type-safe access to the complete Dokploy API, ensuring extensive tool coverage across all available endpoints.

How to use Dokploy MCP?

To use Dokploy MCP, install it via npm with the command npx -y dokploy-mcp, and configure it by setting the required environment variables for your Dokploy instance and API key.

Key features of Dokploy MCP?

  • 380 tools covering 100% of Dokploy API functionality
  • Smart tool selection with core tools enabled by default
  • Advanced tools available but disabled by default for performance
  • Type-safe integration with auto-generated OpenAPI types
  • Environment-based authentication
  • Modular architecture with each tool in separate files
  • Comprehensive error handling for all HTTP status codes
  • Production-ready MCP server with optimized tool selection

Use cases of Dokploy MCP?

  1. Integrating various tools with the Dokploy API seamlessly.
  2. Managing tool configurations dynamically based on project needs.
  3. Facilitating development and testing of applications using Dokploy services.

FAQ from Dokploy MCP?

  • How do I get my API key?

You can create an API key in your Dokploy dashboard under Settings → Profile.

  • Can I enable or disable specific tools?

Yes! You can control which tools are enabled or disabled at runtime using command-line arguments or environment variables.

  • Is Dokploy MCP suitable for production use?

Yes! Dokploy MCP is designed to be production-ready with optimized tool selection.

Server Config

{
  "mcpServers": {
    "dokploy": {
      "command": "npx",
      "args": [
        "-y",
        "dokploy-mcp"
      ],
      "env": {
        "DOKPLOY_URL": "https://your-dokploy-instance.com",
        "DOKPLOY_API_KEY": "your-api-key-here"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
Alexey Elizarov
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago