# WordPress.com MCP connector

The WordPress.com connector brings your sites, posts, pages, users, plugins and domains into Elaichi, so Claude, ChatGPT, Cursor or any MCP client can draft, publish and manage them as the person who signed in.

Source: https://elaichi.ai/connectors/wordpress-com/

## Facts

| | |
| --- | --- |
| Application | WordPress.com |
| Category | Application Development |
| AI tools | 19 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. WordPress.com builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | wordpress.com/support/contact |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once WordPress.com is connected

- Draft a post announcing the spring pricing update for the main site
- Which plugins are installed on the agency client sites?
- Point the shop domain's mail records at Google Workspace

## Connect WordPress.com in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick WordPress.com.
2. Optionally set Share with, then press Connect.
3. Approve it in WordPress.com. WordPress.com's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which WordPress.com tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## WordPress.com MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## WordPress.com MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## WordPress.com MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect WordPress.com to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a WordPress.com tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with WordPress.com through Elaichi

### Turn a campaign brief into a published post

Marketing. Hand over the brief and get a draft post on the right WordPress.com site, then publish it or schedule it for the launch date once it reads well.

### Catch the pricing page up after a change

Content. When plans or prices move, ask for the pricing page to be updated with the new numbers and check the result before it goes live.

### Point a domain at the right place

IT. Update DNS records or nameservers for a domain held on WordPress.com, and restore the defaults if a change goes wrong.

### Set up email on a new domain

Operations. Choose a mail service for a domain and have the right records added, so the new address works the day the team needs it.

### Spin up a new client site

Agency. Create a site, compare the WordPress.com plans, and hand the client a checkout link for the plan and domain they picked.

### Add a contributor and check their plugins

Support. Give a new writer the right role on a site, see which plugins are installed, and confirm nothing is missing before they start.

## Elaichi vs Zapier MCP vs Composio for WordPress.com

All three can connect WordPress.com to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over WordPress.com tools | Allow or restrict single WordPress.com tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per WordPress.com call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect WordPress.com to Claude?

Connect WordPress.com in Elaichi first. WordPress.com shows its own sign-in screen, you approve access as yourself, and that is the whole setup, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi and your WordPress.com sites appear.

### Does WordPress.com work with ChatGPT and Cursor as well as Claude?

Yes. Once WordPress.com is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect WordPress.com once and every client you use picks it up.

### What can an AI agent actually do with my WordPress.com data?

With WordPress.com connected, an agent can draft and publish posts and pages, edit site content, list your sites, manage users and plugins, create a new site, check plans and produce a checkout link, and update DNS records, nameservers and mail settings for your domains. Short, concrete asks work best, such as "publish the draft about the new office on the company site" rather than a long paragraph.

### Does connecting WordPress.com give the AI access to every site I own?

The AI only sees what the person who signed in to WordPress.com can see. If you are an editor on two sites and an administrator on a third, that is exactly what the agent can reach. Elaichi can narrow that further, for example to publishing only, and can never widen it beyond your own WordPress.com access.

### Can my team share one WordPress.com connection?

Yes. One person connects WordPress.com in Elaichi and shares it with a team, and nobody else ever handles a password or token. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who published a post or changed a DNS record, not the account that was shared.

### Can I stop an agent from deleting or changing things in WordPress.com?

Yes. Restrictions in Elaichi work per action, so you can allow drafting posts on WordPress.com while blocking publishing, user changes or DNS edits. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however it is worded, can reach it.

### What happens to a WordPress.com connection when someone leaves?

Offboarding a person in Elaichi ends their access to WordPress.com through every client at once. A WordPress.com connection that was shared with a team keeps working for everyone else. If you want it gone entirely, disconnecting WordPress.com once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

### Does the WordPress.com MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. WordPress.com is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for WordPress.com?

Yes. Both let Claude, ChatGPT or Cursor use WordPress.com. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every WordPress.com call.

### How is Elaichi different from Composio for WordPress.com?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to WordPress.com: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 19 WordPress.com tools

