Model Context Protocol
Hosting an AI agent can operate
Aderlo Cloud runs a hosted MCP (Model Context Protocol) server at https://aderlo.cloud/api/mcp. Add it in Claude, Claude Code, Cursor or any MCP client, sign in to the panel, choose the scopes — and the agent can browse files, change DNS, work with databases and run WP-CLI on your hosting account, with nothing to install.
What the agent can do
Permissions come in five scopes. When connecting you tick only the ones the agent needs; the server refuses any tool outside the granted scopes.
| Scope | Tools |
|---|---|
files | list, read and write files, create directories, delete to trash, search file names and text, WP-CLI commands |
dns | list DNS records, add a record |
databases | list MySQL and PostgreSQL databases, create a database, agent access, schema, SQL queries |
mail | list mailboxes |
account | list domains, account resource usage |
tools/list response.How to connect it in Claude
Add a connector
In Claude’s settings, add a custom connector and paste the server address below.
Sign in to the Aderlo Cloud panel
Claude opens a consent screen on aderlo.cloud. Sign-in asks for your second factor if you have one enabled.
Choose the service and scopes
Pick the hosting account and tick the scopes. The token goes to that client only and is listed in the panel under Integrations.
https://aderlo.cloud/api/mcp
Client without OAuth support? Generate a connection token in the panel under Integrations → Remote MCP and send it as an Authorization: Bearer header.
Example requests
- “Check whether the store domain’s SPF record is correct and add the missing TXT record.”
- “Find where the theme still loads the old chat script and remove it.”
- “Show the 10 slowest tables in the store database and suggest indexes.”
- “Update the WordPress plugins with WP-CLI and list what changed.”
Security
- The agent works only on the account you choose, and only within the granted scopes.
- Revoke access with one click under Integrations; the server checks on every call.
- Deleting a file moves it to the trash rather than erasing it; writes are verified by reading back.
- Tokens are stored only as SHA-256 hashes. Authorization codes are single-use and expire after 5 minutes.
Local version (npm)
Prefer an API key to a connector? The @aderlo/mcp package runs locally through npx. Create a key with the right scope in the panel under Integrations.
{
"mcpServers": {
"aderlo": {
"command": "npx",
"args": ["-y", "@aderlo/mcp"],
"env": {
"ADERLO_ACCOUNT": "your-hosting-login",
"ADERLO_API_KEY": "key-from-the-panel"
}
}
}
}Technical details
- Transport: Streamable HTTP, JSON-RPC 2.0,
POST https://aderlo.cloud/api/mcp. - Authorization: OAuth 2.1 (authorization code + PKCE S256, Dynamic Client Registration) or a Bearer token
aderlo_mcp_…. - Discovery: /.well-known/oauth-protected-resource (RFC 9728) and /.well-known/oauth-authorization-server (RFC 8414).
- Methods:
initialize,tools/list,tools/call,ping.