tport-cloud-mcp
Manage tport.cloud servers, PostgreSQL clusters, DNS, and billing via MCP.
Browse plans, prices, regions, images, installs, and availability without an API key.
List/inspect servers, shared accounts, and orders; create, resize, power-control, and delete servers with confirmation for destructive actions.
List/inspect managed PostgreSQL clusters; create clusters with region/version/allow list, replace allow lists, and delete clusters with typed-name confirmation.
Manage free DNS zones and records: list zones/records, add/delete zones, and add/edit/delete record types such as A, AAAA, CNAME, MX, TXT, SRV, CAA, and NS.
Check account balance, monthly spend, and recent billing ledger.
API key scopes govern which actions are allowed.
Provides tools for managing managed PostgreSQL clusters through tport.cloud, including listing and retrieving clusters, ordering new clusters, configuring allow lists, and deleting clusters.
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., "@tport-cloud-mcp order a 4GB root server in Frankfurt with Ubuntu 24.04"
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.
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
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).
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 |
| Your API key ( |
| Optional, default |
Related MCP server: TuxCare ePortal MCP Server
Tools
Tool | Does | Scope |
| Plans, prices, regions, images, installs (about 50 apps, with the ones each plan takes), availability | none |
| Your servers and shared accounts, one in detail, an order's progress |
|
| Order a root server or shared account (charged from the balance) |
|
| Move to another plan of the same kind |
|
| Start, stop, restart |
|
| Delete (typed name to confirm; unused days credited) |
|
| Database engines, add-ons, prices, sizes per region, availability | none |
| Your managed databases, one in detail (the login, once) |
|
| Who reached a database: IPs, first/last seen, connections, refused tries |
|
| Order, allow list, resize, delete |
|
| Primary + standby PostgreSQL clusters |
|
| Order, allow list, delete |
|
| A server's own domains and the records to set |
|
| Your own domain on a small server |
|
| Zones and records on the free nameservers |
|
| Change zones and records |
|
| Balance and ledger |
|
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` binMIT licence. (c) Biz59 LLC.
Available Tools
20 toolscreate_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_deleteADestructive
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_getARead-only
One managed PostgreSQL cluster: status, connection details, pooler, standby, allow list. Scope databases:read.
Inputs: id (required).
databases_listARead-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_serverADestructive
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_recordADestructive
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_zoneADestructive
Delete a zone and all its records. Scope dns:write.
Inputs: zone (required), confirm (required).
dns_get_zoneCRead-only
All records of one zone. Scope dns:read.
Inputs: zone (required).
dns_list_zonesARead-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_billingARead-only
Account balance, monthly spend and recent ledger lines. Scope billing:read.
Inputs: no named parameters.
get_orderBRead-only
An order's progress (queued, creating, ready, failed) with its item id. Scope servers:read.
Inputs: order_id (required).
get_serverARead-only
One server or shared account in detail: status, IP, plan, price, paid until, recent events. Scope servers:read.
Inputs: id (required).
list_plansBRead-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_serversARead-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
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.
Maintenance
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
- AlicenseBqualityDmaintenanceEnables management of Timeweb Cloud resources including servers, databases, Kubernetes clusters, S3 storage, DNS, SSH keys, and floating IPs through natural language.977 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables management of TuxCare ePortal resources such as servers, feeds, registration keys, patchsets, and users through the ePortal API, with support for basic and API key authentication.13 npmMIT

Hostodo MCPofficial
AlicenseBqualityDmaintenanceManage Hostodo VPS infrastructure from MCP clients and AI agents with scoped tokens and audit logs.471MIT- AlicenseBqualityBmaintenanceEnables AI agents to autonomously govern cloud hosting infrastructure and billing workflows, including provisioning, invoices, wallet credits, support tickets, and catalog management through 35 tools with JSON:API response hydration.35MIT