MagicWP MCP
The MagicWP MCP server connects an AI assistant to your MagicWP workspace. Ask in plain language, and the assistant looks at your sites, takes backups, applies updates, creates staging copies, changes PHP and cache settings, fixes redirects and more, then tells you what happened.
It uses the Model Context Protocol (MCP), an open standard that AI assistants use to call tools. MagicWP runs the server for you; there is nothing to install on your side except the assistant itself.
Which plans include MCP
MCP is included with paid plans. When your workspace's plan includes it, MCP appears in the dashboard sidebar. If you don't see it, your plan doesn't include MCP.
How it works
- You create an API token for MCP in the dashboard and add it to your assistant together with the server address.
- The assistant sends every request with your token. The MCP server passes it to the MagicWP API and never stores it.
- The assistant sees only the tools your token allows. A read-only token can look but never change anything.
- Destructive actions, such as deleting a site or restoring a backup over it, need you to type the site's domain to confirm.
- Everything the assistant does is recorded in Activities, marked via MCP, with your own IP address.
Get started
Create a token
In the dashboard, open MCP and choose For MCP (full) or For MCP (read-only). Copy the token: it is shown only once.
Add MagicWP to your assistant
Server: https://mcp.magicwp.io/mcp. Each client has its own setup; see
Connect your assistant.
Ask
"Give me an overview of all my sites: anything down, failing or waiting for updates?" More ideas are in Example prompts.
In this section
Connect your assistant
The token presets, the server address, and setup for each client.
Tools
All 54 tools: what each one does and the permission it needs.
Example prompts
Real things to ask, from health checks to updates and staging.
Safety and limits
Permissions, confirmations, Magic Login, activity and rate limits.
Troubleshooting
No MCP access, token errors, IP limits and rate limits.
Supported assistants
Claude Code, Claude Desktop, Cursor, Codex and Gemini CLI. Any other client
that supports remote MCP servers over Streamable HTTP and lets you send an
Authorization header will work too.
The server signs in with an API token sent as a header. It doesn't support OAuth sign-in, so assistants that can only connect through OAuth can't use it yet.