A self-contained PHP application you install anywhere PHP runs — shared hosting, a VPS, or Docker. Same admin, same tools, same MCP endpoints as the WordPress build, because it is the same codebase.
The installer checks the server can run GetMCP, downloads the build, verifies it, and hands you the setup screen. Everything after that happens in the browser.
Then finish in the browser: database, administrator, done. Already run WordPress? Install it there instead.
# On any host with PHP 8.3 or newer curl -fsSL https://get.getmcp.com | bash
# In PowerShell irm https://get.getmcp.com/install.ps1 | iex
The steps that usually make self-hosting a PHP app tedious are the ones it handles.
PHP version and the extensions that matter — including sodium, which encrypts stored API credentials and is not optional. If something is missing it names it before touching anything.
Checksum-verified, unpacked with the right permissions, .env written with a key generated for your install. Composer and Node are never needed — the archive ships ready to run.
Your database — SQLite needs no configuration at all — and your administrator account. The installer closes itself permanently once it finishes.
A single entry drives log retention, daily analytics, audit verification and licence checks. Everything else is the dashboard.
Your data never leaves the server. Tool calls go from the MCP client, through your install, to your API — we never see them.
Not a cut-down edition. The differences are only the ones the host forces.
| Standalone app | WordPress plugin | |
|---|---|---|
| Tools, resources, prompts | ✓ | ✓ |
| Chat Playground | ✓ | ✓ |
| OAuth 2.1, API keys, PII redaction | ✓ | ✓ |
| Analytics and call logs | ✓ | ✓ |
| Install & updates | Its own installer | Like any plugin |
| Logins & cron | Built in | WordPress’s |
| Read WordPress posts as a resource | — | ✓ |
| Server logo from the media library | — | ✓ |
Move between them whenever you like — a server exports to a single file that recreates it, with its tools, resources, prompts and settings, on the other build.
No. It installs on hosting you already have, on a subdomain like mcp.yoursite.com. It is a normal PHP application — if your host can run WordPress, it can run this.
No. The same licence covers the standalone app and the WordPress plugin, and moving from one to the other does not need a new one.
Updates arrive through the same licence, and the release archive replaces the application files while leaving your .env, database and storage alone. Back both up before you update — they are not useful separately.
Yes. Each install is independent, and one install can host as many MCP servers as your plan allows. Agencies typically run one per client.
Run the installer again — a half-finished attempt is resumable. If it still stops, the message stays on screen and storage/logs/laravel.log in the install directory will say why.