Base URL
All admin REST API endpoints are under the GetMCP namespace:
https://yoursite.com/wp-json/getmcp/v1
yoursite.com with the domain of the WordPress site where GetMCP is installed.
Authentication
The GetMCP admin API uses API key authentication. Every request must include your API key in the Authorization header.
Authorization: Bearer gmcp_your_api_key_here
Generating Your API Key
Open GetMCP Settings
In your WordPress admin, navigate to GetMCP > Settings.
Go to the API Keys tab
Click the API Keys tab in the Settings page.
Generate a Key
Click Generate New Key. Your key will be displayed once — copy it immediately and store it securely.
Your API key is shown only once at generation time. Store it in a secure location such as an environment variable or secrets manager. If you lose it, generate a new one — this immediately revokes the old key.
gmcp_ followed by a 32-character hex string:
gmcp_a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4
Example Request
curl -H "Authorization: Bearer gmcp_your_api_key" \
"https://yoursite.com/wp-json/getmcp/v1/servers"
X-WP-Total — Total number of itemsX-WP-TotalPages — Total number of pages
Error Responses
Errors follow this format:
{
"code": "getmcp_not_found",
"message": "Server not found.",
"data": {
"status": 404
}
}
Common Error Codes
| Code | HTTP Status | Description |
|---|
rest_forbidden | 403 | Invalid or missing API key |
getmcp_not_found | 404 | Resource not found |
getmcp_create_failed | 500 | Failed to create resource |
getmcp_update_failed | 500 | Failed to update resource |
getmcp_delete_failed | 500 | Failed to delete resource |
getmcp_missing_curl | 400 | cURL import: missing command |
getmcp_invalid_params | 400 | Invalid parameters |
Two URL Spaces
GetMCP has two distinct URL spaces — do not confuse them:
| Purpose | Base URL | Auth |
|---|
| MCP Protocol (AI clients connect here) | https://yoursite.com/mcp/{slug}/{id} | MCP API key or none |
| Admin REST API (manage configuration) | https://yoursite.com/wp-json/getmcp/v1/ | GetMCP API key |
