The SSE protocol will be deprecated soon. Please use streamable-http as the connectionType moving forward.

​
Prerequisites

To get the most out of this guide, you’ll need to:

​
1. Create a WordPress MCP Server

Use the following endpoint to create a new remote WordPress MCP server instance:

​
Request

curl --request POST \
  --url https://api.klavis.ai/mcp-server/instance/create \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
  "serverName": "WordPress",
  "userId": "<YOUR_USER_ID>",
  "platformName": "<YOUR_PLATFORM_NAME>"
}'

​
Response

{
  "serverUrl": "https://wordpress-mcp-server.klavis.ai/sse?instance_id=<instance-id>",
  "instanceId": "<instance-id>"
}
serverUrl specifies the endpoint of the WordPress MCP server, which allows you to interact with WordPress sites.
instanceId is used to get an authentication token. After you complete the OAuth flow, this token allows the MCP server to access WordPress on your behalf.

​
2. WordPress OAuth Flow

To enable your MCP server to access WordPress, you need to authenticate with WordPress’s OAuth flow.

const authUrl = `https://api.klavis.ai/oauth/wordpress/authorize?instance_id=${instanceId}`;
window.location.href = authUrl;

​
Watch the Example

​
Explore MCP Server Tools