Client Setup

The Vultr Model Context Protocol (MCP) Server works with any client that supports remote MCP over Streamable HTTP. Every example in this guide uses the full endpoint, https://mcp.vultr.com/mcp. To load fewer tools, replace the URL with one of the endpoints in Tools.

Follow this guide to connect a supported MCP client to the Vultr MCP Server.

Prerequisites

Before you begin, ensure that:

• An organization administrator has enabled the MCP Server for your organization.
• An administrator has attached the Use MCP permission policy to your user, group, or role.
• The client that you want to connect is installed.

Supported Clients

Select your client from the following list:

• Claude.ai and Claude Desktop
• Claude Code
• Cursor
• VS Code
• Codex CLI
• OpenClaw
• opencode
• Hermes Agent
• Other Clients

Claude.ai and Claude Desktop

Add the Vultr MCP Server as a custom connector, and then log in.

1. Open Settings and click Connectors.
2. Click Add then Add custom connector.
3. Enter Vultr as the name and https://mcp.vultr.com/mcp as the URL.
4. Click Add.
5. Click Connect, log in to Vultr, and approve access.

A connector that you add once works in both Claude Desktop and Claude.ai. On Team and Enterprise plans, an Owner adds the connector first under Organization settings and Connectors, and then each person connects from their own Settings. Claude Desktop and Claude.ai log in with OAuth only.

Claude Code

Add the server with the claude mcp add command, and then log in from Claude Code.

1. Add the server.

   CONSOLE

   Copy

   $ claude mcp add --transport http vultr https://mcp.vultr.com/mcp

   Explain Code

   Powered by Vultr AgentBeta

   Add --scope user to make the server available in every folder instead of only the current one.

2. Run /mcp in Claude Code, select vultr, and log in.

Cursor

Add the server to the Cursor MCP configuration, and then log in.

1. Open Settings, click Tools & MCP, and click Add custom MCP.

2. Add the following entry to mcp.json.

   JSON

   Copy

   {
     "mcpServers": {
       "vultr": {
         "type": "http",
         "url": "https://mcp.vultr.com/mcp"
       }
     }
   }

   Explain Code

   Powered by Vultr AgentBeta

3. Save the file and click Needs login to log in.

VS Code

Add the server to the VS Code MCP configuration, and then log in.

1. Add the following entry to .vscode/mcp.json. Alternatively, open the MCP Servers panel, click +, and add an HTTP server.

   JSON

   Copy

   {
     "servers": {
       "vultr": {
         "type": "http",
         "url": "https://mcp.vultr.com/mcp"
       }
     }
   }

   Explain Code

   Powered by Vultr AgentBeta

2. Log in when VS Code prompts you.

Codex CLI

Add the server with the Codex CLI, and then log in.

1. Add the server.

   CONSOLE

   Copy

   $ codex mcp add vultr --url https://mcp.vultr.com/mcp

   Explain Code

   Powered by Vultr AgentBeta

2. Log in.

   CONSOLE

   Copy

   $ codex mcp login vultr

   Explain Code

   Powered by Vultr AgentBeta

OpenClaw

Add the server with the OpenClaw CLI, and then log in.

1. Add the server.

   CONSOLE

   Copy

   $ openclaw mcp add vultr --url https://mcp.vultr.com/mcp --transport streamable-http --auth oauth

   Explain Code

   Powered by Vultr AgentBeta

2. Log in.

   CONSOLE

   Copy

   $ openclaw mcp login vultr

   Explain Code

   Powered by Vultr AgentBeta

On a remote machine, the browser may show an error page with an authorization code instead of finishing the login. Copy the code and run the following command. Replace AUTHORIZATION-CODE with the code.

$ openclaw mcp login vultr --code AUTHORIZATION-CODE

opencode

Add the following entry to opencode.json. opencode starts the login on its own.

{
  "mcp": {
    "vultr": {
      "type": "remote",
      "url": "https://mcp.vultr.com/mcp",
      "enabled": true
    }
  }
}

Hermes Agent

Add the following entry to ~/.hermes/config.yaml.

mcp_servers:
  vultr:
    url: "https://mcp.vultr.com/mcp"
    auth: oauth

Other Clients

Any client that supports remote MCP over Streamable HTTP works. Provide the URL, leave the credentials empty, and the client logs in with OAuth.

Clients that can only launch local servers can connect through mcp-remote, which logs in with OAuth.

$ npx -y mcp-remote https://mcp.vultr.com/mcp

On a network that inspects TLS traffic, point Node.js at your company's certificate authority with the NODE_EXTRA_CA_CERTS environment variable instead of turning off certificate checks. Replace PATH-TO-CA-FILE with the path to the certificate file.

$ export NODE_EXTRA_CA_CERTS=PATH-TO-CA-FILE

Verify the Connection

After you log in with any client, ask the client what account it is connected to.

1. Ask the client What Vultr account am I connected as?

   Verify that the response shows the account and organization that you expect.

The client is now connected to the Vultr MCP Server. For more information, see Example Prompts and Troubleshooting. For the most current client instructions, see the Vultr MCP Server repository on GitHub.