# WordPress VIP MCP connector

The WordPress VIP connector brings your site's reusable blocks, block patterns, revisions, autosaves and application passwords to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with every call running as the person who signed in.

Source: https://elaichi.ai/connectors/wordpressvip/

## Facts

| | |
| --- | --- |
| Application | WordPress VIP |
| Category | Marketing Automation |
| AI tools | 153 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, 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 VIP is connected

- Show me the block patterns in the call to action category
- What changed in the homepage hero block this week?
- List application passwords created in the last 30 days

## Connect WordPress VIP in Elaichi

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

1. Open Connections, choose Add connection, and pick WordPress VIP.
2. Optionally set Share with, then press Connect.
3. Paste a WordPress VIP API key. One person generates a token in WordPress VIP and pastes it once. Everyone else works through Share with, and never sees it.

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

## WordPress VIP 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 VIP MCP connector for Claude Code

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## WordPress VIP 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. The plugin directory lives at chatgpt.com/plugins.

## WordPress VIP 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.

## WordPress VIP MCP connector for Microsoft Copilot

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

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect WordPress VIP 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

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a WordPress VIP tool needs "Use your connected apps". 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. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with WordPress VIP through Elaichi

### Find the right block pattern before a launch

Marketing. Ask which block patterns and pattern categories your WordPress VIP site already has, so a landing page is built from approved layouts instead of a new one.

### See what changed in a reusable block

Editorial. Pull the revision history for a WordPress VIP block and get a plain summary of what was edited, by whom and when, before it goes live again.

### Update a brand block once, everywhere

Design. Change the copy or layout of a synced block in WordPress VIP and every page that uses it picks up the edit.

### Rotate application passwords without the admin screen

IT. List the application passwords on your WordPress VIP site, create a fresh one for a service and delete the ones nobody uses any more.

### Recover a draft from an autosave

Web. When an editor loses work, find the latest WordPress VIP block autosave and bring the content back into the block.

### Audit which block types the site registers

Operations. Get a list of every block type available on your WordPress VIP site, grouped by namespace, so the theme and plugin inventory is always current.

## Elaichi vs Zapier MCP vs Composio for WordPress VIP

All three can connect WordPress VIP 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 VIP tools | Allow or restrict single WordPress VIP 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 VIP 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 | Free for one person; $15 per user per month on Gold. | 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 VIP to Claude?

Connect WordPress VIP in Elaichi by pasting an API key from WordPress VIP, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. Once Claude signs in to Elaichi, your WordPress VIP blocks, patterns and revisions are available in the chat.

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

Yes. WordPress VIP is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. Each person signs in as themselves in whichever client they use.

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

An agent can list and search the reusable blocks, block patterns, pattern categories and block types on your WordPress VIP site, read a block's revision history and autosaves, and create, update or delete a block. It can also list, create and delete the application passwords used by services. Short, concrete asks work best, such as the name of a block and what you want changed.

### Does connecting WordPress VIP give the AI access to everything on my site?

No. Every call runs as the person who signed in, so an agent sees exactly the blocks, patterns and application passwords that person's WordPress VIP role allows and nothing more. Elaichi can narrow that access with restrictions, and it can never widen it beyond what WordPress VIP itself grants.

### Can my team share one WordPress VIP connection?

Yes. One person connects WordPress VIP with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every WordPress VIP call.

### Can I stop an agent from deleting or changing blocks in WordPress VIP?

Yes. Restrictions in Elaichi apply per action, so you can allow reading WordPress VIP blocks and revisions while restricting updates, deletions or application password changes, on a role or on one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a WordPress VIP connection when someone leaves?

Offboarding a person in Elaichi ends their access to WordPress VIP at once, in every client they used. A shared WordPress VIP connection keeps working for everyone else on the team. If you disconnect WordPress VIP in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent in one step.

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

Yes. WordPress VIP 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, Microsoft Copilot, 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 VIP?

Yes. Both let Claude, ChatGPT or Cursor use WordPress VIP. 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 VIP call.

### How is Elaichi different from Composio for WordPress VIP?

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 VIP: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 153 WordPress VIP tools

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

