VPS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORTAINER_URL | Yes | The URL of your Portainer instance | |
| PORTAINER_API_KEY | Yes | Your Portainer API key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_portainer_configB | Configure Portainer connection settings (URL, API Key, Endpoint ID). The settings are saved to the .env file. |
| get_portainer_configB | Get current Portainer configuration (API key is masked for security) |
| test_portainer_connectionB | Test the connection to Portainer API with current configuration |
| list_endpointsA | List available Portainer endpoints to find the correct Endpoint ID. Use this when you get an "Object not found" error during connection test. |
| list_containersC | List all Docker containers |
| get_containerC | Get detailed information about a specific container |
| start_containerC | Start a stopped container |
| stop_containerC | Stop a running container |
| restart_containerC | Restart a container |
| remove_containerC | Remove a container |
| create_containerC | Create a new container |
| list_imagesC | List all Docker images |
| get_imageB | Get detailed information about a specific image |
| pull_imageC | Pull an image from a registry |
| remove_imageC | Remove an image |
| list_networksA | List all Docker networks |
| create_networkC | Create a new Docker network |
| remove_networkC | Remove a Docker network |
| list_volumesA | List all Docker volumes |
| create_volumeC | Create a new Docker volume |
| remove_volumeC | Remove a Docker volume |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific Docker/Portainer resources (containers, images, networks, volumes, Portainer config) and actions (create, get, list, remove, start/stop/restart), making it easy for an agent to select the correct one. For example, 'create_container' vs 'start_container' serve different lifecycle stages.
All tool names follow a consistent verb_noun pattern using snake_case throughout. Verbs like create, get, list, remove, start, stop, restart, pull, test, and set are applied predictably to nouns like container, image, network, volume, and portainer_config. There are no deviations in naming conventions.
With 21 tools, the count is slightly high but reasonable for the server's purpose of managing Docker and Portainer operations. It covers a comprehensive set of actions across multiple resource types, though it might feel heavy compared to a more minimal set. Each tool earns its place by addressing a specific need in container management.
The tool surface provides complete CRUD/lifecycle coverage for Docker resources (containers, images, networks, volumes) and Portainer configuration. It includes creation, retrieval, listing, removal, and operational controls (start/stop/restart), with no obvious gaps. The Portainer tools handle connection testing and configuration, ensuring agents can manage the full workflow.