Can I use Vultr as a CLI?

Yes. KosmoKrator exposes a Vultr CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Vultr through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Vultr tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Vultr credentials stored?

Vultr credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Vultr MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Vultr CLI for Coding Agents

Use the Vultr CLI for coding agents with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write Bearer token auth

Submit Vultr feedback View package source

Vultr CLI for Coding Agents

Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

Use this pattern when another coding agent needs exact commands and schema discovery. The Vultr CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Vultr CLI for Coding Agents
kosmokrator integrations:configure vultr --set access_token="$VULTR_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call vultr.vultr_list_instances '{}' --json

Discovery Before Execution

Agents and scripts can inspect Vultr docs and schemas before choosing a function.

kosmo integrations:docs vultr --json
kosmo integrations:docs vultr.vultr_list_instances --json
kosmo integrations:schema vultr.vultr_list_instances --json
kosmo integrations:search "Vultr" --json
kosmo integrations:list --json

Useful Vultr CLI Functions

Function	Type	Parameters	Description
`vultr.vultr_list_instances`	Read	none	List all compute instances in the Vultr account. Returns IDs, labels, status, plan, region, and IP addresses.
`vultr.vultr_get_instance`	Read	id	Get details for a specific Vultr compute instance by ID. Returns full instance information including IP addresses, plan, region, and OS.
`vultr.vultr_list_plans`	Read	none	List all available hosting plans in Vultr. Returns plan IDs, pricing, vCPU, RAM, disk, and bandwidth details.
`vultr.vultr_list_regions`	Read	none	List all available data center regions in Vultr. Returns region IDs, city, country, and continent information.
`vultr.vultr_list_snapshots`	Read	none	List all snapshots in the Vultr account. Returns snapshot IDs, descriptions, sizes, creation dates, and status.
`vultr.vultr_list_ssh_keys`	Read	none	List all SSH keys in the Vultr account. Returns key IDs, names, and creation dates.
`vultr.vultr_get_current_user`	Read	none	Get information about the current authenticated Vultr account, including email, name, and balance.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Vultr CLI Pages

CI Vultr CLI for CI. Cron Jobs Vultr CLI for cron jobs. Shell Scripts Vultr CLI for shell scripts. Headless Automation Vultr CLI for headless automation.