WordPress.com Official Remote MCP Server
The WordPress.com MCP endpoint (public-api.wordpress.com/wpcom/v2/mcp/v1) exposes your WordPress.com sites โ posts, pages, media and settings โ to agents after a standard WordPress.com OAuth flow.
- Provider
- Automattic โ
- Categories
- ๐จ Design & UI/UX๐ ๏ธ Developer Tools & Git
ไธญๆ็ฎไป
WordPress.com ๅฎๆน่ฟ็จ MCP ๆๅกๅจ๏ผ็ฑ Automattic ๆ็ฎกใAI ไปฃ็ๅฏ้่ฟ OAuth ่ฏปๅๆ็ซ ไธ้กต้ขใ็ฎก็ๅ ๅฎน่็จฟๅนถๆฅ็็ซ็น่ฎพ็ฝฎใ
Maintainer of WordPress.com? Claim or update this listing โ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"wordpress": {
"url": "https://public-api.wordpress.com/wpcom/v2/mcp/v1"
}
}
}claude mcp add --transport http wordpress https://public-api.wordpress.com/wpcom/v2/mcp/v1
Or add to .vscode/mcp.json:
{
"servers": {
"wordpress": {
"type": "http",
"url": "https://public-api.wordpress.com/wpcom/v2/mcp/v1"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://public-api.wordpress.com/wpcom/v2/mcp/v1 - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://public-api.wordpress.com/wpcom/v2/mcp/v1"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"wordpress": {
"serverUrl": "https://public-api.wordpress.com/wpcom/v2/mcp/v1"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"wordpress": {
"url": "https://public-api.wordpress.com/wpcom/v2/mcp/v1"
}
}
}Add to ~/.codex/config.toml โ Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.wordpress] url = "https://public-api.wordpress.com/wpcom/v2/mcp/v1"
Add to cline_mcp_settings.json (Cline โ MCP Servers โ Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"wordpress": {
"type": "streamableHttp",
"url": "https://public-api.wordpress.com/wpcom/v2/mcp/v1"
}
}
}Add to ~/.gemini/settings.json under mcpServers โ httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"wordpress": {
"httpUrl": "https://public-api.wordpress.com/wpcom/v2/mcp/v1"
}
}
}๐งฐ WordPress.com MCP Tools & Schema (5)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| list_sites ~38 tok | ๐ข Read | List WordPress.com sites accessible to your account. | โ |
| list_posts ~83 tok | ๐ข Read | List posts on a site with status and search filters. | siteId*: stringstatus: stringsearch: string |
| get_post ~70 tok | ๐ข Read | Get the full content and metadata of a post or page. | siteId*: stringpostId*: string |
| create_post_draft ~87 tok | ๐ Write | Create a draft post or page on a site. | siteId*: stringtitle*: stringcontent*: string |
| list_media ~67 tok | ๐ข Read | List media library items on a site. | siteId*: stringmediaType: string |
๐ก๏ธ Security, Quality & Context Token Audit
Every tool definition (name + description + input schema) is injected into your LLMโs context on every request โ Estimate per-call LLM token cost โ
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- OAuth 2.1 with PKCE S256 enforced
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Scopes
readwrite- Protected resource metadata
- https://public-api.wordpress.com/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ WordPress.com MCP Endpoint Overview & Security Guide
WordPress.com MCP โ Remote MCP Server
WordPress.com's remote MCP gives agents a managed route into the wpcom REST surface: enumerate your sites, pull posts and pages for summarization or cross-posting, and create drafts for human review โ all behind WordPress.com's standard OAuth, no plugin install required.
Official WordPress.com MCP Endpoint & Transport Architecture
- Endpoint URL:
https://public-api.wordpress.com/wpcom/v2/mcp/v1 - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. WordPress.com MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
WordPress.com MCP uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
Of the 5 cataloged tools, 4 are read-only and 1 can write or mutate state (create resources, run SQL, post messages). Grant access only to the accounts and projects you intend agents to act on, and prefer scoped credentials or a dedicated workspace where the provider supports them.
Common Troubleshooting & Connection Tips
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - Applies to WordPress.com hosted sites; self-hosted WordPress needs the wp-mcp community plugin instead.
- Write operations create drafts by default โ review before publishing.
๐ How to Connect
- Copy the WordPress.com MCP endpoint URLThe remote endpoint is https://public-api.wordpress.com/wpcom/v2/mcp/v1.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http wordpress https://public-api.wordpress.com/wpcom/v2/mcp/v1. Cursor: add"wordpress": { "url": "https://public-api.wordpress.com/wpcom/v2/mcp/v1" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Automattic consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://public-api.wordpress.com/wpcom/v2/mcp/v1 into remotemcp.net/inspector, run initialize and tools/list, and confirm WordPress.com MCP's 5 tools respond.
โ FAQ
What is the WordPress.com MCP remote MCP endpoint?
The primary endpoint is https://public-api.wordpress.com/wpcom/v2/mcp/v1. It is an official first-party server operated by Automattic, speaking the Streamable HTTP transport.
How do I authenticate with WordPress.com MCP?
WordPress.com MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from WordPress.com MCP โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with WordPress.com MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http wordpress https://public-api.wordpress.com/wpcom/v2/mcp/v1`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does WordPress.com MCP expose?
5 tools are cataloged in this directory โ including `list_sites`, `list_posts`, `get_post` and more. Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
Related Servers
Figma's official remote MCP server. Agents can pull design context, variables, Code Connect mappings and screenshots from your Figma files.
Canva's official remote MCP server. Agents can search your designs, generate new designs from templates, autofil brand content and export to image or PDF โ with interactive MCP Apps rendering.
CastHTML's hosted remote MCP server. CastHTML's MCP lets Claude, Cursor and other AI agents publish generated HTML dashboards or Markdown research reports as sandboxed, shareable online links (cast_live_... API key as bearer). It authenticates with a bearer token or API key sent via the Authorization header.
The official drawio (diagrams.net) remote MCP server โ public and authless. Agents can generate diagrams as drawio XML and open them directly in the editor via interactive MCP Apps.