Skip to main content
GetMCP ships a wp getmcp command tree for WP-CLI, the official WordPress command-line interface. Use it to manage servers, list and test tools, mint API keys, and run a self-diagnostic — all without opening the admin UI. It’s the right tool when you want to:
  • Provision servers from a deploy script or wp-config bootstrap
  • Run a quick health check from CI before/after a release
  • Pipe server or tool data into another tool (--format=json plays nicely with jq)
  • Test a tool against a real upstream API without spinning up an MCP client

Prerequisites

  • WP-CLI 2.5+ installed on the server. Check with wp --info. If WP-CLI isn’t installed, follow the official install guide.
  • GetMCP plugin active on the WordPress install you’re running commands against.
  • Permission-wise, wp runs as the user that owns the WordPress install — there’s no separate auth.

Command Tree

Run wp help getmcp <subcommand> for full options on any command (replace <subcommand> with the actual command name, e.g. wp help getmcp servers create).

Common Tasks

List your servers

Get one server’s full configuration

The argument can be the server’s slug, UUID, or numeric ID — the resolver tries each in order.

Create a server from a deploy script

The slug becomes part of the MCP endpoint URL: https://yoursite.com/mcp/customer-api.

Pause and resume

Paused servers return 503 Service Unavailable to MCP clients without removing the server config — ideal for emergency cutovers.

Test a tool against your upstream API

Runs the tool through the live executor (with auth, parameter mapping, response transforms — everything an MCP client would trigger). Exits 1 if the upstream returns isError: true so you can use it as a smoke test in CI.

Mint a one-shot API key

The plaintext key is printed once at creation. Copy it immediately — there’s no way to retrieve it after this command exits.

Revoke an API key


Output Formats

Every list-style subcommand supports the standard WP-CLI formats via --format=<format>: Combine ids + xargs for batch operations:

wp getmcp doctor

Runs a self-diagnostic and reports the status of every dependency GetMCP cares about. Exits 1 on any failed check so it’s CI-friendly.
Sample output:
Use it as a release gate:
If doctor exits non-zero the workflow fails before the rest of the deploy continues.

Recipes

Bulk-create servers from a CSV

Snapshot all servers as JSON for backup

Revoke every key matching a name pattern


Troubleshooting

WP-CLI isn’t installed. Follow the WP-CLI install guide — on most VPS hosts it’s a one-line curl + chmod step.
Run from inside your WordPress directory, or pass --path=/var/www/html (the path to your WP root).
The plugin isn’t active on this install. Activate it with wp plugin activate getmcp and try again.
The tool’s authentication isn’t configured on this server. Check the Authentication tab in the GetMCP admin and confirm the bearer token / API key / OAuth credentials are set for the parent server.
Either the license activation hasn’t completed yet (the InfiAuth client is still warming up) or your activation has expired. Check License in the admin and re-activate.

WP-CLI commands are gated behind defined( 'WP_CLI' ) && WP_CLI so the command classes never load during normal web requests — there’s zero runtime cost on your front end.