pulsemcp Safe content atomic mcp-remote

WordPress Remote

MCP WordPress Remote serves as a bridge between local Model Context Protocol clients and WordPress websites running the wordpress-mcp plugin. Developed by Automattic, it eliminates the need for direct streaming connections by efficiently translating MCP requests into simple REST API calls to WordPress. The proxy handles authentication through WordPress API passwords and WooCommerce credentials, supports all standard MCP operations including tools, resources, and prompts, and implements comprehensive logging for troubleshooting. It's particularly valuable for users who want to leverage WordPress content and WooCommerce data through AI assistants without managing complex API integrations or maintaining persistent connections to their websites.

Cognium trust score

65%

Tier

Unverified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: ecommerce
Source: PulseMCP
Repository: github.com/automattic/mcp-wordpress-remote
Author type: human
Updated: 2026-05-27

View source Find related skills

MCP

Resolve WordPress Remote from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"