DuploCloud Docker MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DuploCloud Docker MCP Server list all services in the 'production' tenant"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DuploCloud Docker MCP Server
MCP server that exposes DuploCloud infrastructure management as tools consumable via Docker MCP Toolkit.
Tools (31 total)
Category | Tools |
Tenants |
|
Services |
|
Hosts |
|
Databases |
|
Storage |
|
Containers |
|
Setup
Prerequisites
Python 3.13+
DuploCloud portal access with an API token
Environment Variables
export DUPLO_HOST=https://your-company.duplocloud.net
export DUPLO_TOKEN=your-api-token
export DUPLO_TENANT=default # optionalInstall & Run
uv sync
uv run main.pyDocker
docker build -f docker/Dockerfile -t duplocloud-mcp .
docker run -i --rm \
-e DUPLO_HOST=https://your-company.duplocloud.net \
-e DUPLO_TOKEN=your-api-token \
duplocloud-mcpDocker MCP Toolkit
docker mcp server add duplocloud-mcpTool Reference
Tenants
Tool | Parameters | Description |
| — | List all tenants accessible in the DuploCloud portal |
|
| Get details of a specific tenant by name |
|
| Create a new tenant |
|
| Delete a tenant by name |
Services
Tool | Parameters | Description |
|
| List all services in a tenant |
|
| Get details of a specific service |
|
| Create a new service |
|
| Update service image and/or replicas |
|
| Delete a service |
|
| Restart a service (rolling redeployment) |
Hosts
Tool | Parameters | Description |
|
| List all hosts (VMs) in a tenant |
|
| Get details of a specific host |
|
| Create a new host (0=Linux Docker, 7=EKS Linux) |
|
| Terminate a host |
|
| Reboot a host |
Databases
Tool | Parameters | Description |
|
| List all RDS instances in a tenant |
|
| Get details of an RDS instance |
|
| Create an RDS instance |
|
| Resize an RDS instance |
|
| Delete an RDS instance |
Storage
Tool | Parameters | Description |
|
| List all S3 buckets in a tenant |
|
| Get details of an S3 bucket |
|
| Create a new S3 bucket |
|
| Update bucket configuration (versioning) |
|
| Delete an S3 bucket |
Containers (ECS)
Tool | Parameters | Description |
|
| List all ECS services in a tenant |
|
| List all ECS task definition families |
|
| List running tasks for a service |
|
| Run a task from a task definition family |
|
| Update the image of an ECS service |
|
| Delete an ECS service |
Troubleshooting
Missing environment variables
DuploError: DUPLO_HOST environment variable is requiredSet DUPLO_HOST and DUPLO_TOKEN before running. See .env.example.
Invalid or expired token
{"error": "Unauthorized", "code": 401}Generate a new API token from the DuploCloud portal: User menu > Security > API Token.
Tenant not found
{"error": "Tenant 'xyz' not found", "code": 404}Verify the tenant name with tenant_list. Tenant names are case-sensitive.
Connection refused
{"error": "Unexpected error: Connection refused", "code": 500}Verify DUPLO_HOST is correct and the DuploCloud portal is reachable from your network.
Development
# Install with dev dependencies
uv sync
# Lint & format
uv run ruff check .
uv run ruff format .
# Tests
uv run pytest
uv run pytest --cov=duplocloud_mcp --cov-report=term-missing
# Single test
uv run pytest tests/test_tools/test_services.py::test_service_listArchitecture
main.py # Entrypoint: mcp.run(transport="stdio")
duplocloud_mcp/
server.py # FastMCP instance, imports tool modules
client.py # DuploClient singleton wrapper
errors.py # Error decorator, validators
tools/
tenants.py # Tenant CRUD tools
services.py # Service CRUD + restart tools
hosts.py # Host CRUD + reboot tools
databases.py # RDS database CRUD tools
storage.py # S3 bucket CRUD tools
containers.py # ECS service/task toolsEach tool module imports the shared mcp instance from server.py and registers tools via @mcp.tool(). The @handle_duplo_errors decorator translates DuploCloud exceptions into structured JSON error responses. The duplocloud-client library handles all REST API communication.
License
MIT
Available Tools
31 toolsbucket_createC
Create a new S3 bucket in a DuploCloud tenant.
Args: tenant_id: The tenant ID to create the bucket in. name: Name for the new bucket.
Inputs: tenant_id (required), name (required). Returns: result
bucket_deleteB
Delete an S3 bucket from a DuploCloud tenant.
Args: tenant_id: The tenant ID containing the bucket. name: The bucket name to delete.
Inputs: tenant_id (required), name (required). Returns: result
bucket_getC
Get details of a specific S3 bucket.
Args: tenant_id: The tenant ID containing the bucket. name: The bucket name to look up.
Inputs: tenant_id (required), name (required). Returns: result
bucket_listB
List all S3 buckets in a DuploCloud tenant.
Args: tenant_id: The tenant ID to list buckets for.
Inputs: tenant_id (required). Returns: result
bucket_updateC
Update an S3 bucket configuration.
Args: tenant_id: The tenant ID containing the bucket. name: The bucket name to update. versioning: Enable or disable versioning (optional).
Inputs: tenant_id (required), name (required), versioning. Returns: result
database_createB
Create a new RDS database instance in a DuploCloud tenant.
Args: tenant_id: The tenant ID to create the database in. identifier: The database instance identifier. engine: Database engine (e.g. mysql, postgres, mariadb). size: Instance class (e.g. db.t3.micro). master_username: Master database username. Defaults to 'master'. master_password: Master database password. Required for most engines.
Inputs: tenant_id (required), identifier (required), engine (required), size (required), +2 more. Returns: result
database_deleteC
Delete an RDS database instance from a DuploCloud tenant.
Args: tenant_id: The tenant ID containing the database. name: The database instance identifier to delete.
Inputs: tenant_id (required), name (required). Returns: result
database_getA
Get details of a specific RDS database instance.
Args: tenant_id: The tenant ID containing the database. name: The database instance identifier.
Inputs: tenant_id (required), name (required). Returns: result
database_listA
List all RDS database instances in a DuploCloud tenant.
Args: tenant_id: The tenant ID to list databases for.
Inputs: tenant_id (required). Returns: result
database_updateC
Update an RDS database instance. Currently supports resizing.
Args: tenant_id: The tenant ID containing the database. name: The database instance identifier. size: New instance class (e.g. db.t3.small).
Inputs: tenant_id (required), name (required), size. Returns: result
ecs_service_deleteB
Delete an ECS service from a DuploCloud tenant.
Args: tenant_id: The tenant ID containing the ECS service. name: The ECS service name to delete.
Inputs: tenant_id (required), name (required). Returns: result
ecs_service_listC
List all ECS services in a DuploCloud tenant.
Args: tenant_id: The tenant ID to list ECS services for.
Inputs: tenant_id (required). Returns: result
ecs_service_updateC
Update the image of an ECS service's task definition.
Args: tenant_id: The tenant ID containing the ECS service. name: The task definition family name. image: The new Docker image to deploy.
Inputs: tenant_id (required), name (required), image (required). Returns: result
ecs_task_def_listB
List all ECS task definition families in a DuploCloud tenant.
Args: tenant_id: The tenant ID to list task definitions for.
Inputs: tenant_id (required). Returns: result
ecs_task_listB
List running ECS tasks for a specific service.
Args: tenant_id: The tenant ID containing the ECS service. service_name: The ECS service name to list tasks for.
Inputs: tenant_id (required), service_name (required). Returns: result
ecs_task_runC
Run an ECS task from a task definition family.
Args: tenant_id: The tenant ID to run the task in. family_name: The task definition family name. replicas: Number of task instances to run. Defaults to 1.
Inputs: tenant_id (required), family_name (required), replicas. Returns: result
host_createB
Create a new host (VM) in a DuploCloud tenant.
Args: tenant_id: The tenant ID to create the host in. friendly_name: A friendly name for the host. capacity: The instance type/size (e.g. t3.medium). agent_platform: The agent platform type. 0=Linux Docker, 7=EKS Linux. Defaults to 0.
Inputs: tenant_id (required), friendly_name (required), capacity (required), agent_platform. Returns: result
host_deleteB
Terminate a host in a DuploCloud tenant.
Args: tenant_id: The tenant ID containing the host. name: The host name to delete.
Inputs: tenant_id (required), name (required). Returns: result
host_getB
Get details of a specific host by name.
Args: tenant_id: The tenant ID containing the host. name: The host name to look up.
Inputs: tenant_id (required), name (required). Returns: result
host_listB
List all hosts (virtual machines) in a DuploCloud tenant.
Args: tenant_id: The tenant ID to list hosts for.
Inputs: tenant_id (required). Returns: result
host_rebootC
Reboot a host in a DuploCloud tenant.
Args: tenant_id: The tenant ID containing the host. name: The host name to reboot.
Inputs: tenant_id (required), name (required). Returns: result
service_createB
Create a new service in a DuploCloud tenant.
Args: tenant_id: The tenant ID to create the service in. name: Name for the new service. image: Docker image to deploy (e.g. nginx:latest). replicas: Number of replicas to run. Defaults to 1.
Inputs: tenant_id (required), name (required), image (required), replicas. Returns: result
service_deleteC
Delete a service from a DuploCloud tenant.
Args: tenant_id: The tenant ID containing the service. name: The service name to delete.
Inputs: tenant_id (required), name (required). Returns: result
service_getC
Get details of a specific service by name.
Args: tenant_id: The tenant ID containing the service. name: The service name to look up.
Inputs: tenant_id (required), name (required). Returns: result
service_listB
List all services in a DuploCloud tenant.
Args: tenant_id: The tenant ID to list services for.
Inputs: tenant_id (required). Returns: result
service_restartC
Restart a service, triggering a rolling redeployment.
Args: tenant_id: The tenant ID containing the service. name: The service name to restart.
Inputs: tenant_id (required), name (required). Returns: result
service_updateB
Update an existing service. Provide only the fields to change.
Args: tenant_id: The tenant ID containing the service. name: The service name to update. image: New Docker image (optional). replicas: New replica count (optional).
Inputs: tenant_id (required), name (required), image, replicas. Returns: result
tenant_createC
Create a new DuploCloud tenant.
Args: account_name: Name for the new tenant. plan_id: The infrastructure plan ID to associate with.
Inputs: account_name (required), plan_id (required). Returns: result
tenant_deleteB
Delete a DuploCloud tenant by name.
Args: name: The tenant name to delete.
Inputs: name (required). Returns: result
tenant_getB
Get details of a specific DuploCloud tenant by name.
Args: name: The tenant name to look up.
Inputs: name (required). Returns: result
tenant_listA
List all tenants accessible in the DuploCloud portal.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 31 tools
Each tool has a clearly distinct purpose targeting specific resources (buckets, databases, ECS services, hosts, services, tenants) with well-defined actions (create, delete, get, list, update, restart, reboot, run). There is no ambiguity or overlap between tools, as each combines a resource type with a unique operation.
All tools follow a consistent verb_noun pattern with snake_case, such as bucket_create, database_list, ecs_service_update, host_reboot, service_restart, and tenant_delete. The naming is uniform across all 31 tools, making them predictable and easy to understand.
With 31 tools, the count is borderline high for a single server, potentially feeling heavy. However, given the broad scope covering multiple AWS services (S3, RDS, ECS, EC2) and DuploCloud-specific operations, it is reasonable but could be overwhelming for agents due to the volume.
The tool set provides comprehensive CRUD/lifecycle coverage for each resource type (buckets, databases, hosts, services, tenants) and includes additional operations like restart, reboot, and run. Minor gaps exist, such as no update for tenants and limited ECS service operations (e.g., missing create), but core workflows are well-covered.
Related MCP Connectors
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Cloud cost, inventory and governance on AWS/Azure/GCP. Read-only by default, optional scoped writes
Manage your HyperLake data lake: clusters, catalogs, access policy, apps and agents.
Manage team cloud resources: services, members, access grants, secrets, tokens and storage.