Read SpinupWP servers, sites and events; purge caches, restart services, run git deploys. 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": {
"spinupwp": {
"url": "https://spinupwp.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"spinupwp": {
"type": "http",
"url": "https://spinupwp.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 SpinupWP API token.
Create a token in SpinupWP under My Account → API Tokens (or Team Settings → API Tokens for team owners and admins) at spinupwp.app. The API needs an active SpinupWP plan. This connection cannot create or delete servers or sites. Your token is used only to call the SpinupWP 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 SpinupWP API token. 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 |
|---|---|---|
spinupwp_list_servers | read | List servers List the servers in your SpinupWP team: name, provider, region, size, IP, Ubuntu version, disk space, connection status and whether a reboot or upgrade is required. GET /servers. |
spinupwp_get_server | read | Get server One server by id: provider, size, disk usage, database server, connection status, reboot/upgrade-required flags and install notes. GET /servers/{id}. |
spinupwp_list_sites | read | List sites List sites across your servers (or one server): domain, PHP version, WordPress flag, HTTPS, page cache, backups, pending WordPress core/theme/plugin updates, git deploy settings and status. Deploy-trigger URLs are hidden. GET /sites. |
spinupwp_get_site | read | Get site One site by id with its full settings: domains, PHP version, page cache, HTTPS, nginx options, database reference, backup schedule and storage, WordPress update counts, git repo/branch/deploy script, basic-auth username, cron and SpinupWP subdomain. The git deploy-trigger URL is hidden. GET /sites/{id}. |
spinupwp_list_site_domains | read | List site domains The additional domains of a site, with their redirect settings (enabled, type, destination). GET /sites/{id}/domains. |
spinupwp_list_site_path_redirects | read | List site path redirects The path redirects configured on a site (from, to, type permanent/redirect). GET /sites/{id}/path-redirects. |
spinupwp_list_events | read | List events List recent events (the activity log: provisioning, restarts, deploys, cache purges) with who started them, status (queued, creating, updating, deleting, deployed, failed) and timestamps. Long command output is shortened; read one event for its full output. GET /events. |
spinupwp_get_event | read | Get event One event by id, with status and command output. Use it to see whether a purge, restart or deploy (which reply with an event_id) has finished or failed. GET /events/{id}. |
spinupwp_list_storage_providers | read | List backup storage providers The backup storage providers connected to the team (id, service, name). GET /storage-providers. |
spinupwp_list_team_ssh_keys | read | List team SSH keys The team's saved SSH public keys (id, name, fingerprint, public key). Public keys only; read-only. GET /ssh-keys. |
spinupwp_purge_page_cache | write | Purge page cache WRITE: purge the nginx page cache of one site. Pages are rebuilt on the next visit, so the site may be slower for a moment; nothing is lost. Asynchronous: returns an event_id. POST /sites/{id}/page-cache/purge. |
spinupwp_purge_object_cache | write | Purge object cache WRITE: flush the Redis object cache of one site (the site must have object caching). The cache refills on demand. Asynchronous: returns an event_id. POST /sites/{id}/object-cache/purge. |
spinupwp_correct_file_permissions | write | Correct file permissions WRITE: reset a site's files and folders to the permissions and ownership SpinupWP recommends (usually after a manual upload as the wrong user). Can take a while on big sites. Asynchronous: returns an event_id. POST /sites/{id}/file-permissions/correct. |
spinupwp_deploy_site_git | write | Run site git deploy WRITE: pull the latest commit of the site's connected git branch and run its deploy script on the server. This changes the live site's files (and may run build/migration commands); it fails if git is not connected. Asynchronous: returns an event_id. POST /sites/{id}/git/deploy. |
spinupwp_restart_nginx | write | Restart nginx WRITE: restart nginx (web server) on one server. Visitors may see a brief interruption. Asynchronous: returns an event_id. POST /servers/{id}/services/nginx/restart. |
spinupwp_restart_php | write | Restart php WRITE: restart PHP-FPM (every PHP version) on one server. Running PHP requests can fail or be cut off while it restarts. Asynchronous: returns an event_id. POST /servers/{id}/services/php/restart. |
spinupwp_restart_mysql | write | Restart mysql WRITE: restart MySQL (database) on one server. All sites on the server lose database access for a short time; running queries are interrupted. Asynchronous: returns an event_id. POST /servers/{id}/services/mysql/restart. |
spinupwp_restart_redis | write | Restart redis WRITE: restart Redis (object cache) on one server. Cached objects are lost and rebuilt on demand. Asynchronous: returns an event_id. POST /servers/{id}/services/redis/restart. |
spinupwp_reboot_server | write | Reboot server WRITE: reboot a whole server. Every site on it is offline for the duration (typically a minute or two). Use it when spinupwp_get_server shows reboot_required. Asynchronous: returns an event_id. POST /servers/{id}/reboot. |
spinupwp_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. | |
spinupwp_request_feature | Request a missing feature Tell usefulapi that the user needs something the SpinupWP 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. | |
spinupwp_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED SpinupWP 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. | |
spinupwp_cancel_subscription | Cancel the Pro subscription Cancel the caller's SpinupWP 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 spinupwp_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 SpinupWP server only. Subscribe with spinupwp_upgrade (it returns a Stripe Checkout link). Cancel any time with spinupwp_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running spinupwp_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 SpinupWP. The server calls the SpinupWP API with your own SpinupWP access, so it sees only the data that your account can see.
The login page asks for your SpinupWP API token. 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 SpinupWP API token. 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 SpinupWP 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 SpinupWP.
Yes, if you approve it. 9 of the 19 SpinupWP tools can create or change data. The other 10 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 SpinupWP server only. Run spinupwp_usage_status to see how many calls you used.
Ask the AI to run spinupwp_upgrade: it returns a Stripe Checkout link. To cancel, run spinupwp_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 spinupwp_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.