A self-hosted MCP server on your own server. No WordPress required.
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.
Install in under a minute.
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
Nothing left for you to wire up
The steps that usually make self-hosting a PHP app tedious are the ones the installer handles.
-
Checks
Confirms the server can run it
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.
✓ PHP 8.3 or newer ✓ sodium ✓ pdo ✓ curl ✓ mbstring ✓ json ✓ openssl
-
Installs
Downloads and verifies the build
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.
✓ checksum verified ✓ unpacked, permissions set ✓ .env written, key generated
-
Sets up
Two screens in the browser
Your database, where SQLite needs no configuration at all, and your administrator account. The installer closes itself permanently once it finishes.
database SQLite, nothing to configure admin your account # installer removes itself when done
-
Runs
One cron line and it is yours
A single entry drives log retention, daily analytics, audit verification and licence checks. Everything else is the dashboard.
# one cron entry, every minute retention analytics audit licence
If it runs PHP, it runs GetMCP
The requirements are modest on purpose. If your host can run WordPress, it can run this.
What it needs
- PHP 8.3+ with sodium, pdo, curl, mbstring, json and openssl
- SQLite (nothing to configure), MySQL 8 or MariaDB 10.4+, or PostgreSQL 13+
- One cron entry, running every minute
- A web root pointed at the app’s public/ folder
Where it runs
- Shared hosting and cPanel; the installer arranges the public_html split for you
- A VPS or dedicated box
- Docker
- Windows, via PowerShell
Your data never leaves the server. Tool calls go from the MCP client, through your install, to your API. We never see them.
The same application, either way
Not a cut-down edition. The differences are only the ones the host forces.
The dashboard you get on both builds
Servers, tools, resources, prompts, the chat playground, analytics and call logs: the standalone app and the WordPress plugin share one admin, built from one codebase.
- One licence covers both builds
- A server exports to a single file that recreates it on the other build
- Updates arrive the same way on both
| Standalone app | WordPress plugin | |
|---|---|---|
| Tools, resources, prompts | ✓ | ✓ |
| Chat playground | ✓ | ✓ |
| OAuth 2.1, API keys, PII redaction | ✓ | ✓ |
| Analytics and call logs | ✓ | ✓ |
| Install and updates | Its own installer | Like any plugin |
| Logins and 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.
Before you install
Do I need a separate server for this?
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.
Is my licence tied to one of the two builds?
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.
What happens when there is an update?
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.
Can I run more than one?
Yes. Each install is independent, and one install can host as many MCP servers as your plan allows. Agencies typically run one per client.
Something failed during setup. Now what?
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.
Put an MCP server on your own box tonight.
One command, two screens, and your API is something Claude can call.