Vultr MCP integration for AI agents.
Connect AI agents to Vultr through 14 structured actions, including get account, create instance, delete instance, and manage instance power. Review authenti…
- ACTION CONTRACTS
- 14
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Vultr integration exposes
The Vultr Agent App exposes 14 provider-backed actions for developer tools work. Its current contract lets an authorized agent retrieve the connected vultr account profile, acl permissions, balance, and billing summary, create a vultr vps instance from an os, iso, snapshot, application, or application image, and permanently delete a vultr vps instance. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Vultr account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Vultr capabilities.
Showing 12 of 14 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADRetrieve the connected Vultr account profile, ACL permissions, balance, and billing summary.
create_instanceWRITECreate a Vultr VPS instance from an OS, ISO, snapshot, application, or application image.
delete_instanceHIGH IMPACTPermanently delete a Vultr VPS instance.
INPUTS: instanceId
manage_instance_powerREVIEWStart, reboot, or halt a Vultr VPS instance.
INPUTS: instanceId / operation
get_instanceREADRetrieve one Vultr VPS instance by ID.
INPUTS: instanceId
list_domain_recordsREADList DNS records for one domain in the connected Vultr account.
INPUTS: domain / perPage / cursor
list_domainsREADList DNS domains in the connected Vultr account.
INPUTS: perPage / cursor
list_firewall_groupsREADList firewall groups in the connected Vultr account.
INPUTS: perPage / cursor
list_instancesREADList Vultr VPS instances with cursor pagination and common instance filters.
INPUTS: perPage / cursor / label / mainIp / region
list_operating_systemsREADList operating system images available for Vultr instance deployment.
INPUTS: perPage / cursor
list_plansREADList Vultr VPS plans with optional plan-type and Windows compatibility filters.
INPUTS: perPage / cursor / type / operatingSystem
list_regionsREADList Vultr deployment regions and the product features available in each region.
INPUTS: perPage / cursor
INPUT CONTRACTS
Know what the action needs before it runs.
delete_instance
instanceIdREQUIRED- The Vultr instance ID.
manage_instance_power
instanceIdREQUIRED- The Vultr instance ID.
operationREQUIRED- Power operation to perform on the instance.
get_instance
instanceIdREQUIRED- The Vultr instance ID.
list_domain_records
domainREQUIRED- Registered domain name whose DNS records should be listed.
perPageOPTIONAL- Maximum number of items to return, from 1 to 500.
cursorOPTIONAL- The next or previous cursor returned in pagination metadata.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Retrieve the connected Vultr account profile, ACL permissions, balance, and billing summary. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountControl Create Instance
Create a Vultr VPS instance from an OS, ISO, snapshot, application, or application image. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_instanceVerify with Get Instance
Retrieve one Vultr VPS instance by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_instanceSAFETY BOUNDARY
Operate Vultr with explicit limits
- Authorize Vultr with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_instance` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `provisioning`, `subscriptions`, `subscriptions_view`, and `dns`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Vultr task completed successfully.
CONNECTION MODEL
API key
Vultr API key sent as a Bearer token. Create a key in the Vultr customer portal under Account > API, and restrict it to the runtime's public IP when possible: https://my.vultr.com/settings/#settingsapi
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 10
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Vultr.