What is MCP?
The Model Context Protocol (MCP) is an open protocol, introduced by Anthropic in late 2024, that standardises how AI applications connect to external tools and data. Instead of building a custom integration for every assistant, a service exposes an MCP server once and any MCP-compatible client can use it.
How MCP works
There are three roles. The host is the AI app (for example a desktop assistant or code editor). Inside it, an MCP client keeps a connection to one or more MCP servers. Each server advertises capabilities — mainly tools (actions the model can call), resources (data it can read) and prompts (reusable templates). The model decides when to call a tool; the host runs it and returns the result.
MCP for websites and WordPress
An MCP server can expose website operations — reading analytics, listing pages, creating draft posts, updating metadata. For WordPress, community and vendor MCP servers typically wrap the WordPress REST API. Always connect with a limited-permission account and keep publishing behind a human review step.
MCP for AI coding and automation
Coding assistants use MCP servers to reach issue trackers, databases, browsers, documentation and deployment tools. Automation platforms increasingly offer MCP endpoints so an assistant can trigger workflows you already trust.
MCP with Claude and ChatGPT
Anthropic's Claude apps and Claude Code support connecting MCP servers. OpenAI has also added MCP support to its developer platform and ChatGPT connectors. Exact availability depends on plan and product and changes often — check each vendor's current documentation before relying on a feature.
MCP security considerations
An MCP server acts with whatever permissions you give it. Only install servers from sources you trust, review the tools they expose, use scoped API keys, prefer read-only access where possible, watch for prompt injection in content the model reads, and require confirmation before destructive or public actions.