tport-cloud-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TPORT_API_KEY | Yes | Your tport.cloud API key (tpct_...). Needed for everything except list_plans. | |
| TPORT_API_URL | No | Optional base URL of the tport.cloud API | https://api.tport.cloud |
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 |
|---|---|
| list_plansB | What can be ordered: plans with monthly price (cents), vCPU, RAM, disk; regions; images; installs (python, node, postgresql...); which plan is available in which region. No key needed. |
| list_serversA | Your servers and shared accounts with status, plan, region and IP. Scope servers:read. |
| get_serverA | One server or shared account in detail: status, IP, plan, price, paid until, recent events. Scope servers:read. |
| create_serverA | Order a server (kind server = own root server) or a shared account (kind shared). The first 30 days are charged from the account balance; setup takes a few minutes (watch it with get_order or get_server). Ubuntu 24.04 only. A root server without ssh_keys answers a one-time root password once. Scope servers:create. |
| get_orderB | An order's progress (queued, creating, ready, failed) with its item id. Scope servers:read. |
| resize_serverA | Move a server or shared account up to a bigger plan of the same kind. The difference for the days already paid is charged from the balance now; then the new price applies. Smaller plans are refused. Scope servers:resize. |
| powerC | Start, stop or restart a server. Scope servers:power. |
| delete_serverA | Delete a server or shared account and everything on it; unused days go back to the balance. Cannot be undone. Scope servers:delete. |
| databases_listA | Your managed PostgreSQL clusters with status, plan and region. Scope databases:read. |
| databases_getA | One managed PostgreSQL cluster: status, connection details, pooler, standby, allow list. Scope databases:read. |
| databases_createA | Order a managed PostgreSQL cluster (plan kind pg from list_plans: single node or with standby). The first 30 days are charged from the balance. Scope databases:write. |
| databases_set_allowA | Replace a cluster's allow list (who may connect). An empty list closes it. Scope databases:write. |
| databases_deleteA | Delete a managed PostgreSQL cluster and its data; unused days go back to the balance. Cannot be undone. Scope databases:write. |
| dns_list_zonesA | Your DNS zones on the free tport.cloud nameservers, the nameservers to set at your registrar and the record types offered. Scope dns:read. |
| dns_get_zoneC | All records of one zone. Scope dns:read. |
| dns_add_zoneB | Host a domain on the free tport.cloud nameservers, optionally with an apex A/AAAA record. Scope dns:write. |
| dns_delete_zoneA | Delete a zone and all its records. Scope dns:write. |
| dns_add_recordB | Add a record (A, AAAA, CNAME, MX, TXT, SRV, CAA, NS...), or edit one by passing the old value in replace. Scope dns:write. |
| dns_delete_recordA | Delete records by name and type, or just the one with this value. Scope dns:write. |
| get_billingA | Account balance, monthly spend and recent ledger lines. Scope billing:read. |
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 20 tools
Each tool targets a distinct resource+action pair, and the DNS/databases namespacing makes boundaries obvious. Minor soft spots: `power` is a generic name that could be confused with lifecycle ops like `resize_server`, and `dns_add_record` doubles as an edit tool (via `replace`), blurring add vs. update.
Two conventions coexist: unprefixed verb_noun for servers/billing/orders (list_servers, create_server, get_billing) and a resource-prefixed form for DNS and databases (dns_list_zones, databases_set_allow). `power` breaks both patterns as a bare noun with no object or verb, making the scheme only partially predictable.
Twenty tools spread across four product areas (servers, DNS, databases, billing) — roughly 4-6 per area, and each one covers a real operation rather than a redundant variant. Slightly heavy overall, but the breadth of the domain justifies the count.
Servers have full lifecycle (list/get/create/resize/power/delete plus order tracking), DNS covers zone and record create/read/delete, and databases cover create/read/allow-list/delete. Gaps remain: no server rebuild/SSH-key management despite `create_server` referencing ssh_keys, and no database scaling, backup, or user management.