Every tool below is callable through https://api.elaichi.ai/mcp once WordPress.com is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Wpcom mcp content authoring** (Action). Create, read, update, and delete content on a WordPress.com site: posts, pages, comments, media, categories, tags, block patterns, synced patterns, and content search. Includes block-level editing, so a single section of a page or post can be changed in place, and AI image…
- **Wpcom mcp site editor context** (Action). Query site design context — theme presets, applied styles, and registered block types. Read-only companion to Content Authoring. Use it before creating or updating content so the markup uses theme-aligned tokens rather than hard-coded values.
- **Wpcom mcp account** (Action). Manage the authenticated user’s WordPress.com account: profile, notifications, achievements, domains, subscriptions and billing, connections, security, and currency. Operates on the calling user; no wpcom_site parameter required.
- **Wpcom mcp site** (Action). Manage a WordPress.com site: settings, statistics, plugins, collaborators, activity log, themes, backups, security scans, and Jetpack module configuration. Requires wpcom_site (site ID or URL).
- **Wpcom mcp user management** (Action). Manage collaborators on a WordPress.com site: list them, invite new ones, change roles, and remove access. Requires wpcom_site (site ID or URL).
- **Wpcom mcp plugin management** (Action). Manage plugins on a WordPress.com site across their full lifecycle: search the catalog, install, upload, activate, deactivate, update, and uninstall. plugin.search works at account level and needs no site. Every other operation requires wpcom_site .
- **Wpcom mcp site editing** (Action). Read and change site structure: templates, template parts, navigation, classic theme widgets, global styles, and installed themes. Requires wpcom_site (site ID or URL).
- **Wpcom mcp create site** (Create). Provision a new WordPress.com site, either blank or from a template, for the user to build out with the other MCP tools.
- **Wpcom user sites** (Action). List the user’s accessible sites across WordPress.com and self-hosted Jetpack-connected sites. Use it to find site IDs before calling site-scoped tools. Supports pagination, search, status and privacy filters, sorting, and optional site metrics.
- **Wpcom domain purchase** (Action). Search for available domains and generate checkout links for registration. Returns matching domains with prices and pre-built checkout URLs.
- **Wpcom domain update DNS records** (Update). Add or remove DNS records (A, AAAA, ALIAS, CAA, CNAME, MX, NS, SRV, TXT) for a single custom domain you manage. Write.
- **Wpcom domain restore default DNS records** (Restore). Restore the WordPress.com default A records (apex IPs) or the default www CNAME for a single custom domain. Gated by the “Update DNS records” setting. Write.
- **Wpcom domain update nameservers** (Update). Set the nameservers for a single custom domain. Requires the caller to manage the site the domain is connected to. Accepts between 2 and 13 valid nameserver hostnames. Write.
- **Wpcom domain set mail service** (Set). Configure DNS records on a domain for an external mail service: Google Workspace, iCloud Mail, Office 365, or Zoho Mail. Write.
- **Wpcom checkout URL** (Action). Generate a pre-configured checkout URL for one or more products, or for a subscription renewal. The URL takes the user to WordPress.com checkout; payment happens in the browser, not through this tool.
- **Wpcom plans list** (List). List WordPress.com plans with prices and per-tier feature lists. Read-only. Useful for surfacing plan options before generating a checkout URL.
- **Wpcom AI agent sites list** (List). List public WordPress.com sites whose owners have enabled AI Agent Access. Filter by a natural-language topic query or by keywords, matched against site metadata. Discovers opted-in sites; does not search inside one.
- **Wpcom mcp jetpack search voice** (Search). Search a single public, opted-in blog and return the results together with that blog’s voice guidelines. Built for reader-facing questions about a public blog. Short, specific, noun-heavy queries work best.
- **Wpcom mcp send feedback** (Send). Send a feature request, bug report, or general feedback about the WordPress.com MCP server to the development team. Takes a type of request , bug , or general , plus plain-text content .