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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
19 tools
How to connect
How to connect WordPress.com to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect WordPress.com once
-
Open Connections, choose Add connection, and pick WordPress.com.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in WordPress.com. WordPress.com's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
WordPress.com MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect WordPress.com to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with WordPress.com through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Turn a campaign brief into a published post
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.
-
Content
Catch the pricing page up after a change
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.
-
IT
Point a domain at the right place
Update DNS records or nameservers for a domain held on WordPress.com, and restore the defaults if a change goes wrong.
-
Operations
Set up email on a new domain
Choose a mail service for a domain and have the right records added, so the new address works the day the team needs it.
-
Agency
Spin up a new client site
Create a site, compare the WordPress.com plans, and hand the client a checkout link for the plan and domain they picked.
-
Support
Add a contributor and check their plugins
Give a new writer the right role on a site, see which plugins are installed, and confirm nothing is missing before they start.
Try asking
- “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”
Compare
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
WordPress.com tools for your AI agents
19 tools are ready to call through Elaichi's MCP endpoint the moment you connect WordPress.com, governed by the same roles, restrictions, and audit log as everything else in Elaichi. WordPress.com builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting WordPress.com gets you
6 screens from the product, each doing one job for your WordPress.com account.
The agent
Ask about your sites and get real answers.
Ask which posts went live this week and the answer comes from WordPress.com.
- posts
- pages
- sites
- domains
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT or Cursor
MCP clients
Use WordPress.com from Claude, ChatGPT or Cursor.
One governed endpoint, signed in over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
19 WordPress.com tools, ready without any code.
Posts, pages, users, plugins, domains and DNS, covered without writing custom code.
- Wpcom mcp content authoring
- Wpcom mcp site editor context
- Wpcom mcp account
- Wpcom mcp site
ElaichiToolsToolboxes
Every team gets its own WordPress.com toolbox.
Content gets publishing, IT gets domains and DNS, each toolbox scoped to one team.
- Marketing
- Content
- IT
- Agency
ElaichiToolboxesShared connections
Share the connection, never the password.
One person connects WordPress.com and teammates work through it without seeing a credential.
- Marketing
- Content EMEA
- IT
- Client sites
ElaichiConnectionsAudit log
Every WordPress.com change has a name on it.
When, who, what happened and which post or domain, kept in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts the weekly content digest.
New posts are fetched, grouped, drafted into a digest, approved, then published back to WordPress.com.
WordPress.com digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch posts
WordPress.com
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
WordPress.com
Queued
Collections and dashboards
Site health numbers arrive without being asked.
Posts created over 14 days, split by team, computed from WordPress.com with no model involved.
WordPress.com health
Refreshed 4 minutes ago · every 15 minutes · from the posts collection
Posts
1,284 ↓ 12%
Pages
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Posts created
Last 14 days
By team
Share of activity
Marketing 34%
Content EMEA 27%
IT 21%
Client sites 18%
FAQ
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 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.
Put WordPress.com in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.