Manage your cloud by talking to AI
Add Tres to your AI application as a connector, sign in — done. From now on, all you have to do to spin up a server, take a backup or set up a network is have a conversation.
The connector runs only with your permissions, within approval and audit boundaries.
Connect in three steps, start the conversation
Setup takes minutes. Paste a URL, sign in with your account — the rest is just conversation.
Go to the “Connector” section of your AI application and paste Tres’s connection address (URL). No plugin, setup or code required.
Sign in with your Tres account and grant access. The connector can only do what you allow, limited to your account’s permissions.
That’s all. From now on you spin up servers, take backups and manage your network just by talking to your AI — without ever opening the panel.
Works with the AI you love
MCP is an open standard — you choose your application, no lock-in.
Just write; let your assistant handle the rest
The things you used to do by clicking in the panel, now in a single sentence. Here are a few examples of what the connector looks like in everyday life.
A new server in a single sentence
Just tell it the location, cores, memory and operating system. Your assistant picks the right package, provisions the server and brings you the connection details — without navigating a single panel screen.
Automatic backups, in one request
Which server, how often — your assistant handles the rest. The backup plan is set up in the background; your critical data is secured every day, with no effort from you.
Manage ports by talking
Just write which ports you want to keep open. Your assistant updates the security group and closes the rest; your server stays open only to the traffic you allow.
Your isolated network in seconds
Isolate your servers from the outside world. Your assistant creates a private network and connects your servers to it; your internal traffic stays on your own network, secure.
The AI has access; but only within the boundaries you draw
The connector is built on the panel’s real role-based permission, approval flow and audit logging layer. Control always stays with you.
The connector cannot go beyond your account’s role-based permissions. You decide what is allowed.
Steps like deleting a server or changing scale are not applied automatically; nothing runs until you approve.
Every action coming through the AI is written to the audit log with its source IP and port.
Frequently asked questions
Just add Tres’s connection address (URL) to the “Connector” section of your AI application and sign in with your Tres account. No plugin, setup or code required; it connects in a few minutes and you start managing your infrastructure in natural language.
Because MCP (Model Context Protocol) is an open standard, it works with all MCP-compatible applications such as Claude, ChatGPT, Gemini, Copilot and Cursor. You are not locked into a specific product; you choose the application you use yourself.
The connector cannot go beyond your Tres account’s role-based permissions (RBAC); you decide which actions are permitted. Critical actions such as deleting a server require your approval and do not run automatically. Every action coming through the AI is written to the audit log with its source IP and port.
Your infrastructure operations and audit logs are stored on our infrastructure within Turkey, which we run in Tier III+ data centers; it is compliant with KVKK and Law No. 5651. Your natural-language command is interpreted in the AI application you choose, while the operation is carried out securely on the Tres side.
There is no extra charge for the connection itself; only the resources you create (server, IP, backup, etc.) are billed pay-as-you-go, as always. Contact us for detailed information.
Add the connector, start the conversation
Open a free account, add the Tres connector to your AI application and sign in, and start managing your infrastructure in natural language — our engineering team is with you, from setup to authorization.