SpinupWP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPINUPWP_API_TOKEN | Yes | Your SpinupWP API token. You can generate this from the 'API Tokens' tab in your SpinupWP account settings. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_serversB | List all SpinupWP servers and their hardware/update status |
| list_sitesC | List all WordPress sites on a specific SpinupWP server |
| get_serverC | Get details for a specific SpinupWP server |
| reboot_serverC | Reboot a specific SpinupWP server |
| restart_serviceC | Restart a specific service (nginx, php, mysql, redis) on a SpinupWP server |
| get_siteC | Get details for a specific WordPress site |
| purge_site_cacheC | Purge the page cache for a specific WordPress site |
| run_site_git_deploymentC | Run a git deployment for a specific WordPress site |
| correct_site_file_permissionsC | Correct the file permissions for a specific WordPress site |
| list_eventsB | List recent SpinupWP events (optionally filtered by server_id or site_id) |
| get_eventC | Get details and status of a specific SpinupWP event |
| list_ssh_keysB | List SSH keys configured in SpinupWP |
| add_ssh_keyC | Add a new SSH public key to SpinupWP |
| create_siteC | Create a new WordPress site on a server |
| delete_siteC | Delete a specific WordPress site |
| delete_serverC | Delete a specific SpinupWP server |
| create_serverC | Provision a new custom SpinupWP server (MVP using existing infrastructure) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the SpinupWP/WordPress domain. There is no ambiguity between tools like create_server vs. create_site, or list_servers vs. list_sites, as they operate on different entities with clear boundaries.
All tools follow a consistent verb_noun naming pattern (e.g., add_ssh_key, create_server, list_events). The verbs are appropriate and predictable across the set, with no mixing of conventions or styles, making the tool names highly readable and systematic.
With 17 tools, the server is well-scoped for managing SpinupWP servers and WordPress sites, covering provisioning, management, monitoring, and maintenance. Each tool earns its place by addressing specific needs in this domain without being excessive or too sparse.
The tool set provides complete CRUD/lifecycle coverage for servers and sites (create, get, list, delete), along with essential operations like SSH key management, event tracking, cache purging, rebooting, service restarting, and deployments. There are no obvious gaps that would hinder agent workflows in this domain.