Skip to main content
Glama

tport-cloud-mcp

MCP server for tport.cloud: order and manage servers, managed databases and free DNS from Claude, Cursor or any MCP client. It runs on your machine over stdio and calls the tport.cloud API with your API key.

Set up

  1. In the console (https://app.tport.cloud) make an API key and tick only the scopes you want the assistant to have. A key can only do what its scopes allow; the API refuses the rest (403 naming the missing scope).

  2. Add the server to your MCP client.

Claude Desktop (claude_desktop_config.json) or Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "tport-cloud": {
      "command": "npx",
      "args": ["-y", "tport-cloud-mcp"],
      "env": { "TPORT_API_KEY": "tpct_..." }
    }
  }
}

Claude Code: claude mcp add tport-cloud -e TPORT_API_KEY=tpct_... -- npx -y tport-cloud-mcp

Env

Meaning

TPORT_API_KEY

Your API key (tpct_...). Needed for everything except list_plans.

TPORT_API_URL

Optional, default https://api.tport.cloud.

Related MCP server: TuxCare ePortal MCP Server

Tools

Tool

Does

Scope

list_plans

Plans, prices, regions, images, installs (about 50 apps, with the ones each plan takes), availability

none

list_servers, get_server, get_order

Your servers and shared accounts, one in detail, an order's progress

servers:read

create_server

Order a root server or shared account (charged from the balance)

servers:create

resize_server

Move to another plan of the same kind

servers:resize

power

Start, stop, restart

servers:power

delete_server

Delete (typed name to confirm; unused days credited)

servers:delete

data_catalogue

Database engines, add-ons, prices, sizes per region, availability

none

data_list, data_get

Your managed databases, one in detail (the login, once)

databases:read

data_connections

Who reached a database: IPs, first/last seen, connections, refused tries

databases:read

data_create, data_set_allow, data_resize, data_delete

Order, allow list, resize, delete

databases:write

databases_list, databases_get

Primary + standby PostgreSQL clusters

databases:read

databases_create, databases_set_allow, databases_delete

Order, allow list, delete

databases:write

domains_list

A server's own domains and the records to set

dns:read

domains_add, domains_check, domains_remove

Your own domain on a small server

dns:write

dns_list_zones, dns_get_zone

Zones and records on the free nameservers

dns:read

dns_add_zone, dns_delete_zone, dns_add_record, dns_delete_record

Change zones and records

dns:write

get_billing

Balance and ledger

billing:read

A new database's login is shown once, by the first data_get after setup, so your assistant sees it and it can't be read again. Deleting asks for the item's name in confirm, as the console does. Errors come back as the API's own message.

Develop

npm install
npm test              # stub API on 127.0.0.1, end to end through an MCP client
TPORT_LIVE=1 npm test # also read-only checks against the real API (add TPORT_API_KEY to list your servers)
npm run build         # build/index.js, the `tport-cloud-mcp` bin

MIT licence. (c) Biz59 LLC.

Available Tools

20 tools
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.

Inputs: name (required), plan (required), region (required), kind, +5 more.

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.

Inputs: name (required), plan (required), region (required), allow, +1 more.

databases_deleteA
Destructive

Delete a managed PostgreSQL cluster and its data; unused days go back to the balance. Cannot be undone. Scope databases:write.

Inputs: id (required), confirm (required).

databases_getA
Read-only

One managed PostgreSQL cluster: status, connection details, pooler, standby, allow list. Scope databases:read.

Inputs: id (required).

databases_listA
Read-only

Your managed PostgreSQL clusters with status, plan and region. Scope databases:read.

Inputs: no named parameters.

databases_set_allowA

Replace a cluster's allow list (who may connect). An empty list closes it. Scope databases:write.

Inputs: id (required), allow (required).

delete_serverA
Destructive

Delete a server or shared account and everything on it; unused days go back to the balance. Cannot be undone. Scope servers:delete.

