Authentication

2 min readUpdated 21 October 2026

Learn how the Vultr MCP Server uses OAuth to log in with your Vultr account, ties each login to one organization, and supports remote or headless sessions.

The Vultr Model Context Protocol (MCP) Server uses Open Authorization (OAuth) to log in with your Vultr account. There is nothing to create, copy, or rotate. The server keeps no credentials of its own, and every call to api.vultr.com runs under your own account, not a shared one.

Access renews every hour on its own.
You log in again only after 30 days without use, or if access is revoked.
Most MCP clients support this login, including Claude, Cursor, VS Code, Codex CLI, and OpenClaw.

Note

The Vultr MCP Server is in public preview. The tool surface and endpoint structure may change at general availability, so forward compatibility is not guaranteed.

Log In

Add the server URL to your MCP client without any credentials. The client opens a browser window where you log in to Vultr and approve access. For more information, see Client Setup.

Each login is tied to one Vultr organization, which is the organization that is selected in the Vultr Console when you click Authorize. To change organizations, switch organizations in the Vultr Console first, then log in again. Ask What Vultr account am I connected as? to verify where you logged in.

To work with two organizations at once, add the server twice under different names and log in to each separately.

Connect from a Remote or Headless Session

If your MCP client runs over SSH, in a container, or anywhere else without a local browser, the client cannot open a login window. Use one of the following methods, depending on your client:

Device authorization: The client shows a short code and a URL. Open the URL in a browser on any device, enter the code, and approve access. The client detects the approval and finishes the login automatically.
Authorization code: In some clients, the browser shows an error page that contains an authorization code instead of finishing the login. Copy the code and pass it to the client. For example, with OpenClaw, run openclaw mcp login vultr --code AUTHORIZATION-CODE.

Permissions

The MCP server acts with the permissions of the logged-in user. Vultr enforces what that user is allowed to do, so the server cannot see anything that the user cannot see. An organization administrator controls whether MCP is available and who can use it. For more information, see Admin Controls.

0 Comments

Start the conversation

Be the first to comment and share your perspective with the community.

One Organization per Login

To work with two organizations at once, add the server twice under different names and log in to each separately.

Connect from a Remote or Headless Session

If your MCP client runs over SSH, in a container, or anywhere else without a local browser, the client cannot open a login window. Use one of the following methods, depending on your client:

Device authorization: The client shows a short code and a URL. Open the URL in a browser on any device, enter the code, and approve access. The client detects the approval and finishes the login automatically.

Authorization code: In some clients, the browser shows an error page that contains an authorization code instead of finishing the login. Copy the code and pass it to the client. For example, with OpenClaw, run openclaw mcp login vultr --code AUTHORIZATION-CODE.