Read RunCloud servers, web apps, databases and logs; deploy, restart services, renew SSL. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"runcloud": {
"url": "https://runcloud.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"runcloud": {
"type": "http",
"url": "https://runcloud.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your RunCloud API key.
Create it in RunCloud under Workspace → Settings → API Management (the API is available on the Business and Enterprise plans). Leave the key's IP restriction empty: requests come from Cloudflare addresses, so a key limited to your own IP would be refused. The key has the access of your workspace; revoke it there at any time. Your key is used only to call the RunCloud API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your RunCloud API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
runcloud_ping | read | Check API connection Check that the API key works: RunCloud answers with a message ('pong'). GET /ping. |
runcloud_list_servers | read | List servers List the servers connected to the workspace: id, name, provider, IP address, OS, stack, online/connected state, agent and PHP CLI version, auto-update settings and tags. GET /servers. |
runcloud_get_server | read | Get server One server by id: provider, IP, OS and version, stack, online state, agent version, update settings, tags. GET /servers/{id}. |
runcloud_get_server_stats | read | Get server counts How many web applications, databases, cron jobs and supervisor jobs a server has, and its country. GET /servers/{id}/stats. |
runcloud_get_server_hardware | read | Get server hardware info Kernel version, CPU model and cores, memory and disk totals/free, load average and uptime of a server. GET /servers/{id}/hardwareinfo. |
runcloud_get_server_health | read | Get latest server health The latest health sample of a server: total/available/used memory and disk space (MB) and load average. GET /servers/{id}/health/latest. |
runcloud_list_server_logs | read | List server activity logs The server's activity log (what was changed in RunCloud and when), newest first. GET /servers/{id}/logs. |
runcloud_list_services | read | List server services The services on a server (nginx, php-fpm, mariadb, redis, supervisor...) with real name, running state, CPU, memory and version. The realName is what runcloud_control_service needs. GET /servers/{id}/services. |
runcloud_list_system_users | read | List system users The system (Linux) users on a server: id, username, whether deletable. Deployment keys and passwords are never returned. GET /servers/{id}/users. |
runcloud_list_webapps | read | List web applications List the web applications on a server: id, name, root/public path, PHP version, stack, type (wordpress, custom...), default flag, alias. Deployment webhook keys are not returned. GET /servers/{id}/webapps. |
runcloud_get_webapp | read | Get web application One web application by id (path, PHP version, stack, type, default flag). GET /servers/{id}/webapps/{webapp}. |
runcloud_get_webapp_settings | read | Get web application settings PHP and FPM/Nginx settings of a web application (disabled functions, timezone, memory and upload limits, process manager...). GET /servers/{id}/webapps/{webapp}/settings. |
runcloud_list_webapp_logs | read | List web application activity logs The activity log of a web application (settings changes, PHP version changes, deployments), newest first. GET /servers/{id}/webapps/{webapp}/log. |
runcloud_list_domains | read | List domain names The domain names of a web application: id, name, type (primary/alias), www, redirection, wildcard, DNS integration, status. GET /servers/{id}/webapps/{webapp}/domains. |
runcloud_get_domain_dns | read | Get domain DNS setup instructions The DNS records (A, CNAME...) a domain name needs to point at the server. GET /servers/{id}/webapps/{webapp}/domains/{domain}/dns. |
runcloud_get_webapp_ssl | read | Get web application SSL The web application's SSL certificate (basic / web-app-level SSL): provider, validity, HTTPS settings. Private keys are never returned. GET /servers/{id}/webapps/{webapp}/ssl. |
runcloud_get_ssl_method | read | Check SSL method and AutoSSL status Whether the web application uses basic (one certificate for the app) or advanced (one per domain) SSL, and its AutoSSL status. Advanced SSL is a Business/Enterprise feature. GET /servers/{id}/webapps/{webapp}/ssl/advanced. |
runcloud_get_git_deployment | read | Get Git deployment The Git deployment configured on a web application: provider, branch, repository URL, auto-deploy flag, deployment script and whether it is an atomic deployment. The deployment webhook keys are not returned. The id of the result is the git_id for runcloud_deploy_git. GET /servers/{id}/webapps/{webapp}/git. |
runcloud_list_databases | read | List databases The databases on a server: id, name, collation. No credentials. GET /servers/{id}/databases. |
runcloud_list_database_users | read | List database users The database users on a server (id, username). Passwords are never returned. GET /servers/{id}/databaseusers. |
runcloud_list_cronjobs | read | List cron jobs The cron jobs of a server: id, label, user, schedule, command, enabled flag. The id is what runcloud_run_cronjob needs. GET /servers/{id}/cronjobs. |
runcloud_list_supervisors | read | List supervisor jobs The supervisor (background worker) jobs of a server: id, label, user, process count, auto start/restart, directory, command. GET /servers/{id}/supervisors. |
runcloud_get_supervisor_status | read | Get supervisor job status The live status (RUNNING, FATAL, BACKOFF...), pid and uptime of every supervisor process, by job label. GET /servers/{id}/supervisors/status. |
runcloud_list_firewall_rules | read | List firewall rules The firewall rules of a server: type (global/rich), port, protocol, IP address, action. GET /servers/{id}/security/firewalls. |
runcloud_list_blocked_ips | read | List Fail2Ban blocked IPs The IP addresses Fail2Ban currently blocks on a server. GET /servers/{id}/security/fail2ban/blockedip. |
runcloud_list_backups | read | List backups The backup instances of the workspace: label, what they cover (web app / database), storage, type, frequency, size, status. Filter by server, storage, status or name. GET /backups. |
runcloud_list_backup_snapshots | read | List backup snapshots The snapshots of one backup instance: run date, status, type and size. GET /backups/{id}/snapshots. |
runcloud_list_atomic_projects | read | List atomic deployment projects The atomic Git deployment projects of the workspace: name, provider, repository, branch, auto-deploy, success/failure counts and the latest deployment. Webhook keys are not returned. GET /atomic. |
runcloud_list_atomic_deployments | read | List atomic deployments The deployments of an atomic project: commit hash, branch, message, committer, release name, status (DEPLOYING, COMPLETED, FAILED), start and end time. GET /atomic/{project}/deployments. |
runcloud_control_service | write | Start, restart or reload a service WRITE: run systemctl start, restart or reload on one service of a server (for example nginx-rc or php81rc-fpm). A restart briefly interrupts that service and the sites behind it. 'stop' is deliberately not offered. Get the realName from runcloud_list_services. PATCH /servers/{id}/services. |
runcloud_deploy_git | write | Force a Git deployment WRITE: force a Git deployment of a web application now: RunCloud pulls the configured branch and runs the deployment script, which changes the live site's files. Get git_id from runcloud_get_git_deployment (its id). PUT /servers/{id}/webapps/{webapp}/git/{git}/script. |
runcloud_force_deploy_atomic | write | Force an atomic deployment WRITE: start an atomic deployment of a project now (builds a new release and switches the live symlink when it succeeds). PUT /atomic/{project}/forcedeploy. |
runcloud_run_cronjob | write | Run a cron job now WRITE: force-run one cron job of a server once, right now, outside its schedule. The job's command runs on the server with its configured user. Get the id from runcloud_list_cronjobs. POST /servers/{id}/cronjobs/{job}/run. |
runcloud_reload_supervisor | write | Reload a supervisor job WRITE: reload one supervisor job so its worker processes restart (running processes are interrupted). Get the id from runcloud_list_supervisors. POST /servers/{id}/supervisors/{job}/reload. |
runcloud_renew_ssl | write | Renew a Let's Encrypt certificate WRITE: redeploy (renew) the Let's Encrypt certificate of a web application, which re-issues it and reloads the web server. Let's Encrypt certificates only. For basic SSL pass the ssl_id from runcloud_get_webapp_ssl; for advanced (per-domain) SSL, which requires advanced SSL mode (check runcloud_get_ssl_method), also pass domain_id. PUT /servers/{id}/webapps/{webapp}/ssl/{ssl} or /domains/{domain}/ssl/{ssl}. |
runcloud_install_letsencrypt_ssl | write | Issue a Let's Encrypt certificate WRITE: issue and install a free Let's Encrypt certificate for a web application (basic SSL) or for one domain of it (advanced SSL, pass domain_id; this requires advanced SSL mode, see runcloud_get_ssl_method). The web server is reloaded; the domain's DNS must already point at the server. Custom certificates are not supported here. POST /servers/{id}/webapps/{webapp}/ssl or /domains/{domain}/ssl. |
runcloud_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
runcloud_request_feature | Request a missing feature Tell usefulapi that the user needs something the RunCloud tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
runcloud_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED RunCloud tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
runcloud_cancel_subscription | Cancel the Pro subscription Cancel the caller's RunCloud Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run runcloud_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this RunCloud server only. Subscribe with runcloud_upgrade (it returns a Stripe Checkout link). Cancel any time with runcloud_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running runcloud_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by RunCloud. The server calls the RunCloud API with your own RunCloud access, so it sees only the data that your account can see.
The login page asks for your RunCloud API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your RunCloud API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the RunCloud API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in RunCloud.
Yes, if you approve it. 7 of the 36 RunCloud tools can create or change data. The other 29 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this RunCloud server only. Run runcloud_usage_status to see how many calls you used.
Ask the AI to run runcloud_upgrade: it returns a Stripe Checkout link. To cancel, run runcloud_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with runcloud_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.