Inputs: id (required), confirm (required).

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.

Inputs: type (required), zone (required), value (required), tag, +7 more.

dns_add_zoneB

Host a domain on the free tport.cloud nameservers, optionally with an apex A/AAAA record. Scope dns:write.

Inputs: zone (required), ip.

dns_delete_recordA
Destructive

Delete records by name and type, or just the one with this value. Scope dns:write.

Inputs: name (required), type (required), zone (required), content.

dns_delete_zoneA
Destructive

Delete a zone and all its records. Scope dns:write.

Inputs: zone (required), confirm (required).

dns_get_zoneC
Read-only

All records of one zone. Scope dns:read.

Inputs: zone (required).

dns_list_zonesA
Read-only

Your DNS zones on the free tport.cloud nameservers, the nameservers to set at your registrar and the record types offered. Scope dns:read.

Inputs: no named parameters.

get_billingA
Read-only

Account balance, monthly spend and recent ledger lines. Scope billing:read.

Inputs: no named parameters.

get_orderB
Read-only

An order's progress (queued, creating, ready, failed) with its item id. Scope servers:read.

Inputs: order_id (required).

get_serverA
Read-only

One server or shared account in detail: status, IP, plan, price, paid until, recent events. Scope servers:read.

Inputs: id (required).

list_plansB
Read-only

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.

Inputs: kind.

list_serversA
Read-only

Your servers and shared accounts with status, plan, region and IP. Scope servers:read.

Inputs: no named parameters.

powerC

Start, stop or restart a server. Scope servers:power.

Inputs: id (required), action (required).

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.

Inputs: id (required), plan (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    • ThriveCart MCP server for ChatGPT, Claude and any AI agent: create product, create checkout, issue refund and list affiliates in your own ThriveCart account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to ThriveCart yourself; Cotlet does not store your password and you need no ThriveCart API key. About the official ThriveCart API: ThriveCart has an official API, but it is limited (checked 11 Oct 2026). It reads products, transactions, customers and affiliates, and it can refund, pause, resume and cancel subscriptions and approve affiliates. Setup and FAQ: https://cotlet.dev/integrations/thrivecart-api-mcp-server

    • Pirate Ship MCP server for ChatGPT, Claude and any AI agent: get rates, buy labels in bulk, import orders, track shipment and refund labels in your own Pirate Ship account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Pirate Ship yourself; Cotlet does not store your password and you need no Pirate Ship API key. About the official Pirate Ship API: Pirate Ship has no API (checked 11 Oct 2026). Its help center says so and points to store integrations and spreadsheet uploads instead. Setup and FAQ: https://cotlet.dev/integrations/pirate-ship-api-mcp-server

    • SnelStart MCP server for ChatGPT, Claude and any AI agent: create sales invoice, add relation, book entry, list open items and upload document in your own SnelStart account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to SnelStart yourself; Cotlet does not store your password and you need no SnelStart API key. About the official SnelStart API: Yes, but it is gated (checked 14 Oct 2026). SnelStart has a B2B API for software partners: you request a connection, get a development key and portal access, and a production integration for several users needs certification, OAuth, a webhook URL and at least five named customers. Setup and FAQ: https://cotlet.dev/integrations/snelstart-api-mcp-server

    • Fatture in Cloud MCP server for ChatGPT, Claude and any AI agent: create invoice, send to SDI, add client, record expense and list unpaid invoices in your own Fatture in Cloud account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Fatture in Cloud yourself; Cotlet does not store your password and you need no Fatture in Cloud API key. About the official Fatture in Cloud API: Yes, Fatture in Cloud has a documented REST API (v2) for issued invoices, clients, received documents, e-invoices to SDI and attachments (checked 14 Oct 2026), but it has no official MCP server. To use it you register an OAuth 2.0 app, or create a manual access token in the web app, choose scopes and pick the companies the token applies to. Setup and FAQ: https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server

    Related MCP Servers