Tutorials
adminbolt team5 min read

How to Connect adminbolt MCP to Claude, Cursor, and VS Code

How to Connect adminbolt MCP to Claude, Cursor, and VS Code

adminbolt ships an MCP server, so any MCP-capable AI client can drive your hosting panel directly: list hosting accounts, create domains and email boxes, manage databases and DNS, check server health, and more, all from a chat window. MCP (the Model Context Protocol) is the open standard that lets assistants like Claude talk to external tools, and adminbolt exposes its capabilities through a single remote endpoint:

https://ai-hub.adminbolt.com/mcp

This guide walks through connecting that endpoint to the three most common clients: Claude (Desktop and the custom connector flow), Cursor, and VS Code. Authorization runs through your browser over OAuth, so there are no tokens to paste in the common case.

What you'll be able to do

Once connected, your assistant can call adminbolt tools on your behalf. Typical prompts include:

  • "List my hosting accounts."
  • "Create an email account for example.com."
  • "Add a database and a database user, then assign the user to it."
  • "Show the health of the adminbolt MCP server."
  • "Add a DNS record for this domain."

Behind the scenes these map to adminbolt's management actions for accounts, domains, email, databases, FTP, DNS, SSL, and metrics.

Before you start

You need two things:

  1. A paid Claude plan (Pro, Max, Team, or Enterprise) if you are connecting from Claude. Custom connectors are not available on the free plan. Cursor and VS Code do not have this restriction.
  2. The adminbolt MCP endpoint URL: https://ai-hub.adminbolt.com/mcp

Authorization is handled in the browser. In the Advanced settings you will see fields for "OAuth Client ID" and "OAuth Client Secret": leave those empty. After you add the connector, Claude redirects you to log in to adminbolt and approve access.

Connecting in Claude Desktop (custom connector)

Custom connectors let you add a remote MCP server straight from the Claude UI, with no config files to edit. The flow is identical on macOS and Windows; only the menu location differs.

1. Open connector settings

  • macOS: Claude → Settings (or Cmd ,), then the Connectors tab.
  • Windows: Menu / Claude → Settings (or Ctrl ,), then the Connectors tab.

2. Add a custom connector

Scroll to the Custom Connectors section and click Add custom connector (or Add custom connector → Advanced).

3. Enter the server details

  • Name: adminbolt
  • Remote MCP server URL: https://ai-hub.adminbolt.com/mcp
  • Advanced settings: leave OAuth Client ID and OAuth Client Secret empty. They are optional, and authorization goes through the browser.
  • Click Add.

4. Connect and authorize

The connector appears in the list. Click it and choose Connect. A browser window opens for OAuth: log in to adminbolt and approve access. When you return to Claude, the status changes to Connected.

5. Enable it in a conversation

In a new conversation, open the connectors icon (or Search and tools) and make sure adminbolt is checked (enabled).

6. Test it

Ask Claude something simple, like "check the health of the adminbolt MCP server" or "list my hosting accounts." A correct answer means the connector is working.

Where this configuration lives

Custom connectors are tied to your Claude account, so logging in on another device with the same account usually brings them along automatically. If you ever need to inspect or clear the local application files:

  • macOS: ~/Library/Application Support/Claude/
  • Windows: %APPDATA%\Claude\

Connecting in Cursor

adminbolt MCP is a remote HTTP server with OAuth, so in Cursor you only need to supply the URL. Authorization runs through the browser.

Config file:

  • Global (all projects): ~/.cursor/mcp.json
  • Project only: .cursor/mcp.json in the project directory
  • macOS and Windows use the same names (~ on Windows is %USERPROFILE%).

Contents:

{
  "mcpServers": {
    "adminbolt": {
      "url": "https://ai-hub.adminbolt.com/mcp"
    }
  }
}

To do it through the UI: Cursor → Settings → Tools & MCP → New MCP Server (which opens mcp.json for editing). After saving, Cursor detects the server and shows an OAuth login button. A green status means you are connected.

Connecting in VS Code (Copilot Agent mode)

This requires VS Code with MCP support enabled (GitHub Copilot, Agent mode).

Config file:

  • Project or team: .vscode/mcp.json in the project directory
  • Global: command palette (Cmd/Ctrl+Shift+P) → MCP: Open User Configuration

Note: in VS Code the key is servers (not mcpServers), and it requires a type field.

Contents:

{
  "servers": {
    "adminbolt": {
      "type": "http",
      "url": "https://ai-hub.adminbolt.com/mcp"
    }
  }
}

To do it through the UI: command palette → MCP: Add Server → choose HTTP → paste https://ai-hub.adminbolt.com/mcp → name it adminbolt. On first use, VS Code opens the browser for OAuth login.

After adding it, you can start or check the server with MCP: List Servers, or the Start button shown above the entry in mcp.json.

Why manage hosting through MCP

adminbolt was built API-first, with agent access as a first-class feature rather than an afterthought. The MCP server is the natural extension of that: instead of clicking through screens, you describe the outcome you want and the assistant calls the right management actions. It is the same philosophy behind the AI Agent Hub and WhatsApp control, and it builds on the API-first architecture that underpins the whole panel. For broader automation patterns, see Best Hosting Panel for API Automation.

Get started

Spin up a panel with a 30-day free trial at adminbolt.com, point your assistant at https://ai-hub.adminbolt.com/mcp, and start managing hosting in plain language. Full documentation is at docs.adminbolt.com, and the community on Discord and the community forum is the fastest way to get help.

← Back to Blog