ToolsConnector
WordPress
Write drafts, schedule posts, edit pages and upload media on a WordPress site from Claude or ChatGPT via Tulina's MCP server, with no plugin to install.
Official site: wordpress.org
What it can do
1 read/2 write/3 send
- 01Send
Write a post in one call from Markdown, as a draft, with categories, tags, a featured image and an SEO description
- 02Send
Publish, schedule or take a post back to draft in a separate step
- 03Send
List, read, edit and trash posts, pages and custom content types, with a dry run before an edit
- 04Write
Upload media from an address and edit its alt text and caption
- 05Write
Read and manage categories, tags and custom taxonomies
- 06Read
Work across several sites, one named account per site
A blog that depends on a person copying text from a chat into an editor loses the hour it was meant to save. The Tulina connector lets an agent write the post straight into WordPress as a draft, with its categories, image and SEO description, and leaves the publish button to a person unless told otherwise. It uses an application password on a site over HTTPS, so there is no plugin to install.
Is there any MCP for WordPress?
Yes. WordPress publishes the MCP Adapter, an official package from its Core AI team that exposes a site's registered Abilities as MCP tools. WordPress 6.9 introduced the Abilities API and ships three default abilities: site information, current user information and environment information. Anything beyond that is registered by a plugin or by your own code. Tulina's connector is a different route: it works from outside the site through WordPress's REST API and needs no plugin.
How do you add a WordPress MCP?
Through Tulina's own MCP server, in three steps:
- In Tulina, open the WordPress card and choose Connect my WordPress site. Enter the site address and approve access in your wp-admin. WordPress creates an application password and sends it back, so there is nothing to copy. By hand, create one under Users, Profile, Application Passwords and paste the site address, username and password into the form.
- Use an Author, Editor or Administrator account. A Contributor cannot publish anything. The site needs WordPress 5.6 or newer, served over HTTPS.
- Add
https://mcp.tulina.ai/mcpto Claude or ChatGPT and sign in with your Tulina account. The MCP page has the same link.
Each site is a named account, so an agency can connect as many as it manages. To revoke access, use the Revoke button on the same profile screen in WordPress.
WordPress's MCP Adapter and Tulina's WordPress connector
| WordPress MCP Adapter | Tulina's WordPress connector | |
|---|---|---|
| Who runs it | You, as a package installed on the site | Tulina, calling the site's REST API |
| What it exposes | The Abilities that core and plugins register | Posts, pages, custom types, media and taxonomies |
| Sign-in | Application password in WordPress's own example, other methods possible | Application password, created by an approve button or by hand |
| Install on the site | Yes | No |
| Custom abilities from your own plugin | Yes | No |
| Next to your other tools | WordPress | WordPress plus the CRM, chat and spreadsheet connectors |
If a plugin of your own should expose its functions to an agent, the adapter is the better route. Tulina earns its place when the work is editorial: a brief in Notion, a draft in WordPress, a note in Slack when it is ready.
What you can ask it
"Write a post from this brief and save it as a draft in the Guides category." The agent reads the site's content types and taxonomies, writes the post from Markdown with the categories and tags you named, and returns the draft. Nothing is public.
"Schedule the draft for Monday at 9." The agent publishes it with that date. Publishing is its own tool and is the only call that puts a post live.
"Fix the pricing paragraph on the About page." The agent reads the page, shows the change as a dry run, and applies it only after you accept. A page that is already published changes the site as soon as the edit lands.
What runs on its own: a scheduled run can list recent posts and report what went out this week, since WordPress sends no events without a plugin. Sites built on Webflow have their own connector.
What the WordPress connector can't do
- It cannot publish by accident: creating or editing refuses a publish status, and only the publish tool goes live. Editing a post that is already published changes the site right away, so use the dry run first.
- Media is public from the moment it is uploaded, because WordPress has no draft media. The featured image of a draft can be read at its address.
- HTML in the Markdown becomes a Custom HTML block, kept as is only if the account can post unfiltered HTML.
- Yoast and Rank Math fields are written only when the plugin exposes them to the REST API. Otherwise the post is created and the response says the SEO fields were not written.
- Deleting a post or page sends it to the trash; categories, tags and media have no trash and go for good.
- On WordPress.com, only Business plans and above accept application passwords.
- A total across several sites means calling each site in turn.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect WordPress once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach WordPress at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against WordPress returns something usable instead of something generic.
Processes that run on WordPress
None published yet.