Skip to content
Documentation

What is MCP?

The Model Context Protocol is an open standard from Anthropic for connecting AI assistants to external tools and data sources. It’s like REST for AI agents, a stable contract for “here are the things you can do, here are the things you can read.”

The core idea

Section titled “The core idea”

Before MCP, every AI client had its own way of integrating external systems. ChatGPT plugins, Claude tool-use, Cursor commands, OpenAI function-calling: different shapes, different runtimes, different limits. MCP unifies all of that into one protocol.

An MCP server exposes:

  • Tools: actions the AI can take (list-widgets, create-page, update-element)
  • Resources: data the AI can read (Elementor data, page content, settings)
  • Prompts: pre-defined templated prompts

An MCP client connects to one or more servers and surfaces their tools to the AI it’s driving. The AI then decides which tools to call based on the user’s prompt.

How EMCP Tools fits in

Section titled “How EMCP Tools fits in”

EMCP Tools is an MCP server that runs inside your WordPress install. It registers up to 207 tools, each one a wrapper around an Elementor or WordPress operation. The MCP client is your AI app: Claude Code, Claude Desktop, Cursor, Antigravity, etc. The client connects to your EMCP Tools server over HTTP or stdio and gains the ability to manipulate Elementor and the wider WordPress site.

The flow looks like this:

You → AI client → MCP server (EMCP Tools) → Elementor → WordPress
        ↑              ↓
        AI decides     Server returns
        which tools    JSON results
        to call

No vendor lock-in. Any MCP-compatible client speaks to any MCP-compatible server. Switching from Claude to Cursor doesn’t require re-configuring anything on the WordPress side. The server is the same.

Transport: HTTP vs stdio

Section titled “Transport: HTTP vs stdio”

MCP supports multiple transports. The two that matter for EMCP Tools:

  • HTTP: the server is a REST endpoint at /wp-json/mcp/emcp-tools-server. Clients hit it over the network, send a session-ID header, get JSON back. Works for remote WordPress installs, easy to debug with curl.
  • stdio: the server runs as a subprocess (via wp mcp-adapter serve), reads JSON-RPC from stdin, writes responses to stdout. No HTTP, no auth, no sessions, but client and server must be on the same machine. Faster for local dev.

Both transports expose the exact same tools and behavior. Pick the one that fits your setup.

Where to learn more

Section titled “Where to learn more”

Why this matters for WordPress

Section titled “Why this matters for WordPress”

Every WordPress install gains an API for free when you activate the MCP Adapter: the data is already there, the permissions model is already there, the auth (Application Passwords) is already there. MCP just exposes it in a shape AI agents can use.

EMCP Tools is one application of that idea, Elementor-specific. There’s no reason the same approach couldn’t extend to WooCommerce, Gravity Forms, ACF, custom post types: anything with structured data. The MCP Adapter is the substrate; EMCP Tools is one server built on top of it.