contabo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTABO_API_USER | Yes | API user email | |
| CONTABO_AUTH_URL | No | Contabo OAuth2 token endpoint (default is the Contabo token endpoint) | |
| CONTABO_CLIENT_ID | Yes | OAuth2 client id | |
| CONTABO_TIMEOUT_MS | No | Per-request timeout in milliseconds | 30000 |
| CONTABO_API_BASE_URL | No | Base URL for the Contabo API | https://api.contabo.com |
| CONTABO_API_PASSWORD | Yes | API password | |
| CONTABO_CLIENT_SECRET | Yes | OAuth2 client secret | |
| CONTABO_ENABLE_WRITES | No | Set to `1` to enable non-GET operations (POST/PATCH/PUT/DELETE). Default is read-only. | 0 |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| contabo_instancesA | Contabo compute instances (VPS/VDS). Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_snapshotsA | Contabo instance snapshots. Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_imagesA | Contabo standard and custom images. Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_objectStorageA | Contabo S3-compatible object storages and data centers. Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_privateNetworksA | Contabo private networks (VPC). Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_firewallsA | Contabo firewalls and their rules. Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_dnsA | Contabo DNS zones, records and PTR records. Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_domainsA | Contabo domains and contact handles. Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_vipsA | Contabo virtual IPs (VIP). Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_secretsA | Contabo secrets (SSH keys, passwords). Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_tagsA | Contabo tags and tag assignments. Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_usersA | Contabo users, roles, accounts and object-storage credentials. Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_auditsA | Contabo audit logs for every resource type. Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_troubleshootingA | Contabo troubleshooting checks, check collections and remedies. Choose exactly one 'operation'; every operation has its own parameter set (validated per operation). This server runs READ-ONLY: write operations are rejected until it is started with CONTABO_ENABLE_WRITES=1. Operations:
Use the contabo_reference tool for full parameter documentation of any operation. |
| contabo_referenceA | Documentation for every Contabo MCP operation. Pass a domain to list its operations; pass domain + operation to get full parameter documentation (types, required fields, enums, defaults, descriptions and the exact input JSON Schema). |
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 15 tools
Each tool maps to a clearly distinct resource domain (firewalls, instances, snapshots, DNS, domains, etc.), so intent is easy to select. Minor overlap exists where the audits tool exposes history for resources that also have their own dedicated tools, and cross-cutting 'assignInstance'/'assign' verbs appear across several tools, but descriptions disambiguate well.
All tools share the consistent 'contabo_' prefix and operations are uniformly camelCase (create, list, get, update, delete, resetPassword). The only deviation is casing of the domain suffix, mixing lowercase (firewalls, dns) with camelCase (objectStorage, privateNetworks), plus a few operation names that mix resource-qualified forms (listHandles, getZone) with bare verbs (list, get).
15 tools sits at the top of the comfortable range but is well-scoped: each corresponds to a real resource family. The pattern of one tool per domain with an 'operation' selector keeps the visible surface manageable even though underlying operation counts (users, domains, audits) are high.
Coverage is broad, spanning firewalls, instances, snapshots, images, object storage, VPC, DNS, domains, VIPs, secrets, tags, users, audits, and troubleshooting, with a reference tool for parameter docs. Minor gaps: bare metal is only referenced via VIP assignment, and object-storage buckets/objects themselves are not exposed, but core lifecycle CRUD is present throughout.