- Home
- MCP servers
- SpinupWP
SpinupWP
- typescript
0
GitHub Stars
typescript
Language
3 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"farukgaric-spinupwp-mcp": {
"command": "node",
"args": [
"/absolute/path/to/spinupwp-mcp/build/index.js"
],
"env": {
"SPINUPWP_API_TOKEN": "YOUR_API_TOKEN"
}
}
}
}You can manage and observe your SpinupWP infrastructure through a dedicated MCP (Model Context Protocol) server. This enables AI assistants to interact with SpinupWP resources—such as servers, sites, and deployments—directly via MCP clients, making automation and control seamless.
How to use
You run the MCP server locally and connect an MCP client to it over standard input/output. Use a local client to issue commands that list servers, manage sites, restart services, trigger deployments, and handle SSH keys. The server exposes a set of tools that you call through the MCP interface to perform common SpinupWP tasks without switching to a web console.
How to install
Prerequisites you need before running the MCP server:
- Node.js v18 or newer is recommended
- A SpinupWP API Token is required to authenticate with the SpinupWP API
Step-by-step setup commands:
# 1. Clone the MCP server repository
git clone https://github.com/farukgaric/spinupwp-mcp.git
cd spinupwp-mcp
# 2. Install dependencies
npm install
# 3. Build the TypeScript files
npm run build
# 4. Configure environment
cp .env.example .env
Next steps after setup
Create the environment file with your actual API token and start the server. The MCP server runs as a local process and is designed to be consumed by an MCP client over stdio.
# Edit your environment file to include your SpinupWP API token
# Example content in .env:
SPINUPWP_API_TOKEN=your_actual_token_here
# Start the server (loading the .env file)
npm start
Additional setup for MCP clients
To connect an MCP client, provide a configuration that points to the local node process and the built MCP entry point. The example below shows how to configure Claude Desktop to interact with the local MCP server.
{
"mcpServers": {
"spinupwp-local": {
"command": "node",
"args": [
"/absolute/path/to/spinupwp-mcp/build/index.js"
]
}
}
}
Available tools
list_servers
List all SpinupWP servers and their hardware and update status.
get_server
Retrieve detailed information for a specific server.
reboot_server
Reboot a specific SpinupWP server.
restart_service
Restart a specific service (nginx, php, mysql, redis) on a server.
list_sites
List all WordPress sites hosted on a specific server.
get_site
Retrieve detailed information for a specific WordPress site.
purge_site_cache
Purge the page cache for a specific WordPress site.
run_site_git_deployment
Trigger a Git deployment for a specific site.
correct_site_file_permissions
Correct the file permissions for a site.
list_events
List recent SpinupWP events (async background tasks).
get_event
Get the details and status of a single event ID.
list_ssh_keys
List the SSH keys configured in the SpinupWP account.
add_ssh_key
Add a new SSH public key for server access.
create_site
Provision a brand new WordPress site on a server.
delete_site
Delete an existing site.
create_server
Provision a brand new custom server.
delete_server
Delete a server entirely.