KosmoKrator

productivity

Vultr MCP Gateway for AI Agents

Expose Vultr tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.

7 functions 7 read 0 write Bearer token auth
Submit Vultr feedback View package source

Vultr MCP Gateway

Expose Vultr to MCP clients with `kosmokrator mcp:serve --integration=vultr`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server. The gateway exposes only the selected integration in the example below. 

curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash
kosmokrator mcp:gateway:install --integration=vultr --write=deny --json
{
  "mcpServers": {
    "kosmokrator-vultr": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=vultr",
        "--write=deny"
      ]
    }
  }
}

Serve Manually

kosmokrator mcp:serve --integration=vultr --write=deny

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names:

MCP toolSource functionType
integration__vultr__vultr_list_instances vultr.vultr_list_instances Read read
integration__vultr__vultr_get_instance vultr.vultr_get_instance Read read
integration__vultr__vultr_list_plans vultr.vultr_list_plans Read read
integration__vultr__vultr_list_regions vultr.vultr_list_regions Read read
integration__vultr__vultr_list_snapshots vultr.vultr_list_snapshots Read read
integration__vultr__vultr_list_ssh_keys vultr.vultr_list_ssh_keys Read read
integration__vultr__vultr_get_current_user vultr.vultr_get_current_user Read read

Write Access

Start with --write=deny for read-only MCP clients. Use --write=ask or --write=allow only when the client and workspace are trusted.