Broodle's MCP server connects Claude, Cursor, ChatGPT, Claude Code, VS Code, OpenCode, Kiro, and any MCP-compatible AI to your App Containers, cPanel hosting, VPS servers, domains, and account — all through one URL and one token.
From editing a single file to running full WordPress, Node.js, Python, and Docker workflows — grant exactly the capabilities you want, nothing more.
Browse, read, write, search, and organize files anywhere you’ve granted access — from a single config file to a full project tree.
Query and manage MySQL, PostgreSQL, or MariaDB databases directly — inspect data, run migrations, or fix a bad row on the spot.
Full WordPress control by chat — plugins, themes, updates, and security, without logging into wp-admin.
Run and manage Node.js apps end to end — install dependencies, manage processes, and configure the reverse proxy.
Manage Python environments and apps — virtualenvs, pip packages, WSGI/ASGI processes, and everything in between.
Run shell commands inside your App Container, manage its lifecycle, and keep it backed up — all through natural language.
SSH-level control over your VPS or VM — commands, processes, services, and power state, scoped to your own server.
Registrar and DNS control for any domain you grant — nameservers, records, locking, and live Cloudflare management.
Full mailbox control by chat — create accounts, then read, search, send, and manage inbox content directly, with granular per-mailbox permissions.
Read and respond to customer conversations across WhatsApp, Instagram, email, and live chat via Engage.
Account-wide tools gated by permission — tickets, invoices, team management, and service upgrades.
Every token can browse the catalog, check domain availability, and manage your cart — for your own account, automatically, regardless of what else you granted.
Pick your client below, copy the config, swap in your token from the console, and you're connected.
Open Settings → Developer → Edit Config, paste this in, then restart Claude Desktop.
{
"mcpServers": {
"broodle": {
"type": "http",
"url": "https://broodle.host/api/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN_HERE" }
}
}
}Replace YOUR_TOKEN_HERE with a token from Console → Tools → MCP Server.
Every token is scoped, logged, and revocable. Nothing runs on your account beyond what you explicitly allowed.
A token only works on the exact services, domains, and account permissions you selected when creating it — never your whole account by default.
Every tool is tagged read, write, or danger. Mint a read-only token for an assistant that should only look, and reserve full access for the agents you fully trust.
Restrict a token to specific IP addresses or CIDR ranges so it only works from where you expect — off by default, one toggle to turn on.
Every tool call is logged — which tool, which token, from which IP, whether it succeeded — visible right in your console with filters and search.
Tokens expire automatically (1 day up to 90 days, your choice) and can be revoked instantly at any time — no residual access left behind.
Passwords, API keys, and other sensitive values are automatically redacted before anything is logged — even in the detailed call history.
Go to Console → Tools → MCP Server and create a token. Pick exactly which services, domains, and account permissions it can touch, and how far it can go — read-only, read & write, or full access including deletes and orders.
Paste one URL and your token into Claude, Cursor, VS Code, Claude Code, OpenCode, Kiro, or any MCP-compatible client. One connection covers every hosting type, domain, and account capability you granted — no separate integration per service.
Tell your AI agent what you want in plain English — "restart my app container", "check why my WordPress site is slow", "add an MX record for mail.example.com", "open a support ticket about my invoice". It calls the right tool automatically.
Everything you need to know about connecting AI agents to your Broodle hosting via MCP.
MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude, ChatGPT, and coding agents call real tools — not just chat. Broodle’s MCP server exposes your hosting, domains, and account as a set of tools any MCP-compatible AI client can use, so you can manage your infrastructure by asking your favorite AI assistant instead of clicking through a dashboard.
Any client that supports the MCP standard over HTTP: Claude Desktop, Claude Code, Cursor, VS Code, OpenCode, Kiro CLI, and ChatGPT (via custom connectors on supporting plans), among others. It’s one standard connection — if your AI tool speaks MCP, it works with Broodle.
No. Broodle runs a single, unified MCP server at one URL. One token can be granted access to any mix of App Container apps, cPanel hosting, VPS/LXC servers, Engage helpdesk accounts, domains, and account-level permissions — all through the same connection.
You stay in control of exactly what a token can do. Every tool is scoped to read, write, or danger, grants are per-service and per-domain (never blanket account access unless you choose that), tokens expire automatically, and every single call is logged with full detail. Start with a read-only token for anything you’re unsure about.
Practically anything you could do yourself in the console or cPanel — restart an app, read and fix a config file, add a DNS record, install a WordPress plugin, check disk usage, open a support ticket, reply to a customer on WhatsApp via Engage, or even place a real order. It calls the exact same tools our own console and AI Studio use internally.
Yes. Every token supports an optional IP allowlist — add specific IPs or CIDR ranges and the token will only be accepted from those addresses. It’s off by default so tokens work from anywhere, and you can turn it on (or edit the list) at any time from the token’s settings.
The MCP server itself is free — it’s included with every Broodle hosting service, domain, and account. You only pay for the underlying hosting, domains, or orders your AI agent might place on your behalf, exactly as if you’d done it yourself through the console.
Yes — every tool call is recorded in your account’s usage history: which tool ran, on which service, from which token and IP address, whether it succeeded, and (for troubleshooting) the actual call arguments with secrets automatically redacted. Filter by tool, status, or token right from the console.
Generate a token, add one URL to your AI client, and start managing your hosting by chat — no extra cost, no separate integrations.