- **List all WordPress VIP application passwords** (List). List the application passwords of a user (user_id or me); secrets are never returned. Required: user_id.
- **Create a WordPress VIP application password** (Create). Create an application password for a user; the generated password is returned only in this response. Required: user_id, name.
- **WordPress VIP application passwords bulk delete** (Delete). Revoke all application passwords of a user. Required: user_id.
- **Get single WordPress VIP application password by ID** (Get). Retrieve one application password of a user by its uuid. Required: id, user_id.
- **Update a WordPress VIP application password by ID** (Update). Rename an application password (by uuid). Required: id, user_id.
- **Delete a WordPress VIP application password by ID** (Delete). Revoke one application password (by uuid). Required: id, user_id.
- **List all WordPress VIP application password introspections** (List). Retrieve the application password used to authenticate the current request. Required: user_id.
- **List all WordPress VIP block directory items** (List). Search the WordPress.org block directory for installable block plugins (requires the install_plugins capability). Paged with per_page (max 100); use context=edit for fields only editors can see. Required: term.
- **List all WordPress VIP block pattern categories** (List). List the block pattern categories registered on the site.
- **List all WordPress VIP block patterns** (List). List the block patterns registered on the site.
- **List all WordPress VIP block revisions** (List). List block revisions of a parent object. Paged with per_page (max 100); use context=edit for fields only editors can see. Required: parent.
- **Get single WordPress VIP block revision by ID** (Get). Retrieve one block revision by id of a parent object. Required: id, parent.
- **Delete a WordPress VIP block revision by ID** (Delete). Delete a block revision of a parent object (revisions do not support trashing; pass force=true). Required: id, parent.
- **List all WordPress VIP block autosaves** (List). List block autosaves (the autosaves of a parent object). Required: parent.
- **Create a WordPress VIP block autosave** (Create). Create a block autosave (store an autosave of the parent object). Required: parent.
- **Get single WordPress VIP block autosave by ID** (Get). Retrieve one block autosave by id of a parent object. Required: id, parent.
- **List all WordPress VIP block types** (List). List block types.
- **Get single WordPress VIP block type by ID** (Get). Retrieve one registered block type by namespace and name (id), e.g. namespace=core, id=paragraph. Required: id, namespace.
- **List all WordPress VIP namespace block types** (List). List the registered block types in one namespace (e.g. core). Required: namespace.
- **List all WordPress VIP blocks** (List). List blocks. Paged with per_page (max 100); use context=edit for fields only editors can see.
- **Create a WordPress VIP block** (Create). Create a reusable block (synced pattern).
- **Get single WordPress VIP block by ID** (Get). Retrieve one reusable block (synced pattern) by id. Required: id.
- **Update a WordPress VIP block by ID** (Update). Update a reusable block (synced pattern). Required: id.
- **Delete a WordPress VIP block by ID** (Delete). Delete a reusable block (synced pattern). Moves to trash unless force=true (media and some types require force=true). Required: id.
- **List all WordPress VIP categories** (List). List categories. Paged with per_page (max 100); use context=edit for fields only editors can see.
- **Create a WordPress VIP category** (Create). Create a category. Required: name.
- **Get single WordPress VIP category by ID** (Get). Retrieve one category by id. Required: id.
- **Update a WordPress VIP category by ID** (Update). Update a category. Required: id.
- **Delete a WordPress VIP category by ID** (Delete). Delete a category. Terms and menus do not support trashing; pass force=true. Required: id.
- **List all WordPress VIP comments** (List). List comments. Paged with per_page (max 100); use context=edit for fields only editors can see.
- **Create a WordPress VIP comment** (Create). Create a comment.
- **Get single WordPress VIP comment by ID** (Get). Retrieve one comment by id. Required: id.
- **Update a WordPress VIP comment by ID** (Update). Update a comment. Required: id.
- **Delete a WordPress VIP comment by ID** (Delete). Delete a comment. Moves to trash unless force=true (media and some types require force=true). Required: id.
- **List all WordPress VIP media** (List). List media. Paged with per_page (max 100); use context=edit for fields only editors can see.
- **Create a WordPress VIP media** (Create). Upload a media item (multipart/form-data with the file part plus optional title, alt_text, caption, description and post). Required: file.
- **Get single WordPress VIP media by ID** (Get). Retrieve one media item by id. Required: id.
- **Update a WordPress VIP media by ID** (Update). Update a media item. Required: id.
- **Delete a WordPress VIP media by ID** (Delete). Delete a media item. Moves to trash unless force=true (media and some types require force=true). Required: id.
- **List all WordPress VIP menu locations** (List). List menu locations.
- **Get single WordPress VIP menu location by ID** (Get). Retrieve a theme menu location by name (id). Required: id.
- **List all WordPress VIP menu item autosaves** (List). List menu item autosaves (the autosaves of a parent object). Required: parent.
- **Create a WordPress VIP menu item autosave** (Create). Create a menu item autosave (store an autosave of the parent object). Required: parent.
- **Get single WordPress VIP menu item autosave by ID** (Get). Retrieve one menu item autosave by id of a parent object. Required: id, parent.
- **List all WordPress VIP menu items** (List). List menu items. Paged with per_page (max 100); use context=edit for fields only editors can see.
- **Create a WordPress VIP menu item** (Create). Create a menu item.
- **Get single WordPress VIP menu item by ID** (Get). Retrieve one menu item by id. Required: id.
- **Update a WordPress VIP menu item by ID** (Update). Update a menu item. Required: id.
- **Delete a WordPress VIP menu item by ID** (Delete). Delete a menu item. Moves to trash unless force=true (media and some types require force=true). Required: id.
- **List all WordPress VIP menus** (List). List menus. Paged with per_page (max 100); use context=edit for fields only editors can see.
- ...and 103 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
