Skip to main content
Glama
vcode-sh

@vibetools/dokploy-mcp

by vcode-sh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DOKPLOY_URLYesYour Dokploy panel URL (e.g., https://panel.example.com)
DOKPLOY_API_KEYYesYour Dokploy API key (starts with dokp_)
DOKPLOY_PROFILES_JSONNoJSON string of profiles for multiple organizations (optional)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

Search the Dokploy API catalog. IMPORTANT: Do NOT wrap code in a function -- catalog is already a global. Write bare code: catalog.searchText("deploy") or catalog.recommend("safe database password rotation") or catalog.getByTag("application") or catalog.get("application.one"). Common patterns: catalog.recommend("tail project logs across environments") -> helper-first workflow suggestions; catalog.get("application.one") -> application detail fields plus optional shaping params; catalog.get("application.update") -> build/runtime/resource tuning fields such as byte-based memory limits; catalog.get("application.many") -> batched application reads; catalog.get("project.overview") -> compact project state view; catalog.get("deployment.all") -> deployment history entries. Returns procedure names, parameters, HTTP methods, schemas, and response hints for key endpoints.

executeA

Run JavaScript code or a guided Dokploy workflow. In code mode, write bare JS against global dokploy and helpers without wrapping it in a function. In workflow mode, deploy-application can resolve a target, choose preview vs apply, collect bounded rollout options, and build a bounded plan when sampling and elicitation are enabled. When MCP tasks are enabled, execute also supports polling and cancellation for long-running runs. Known Dokploy IDs yield reusable dokploy://... resource links, and search helps discover procedures.

list_profilesA

List the available Dokploy profiles, including default and named targets, without exposing API keys. Returns profile names, normalized Dokploy API URLs, and config sources.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation4/5

Each tool targets a different aspect: execute handles code and workflows, list_profiles lists profiles, and search queries the API catalog. Occasional overlap exists (execute and search both reference workflows) but purposes are mostly distinct.

Naming Consistency2/5

Naming is inconsistent: execute (bare verb), list_profiles (verb_noun with snake_case), search (bare verb). There is no clear pattern across the tool set.

Tool Count2/5

With only 3 tools, the server feels under-scoped for a platform like Dokploy that typically requires managing applications, deployments, and configurations. A broader tool set is expected.

Completeness2/5

The tool set lacks essential operations such as creating, updating, or deleting applications or deployments. While execute and search provide some flexibility, core lifecycle management is absent.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources