Skip to Content
vVozoraDocs
Guides

Connect an AI agent to Vozora with MCP

Connect Claude Code, claude.ai and other MCP clients to your Vozora account with OAuth, choose what the agent may do, and disconnect it.

The Vozora MCP server lets an AI agent manage your account with the same operations as the API. It is at:

https://www.vozora.io/api/mcp

This agent will be able to spend your credit

It can create servers and other paid resources, which are charged to your prepaid credit, and it can delete servers and data. We ask agents to check with you first, but an agent is software you chose and may not always ask. You are responsible for what it does. Limit it with the permissions below, and disconnect it at any time.

An agent can only spend credit you have already added. It cannot top up, pay by card or order a monthly server: those need you, in the console.

Before you start

  • A Vozora account with a verified email address.
  • Credit on the account, and a saved SSH key, if you want the agent to create servers.
  • A client that supports remote MCP servers over HTTP with OAuth sign-in.

How signing in works

You never paste a key. The first time the agent connects, it opens a Vozora page in your browser. Sign in if you are not already, and you see the agent's name and the permissions it is asking for. The read-only ones are ticked; tick the others you want it to have, or untick any you do not, then choose Approve.

Approve only an agent you started yourself. If a page asks you to approve an agent you were not expecting, choose Deny.

The agent then appears under Settings → Connected agents in the console, with what you allowed. It stays connected until you disconnect it there, or until it has not been used for 30 days.

Connect your client

Each client has its own way of adding a remote MCP server; give it the address above and it does the rest. These follow each client's own documentation.

Claude Code

claude mcp add --transport http vozora https://www.vozora.io/api/mcp

Then run /mcp in a Claude Code session, choose vozora, and finish signing in in your browser.

claude.ai

Open Settings → Connectors → Add custom connector, and paste:

https://www.vozora.io/api/mcp

Other clients

Add a remote (HTTP) MCP server with the address above. A client that supports OAuth finds the rest for itself from:

https://www.vozora.io/.well-known/oauth-protected-resource/api/mcp

A client that can only send a fixed Authorization header cannot connect: the MCP server does not accept API keys. Use the API from such a tool instead.

Check it works

Ask the agent "what Vozora account am I connected to?". It should call account_get and tell you your email address and what it is allowed to do.

Tools and the permission each needs

The agent is offered only the tools your approval covers. Calling any other is refused.

ToolPermissionWhat it does
account_getanyThe account this key belongs to, the key itself and what it may do.
billing_getbilling:readCredit balance in pounds, what the account's hourly servers cost per hour, usage so far this month and credit history.
plans_listservers:readServer sizes on sale, with their hourly price in pounds.
images_listservers:readOperating system images a server can be created from.
servers_listservers:readEvery server in the account.
servers_createservers:writeCreate an hourly server, paid from credit. It is returned at once in state "starting"; read it again until it is "running". The account needs credit for 24 hours of all its servers. Spends credit.
servers_getservers:readOne server. To connect: ssh <login_user>@<ipv4> with its SSH key, then sudo for root. There is no root password.
servers_deleteservers:writeDelete a server and its backups for good; it answers once the server is gone (up to two minutes). A monthly server is instead set to end with its paid period, and is returned with cancel_at set. Cannot be undone.
servers_powerservers:writeStop, start or reboot a server. A stopped server costs the same as a running one.
servers_resizeservers:writeMove a stopped hourly server to a larger size. A disk cannot shrink, so there is no way back down. Spends credit.
servers_reinstallservers:writeReplace a server's disk with a fresh operating system. Everything on it and all its backups are lost; its name, addresses and size stay. Cannot be undone.
servers_set_firewallsservers:writeSet which firewalls a stopped server is in.
servers_reverse_dns_getservers:readThe host name a server's addresses resolve back to.
servers_reverse_dns_setservers:writeSet the host name a server's addresses resolve back to, for mail servers. An empty name clears it.
backups_listservers:readA server's backups, newest first, and whether a daily backup is on.
backups_createservers:writeStart a backup of a server's disk now. It appears in the list as it completes. Spends credit.
backups_set_dailyservers:writeTurn a server's daily backup on or off. The newest seven are kept; turning it off keeps those already taken. Spends credit.
backups_restoreservers:writePut a stopped server's disk back to how it was when a backup was taken. Everything since is lost. Cannot be undone.
backups_deleteservers:writeDelete one backup. Cannot be undone.
ssh_keys_listssh_keys:readSaved SSH public keys.
ssh_keys_createssh_keys:writeSave an SSH public key under a name, to put on new servers.
ssh_keys_getssh_keys:readOne saved SSH key.
ssh_keys_deletessh_keys:writeDelete a saved SSH key. Servers already created with it keep it. Cannot be undone.
firewalls_listfirewalls:readFirewalls and their rules. A firewall blocks all inbound traffic that no rule allows; outbound is open.
firewalls_createfirewalls:writeCreate an empty firewall, which allows nothing in until rules are added.
firewalls_getfirewalls:readOne firewall and its rules.
firewalls_deletefirewalls:writeDelete a firewall no server is in. The default firewall cannot be deleted. Cannot be undone.
firewall_rules_createfirewalls:writeAllow inbound traffic through a firewall. Takes effect at once on every server in it.
firewall_rules_deletefirewalls:writeRemove a rule from a firewall. Cannot be undone.
networks_listnetworks:readPrivate networks and the servers on them.
networks_createnetworks:writeCreate a private network, with its own address range, for servers to reach each other on. Spends credit.
networks_getnetworks:readOne private network.
networks_deletenetworks:writeDelete a private network that has no servers on it. Cannot be undone.
networks_attachnetworks:writePut a server on a private network. It gets an address there by DHCP. Can take a minute for a network's first server.
networks_detachnetworks:writeTake a server off a private network.
volumes_listvolumes:readVolumes: extra disks that can be moved between servers.
volumes_createvolumes:writeCreate a volume, either empty at a size in GB or holding a snapshot's contents. Spends credit.
volumes_getvolumes:readOne volume.
volumes_deletevolumes:writeDelete a detached volume and everything on it. Its snapshots are kept. Cannot be undone.
volumes_attachvolumes:writeAttach a volume to a server. It appears there as a new disk to format and mount.
volumes_detachvolumes:writeDetach a volume from its server. Unmount it inside the server first.
snapshots_listvolumes:readSnapshots of volumes.
snapshots_createvolumes:writeStart a snapshot of a volume. It appears in the list as it completes. Spends credit.
snapshots_deletevolumes:writeDelete a snapshot. Cannot be undone.
dns_zones_listdns:readDomains hosted on Vozora DNS, with their records and the nameservers to point each domain at.
dns_zones_createdns:writeAdd a domain. It answers once the domain's registrar points it at the nameservers returned; until then it is unverified.
dns_zones_getdns:readOne domain and its records.
dns_zones_deletedns:writeDelete a domain and all its records. It stops answering at once. Cannot be undone.
dns_records_setdns:writeSet every value of one name and type, replacing what was there. Use the name @ for the domain itself.
dns_records_deletedns:writeRemove every value of one name and type. Cannot be undone.
buckets_liststorage:readObject storage buckets, how much each holds, and the S3 endpoint to connect to.
buckets_createstorage:writeCreate a private bucket. Bucket names are shared by every customer, like domain names. Spends credit.
buckets_getstorage:readOne bucket.
buckets_updatestorage:writeChange a bucket's size limit, versioning, or whether anyone may read and list it without a key.
buckets_deletestorage:writeDelete a bucket and every object in it. Cannot be undone.
storage_key_getstorage_keys:readThe S3 access key and secret for all of the account's buckets. There is none before the first bucket.
storage_key_rotatestorage_keys:writeReplace the S3 key. The old one stops working at once. Cannot be undone.

A server comes back with its addresses and its login_user, so an agent can tell you the exact command to connect: ssh ubuntu@203.0.113.10, say, then sudo for root.

Keep an agent on a short lead

  1. Start read-only. Approve only the :read permissions until you trust how the agent behaves, then connect again with more.
  2. Keep credit modest. An agent cannot add credit, and servers are stopped a day after credit runs out.
  3. Read before you say yes. Tools that spend credit or cannot be undone tell the agent to confirm with you first. Check the name and size of what it is about to create or delete.
  4. Disconnect what you no longer use, under Settings → Connected agents. It stops working at once.

Common refusals

The agent saysWhyWhat to do
missing_scopeYou did not approve the permission that tool needsDisconnect, connect again and tick it
refused: add creditThe account lacks credit for 24 hours of its serversAdd credit in the console
refused: stop the server firstSome changes need a stopped serverAsk the agent to stop it, then retry
not_foundNothing with that id in your accountAsk the agent to list first
No longer connectedYou disconnected it, or it went unused for 30 daysConnect again

Next

  • API reference: the same operations over HTTP, with a key, for scripts and Terraform.

On this page

Vozora is a trading name of Bankside Technology Ltd, company no. 17253446.TermsPrivacysupport@vozora.io