Use Nextify from AI assistants (MCP)

Nextify has a remote MCP server, so AI assistants such as Claude, ChatGPT, Cursor and VS Code can work with your account in plain words. Ask your assistant to compare plans and prices, create a server with your SSH key, put servers behind a load balancer with a domain, or tell you what you have spent this month.

The setup steps for each assistant are on the MCP page. This article explains what an assistant can do once it is connected, and what to watch for.

1. Two addresses

Signing in. When you add the server, your assistant opens the Nextify sign-in page. Sign in with your normal Nextify email and password, then approve the assistant on the consent screen. From then on it acts as you, within your account's limits, exactly as if you were using the portal. There is no separate login for assistants.

API tokens. Assistants that cannot sign in can send an API token instead (Authorization: Bearer nxt_...). Create one in the portal under Account → API tokens. A read-only token gives you an assistant that can look at your account but never change anything.

2. What you can ask

Choose a server. For example: "I want to run PostgreSQL and a small Node.js API for about 5,000 users. Which plan should I use, and what will it cost per month?" The assistant uses recommend_plan, list_plans and get_pricing. Prices and stock come from the live catalog, never from the assistant's memory. This works without an account on the public address.

Create and manage servers. For example: "Add my SSH key, create an Ubuntu 24.04 server called web-1 with it, and tell me its IP address when it is running." The assistant adds the key (add_ssh_key), creates the server (create_instance), follows the background job until the server is ready (get_job, usually under two minutes), then reads the public IP (get_instance). It can also start and stop servers (set_instance_power) and delete them (delete_instance).

Put a website behind a load balancer. For example: "Put web-1 behind a load balancer on port 80 and add shop.example.com with a certificate." See section 3.

Check spending. For example: "What have I spent so far this month?" The assistant uses get_billing_summary.

3. Load balancers and domains

A load balancer sends traffic to a pool of your servers. To serve a website, the assistant creates the load balancer with an HTTP pool of your servers (create_load_balancer, with the servers and the port they listen on, usually 80). Then it adds your domain (add_domain).

• add_domain needs that pool. On a load balancer created with no pool it answers no_http_pool. If you see that, ask the assistant to add your servers to the load balancer, or add a pool in the portal under Network → Load balancers → Backends, then add the domain again.
• add_domain returns the DNS record to create at your DNS provider: an A record pointing your domain at the load balancer's public IP. The Let's Encrypt certificate is issued once the record resolves. Ask "Is the certificate for shop.example.com ready?" and the assistant checks with list_domains.
• The load balancer reaches your servers over your account's private network, which is created with your first server.

For everything a load balancer can do (TCP and UDP services, routing rules, health checks), see Getting started with load balancers.

4. Costs and safety

• Creating servers and load balancers costs money. They are billed by the hour at the published prices, exactly as if you had created them in the portal. Renting needs a card on file or account credit. Without either, the assistant gets a "payment method required" answer telling you what to do next.
• Most assistants ask before using a tool that changes something. Read what the assistant is about to create or delete before you allow it.
• Deleting a server deletes its boot disk, and this cannot be undone. delete_instance only works when the assistant repeats the server's exact name, so it cannot delete the wrong server by mistake. If the name does not match, nothing is deleted.
• Some plans are too small for some images. Ubuntu needs at least 1 GB of memory, for example. Ask the assistant to list the images for a plan (list_images), and it will offer only images that boot on that plan.
• Your assistant can only see and change your own account. Account limits and rate limits apply as usual. To cut off an assistant, revoke its API token in the portal, or remove the connector in the assistant.

5. All tools

Everything the tools do goes through the same API the portal uses. Scripts and tools of your own can call it directly with an API token.