Menu
Mattering Automations connector

A WordPress MCP for automations that reach past WordPress

Connect your site with an application password and posts, pages, media, comments, categories, tags, users, plugins, and site settings become workflow steps. An AI agent can draft a post, attach a featured image pulled from a URL, and hold it for your approval before anything goes live, and the results land next to your tasks and databases instead of in wp-admin tabs.

48 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the WordPress MCP connector does

The WordPress connector for Mattering Automations is 48 nodes on the WordPress REST API v2 of your own site: posts and pages through their full draft-to-publish lifecycle, the media library with upload from a public URL, comment moderation, categories and tags, user accounts, plugin activation, site settings, installed themes, site-wide search, and post revisions. One credential holds it all: your site URL, a WordPress username, and an application password that user generates.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can search the site for the post that mentions a product, read its content and revision history, fix the copy, and re-publish, without anyone logging into wp-admin.

WordPress ships its own official MCP integration: the WordPress mcp-adapter package, built on the Abilities API that arrived in core 6.9, gives an assistant a direct line into a site that installs it. This connector is for the other half of the job, where WordPress is one step among many. On the Mattering canvas the same nodes sit next to every other connector and the platform itself, so a form submission can become a draft post, a publish can wait behind a human approval task, and a plugin-version audit can write what it finds into a Mattering database. It also asks nothing of the site beyond core: any WordPress 5.6 or later install over https works as-is, with no plugin to add. Use whichever fits, or both.

The safety modeling follows how WordPress itself treats deletion. Of the 48 nodes, 25 read and 23 act, and the deletes split along WordPress's trash-versus-force line: post, page, and comment deletes default to the recoverable trash, while four nodes are flagged destructive because WordPress gives their targets no trash at all: media deletes (the file goes with it), category deletes, tag deletes, and user deletes. Some write surfaces are deliberately not shipped: installing or deleting plugins puts runtime PHP on the site and stays in wp-admin, theme switching has no endpoint in core's REST surface, and revision deletes erase history for near-zero automation value.

One connection, three surfaces

  • Visual automations. Drag WordPress nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every WordPress node, ready to drop on the canvas

48 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 25

WordPress: Get Comment

Fetch one comment: commenter name, content (rendered object), status, parent, and the post it belongs to.

WordPress: Get Current User

Fetch the user the stored Application Password belongs to: id, display name, and slug (context=edit adds email, roles, and capabilities). Any authenticated user can call it, so this is the credential health check to run first in any WordPress automation.

WordPress: Get Media

Fetch one media item: source_url (the direct file URL), MIME type, alt text, caption, and the generated size variants under media_details.

WordPress: Get Page

Fetch one page: title/content/excerpt (rendered objects), status, parent, menu order, and template.

WordPress: Get Plugin

Fetch one installed plugin: status, version, author, and WordPress/PHP version requirements. Needs an Administrator credential.

WordPress: Get Post

Fetch one post: title, content, and excerpt (each as {rendered: ...} objects), status, author, featured media, and assigned category/tag IDs.

WordPress: Get Post Status

Fetch one post status by its slug: name and its public/private/protected/queryable flags.

WordPress: Get Post Type

Fetch one post type by its slug: name, hierarchy flag, associated taxonomies, and rest_base route.

WordPress: Get Site Settings

Read the site's settings in one call: title, tagline, admin email, timezone, date/time formats, language, default category, posts per page, front-page configuration, and default comment/ping status. Needs an Administrator credential.

WordPress: Get Taxonomy

Fetch one taxonomy by its slug: name, hierarchy flag, associated post types, and rest_base route.

WordPress: Get User

Fetch one user: display name, slug, description, and avatar URLs (context=edit adds email, roles, and capabilities).

WordPress: List Categories

List categories with their term IDs, names, slugs, hierarchy, and per-term post counts. Sorted by name ascending by default.

WordPress: List Comments

List comments with filters on post, commenter email, status (approve is the default; hold/spam/trash need an authorized user), and date range. The moderation-queue read: status=hold lists comments awaiting approval.

WordPress: List Media

List media-library items (attachments) with filters on search text, media type (image, video, audio, text, application), MIME type, and date ranges. Returns media IDs used by the update/delete nodes and by featured-image fields.

WordPress: List Pages

List pages with filters on search text, author, slug, status, menu order, and date ranges. Returns page IDs used by the get, update, and delete nodes. Totals arrive in the X-WP-Total response header: page by incrementing page.

WordPress: List Plugins

List installed plugins with their identifiers (dir/file form), names, versions, and active/inactive status. Needs an Administrator credential. The site-audit read behind version-monitoring automations.

WordPress: List Post Revisions

List a post's saved revisions: each carries the revision id, author, date, and the title/content/excerpt as of that save. The audit trail for edit-tracking automations.

WordPress: List Post Statuses

List the site's registered post statuses (publish, future, draft, pending, private, trash) as an object keyed by status slug, each with its visibility flags.

WordPress: List Post Types

List the site's registered post types (post, page, attachment, plus any custom types) as an object keyed by type slug, each with its taxonomies and rest_base route, the discovery call for sites with custom content types.

WordPress: List Posts

List posts with filters on search text, author, category, tag, status, slug, and publish/modified date ranges. Returns post IDs used by the get, update, and delete nodes. Totals arrive in the X-WP-Total response header (not carried in the node output): page by incrementing page until a short page comes back.

WordPress: List Tags

List tags with their term IDs, names, slugs, and per-term post counts. Sorted by name ascending by default.

WordPress: List Taxonomies

List the site's registered taxonomies (built-in category and post_tag plus any custom ones) as an object keyed by taxonomy slug, each with its rest_base route and the post types it applies to.

WordPress: List Themes

List installed themes with their stylesheet identifiers, names, versions, and active/inactive status. Read-only: core's REST surface has no theme-activation endpoint, so this connector reports themes rather than switching them.

WordPress: List Users

List the site's users with their IDs, display names, and slugs (context=edit adds emails and roles). Unauthorized requests only see users with published content.

WordPress: Search Site Content

Search across the site's content in one call: returns lightweight results (id, title, url, type, subtype) spanning posts, pages, and other public post types - the find-it-first step before a get node.

Action nodes 23

WordPress: Activate or Deactivate Plugin

Activate or deactivate an installed plugin by setting its status. Fully reversible (set the opposite status), but note a plugin toggle changes live site behavior the moment it lands. Needs an Administrator credential. Installing or deleting plugins is deliberately not offered by this connector.

WordPress: Create Category

Create a category. Reversible with WordPress: Delete Category.

WordPress: Create Comment

Create a comment on a post, optionally as a reply to another comment. Authenticated requests comment as the credential's user unless author fields are set (setting arbitrary author fields needs moderation permission). Reversible with WordPress: Delete Comment (default delete is the trash).

WordPress: Create Page

Create a page. Defaults to a draft; set status to publish to go live. Reversible with WordPress: Delete Page (default delete is the trash).

WordPress: Create Post

Create a post. Defaults to a draft; set status to publish to go live immediately, or to future with a date to schedule. Reversible with WordPress: Delete Post (default delete is the trash).

WordPress: Create Tag

Create a tag. Reversible with WordPress: Delete Tag.

WordPress: Create User

Create a user account (username, email, and password are required by the API). Needs an Administrator credential. Reversible with WordPress: Delete User.

WordPress: Delete Category

DESTRUCTIVE: delete a category, permanently - per the vendor docs force is required to be true, as terms do not support trashing. Posts in the category are not deleted; they fall back to the default category.

WordPress: Delete Comment

Move a comment to the trash (the default), restorable from wp-admin. force=true bypasses the trash and deletes PERMANENTLY.

WordPress: Delete Media

DESTRUCTIVE: delete a media item AND its file from the uploads directory, permanently. Attachments only support a recoverable trash when the site defines the MEDIA_TRASH constant (off by default), so force defaults to true here; on a default site a force-less delete is rejected by WordPress. Posts using the file keep broken references.

WordPress: Delete Page

Move a page to the trash (the default), restorable from wp-admin. force=true bypasses the trash and deletes PERMANENTLY.

WordPress: Delete Post

Move a post to the trash (the default), where it can be restored from wp-admin for 30 days. force=true bypasses the trash and deletes PERMANENTLY - content and revisions are gone.

WordPress: Delete Tag

DESTRUCTIVE: delete a tag, permanently - per the vendor docs force is required to be true, as terms do not support trashing. Tagged posts keep their other tags.

WordPress: Delete User

DESTRUCTIVE: delete a user account, permanently - per the vendor docs force is required to be true, as users do not support trashing. Their posts and links are handed to the reassign user (required by the API). Application passwords owned by the deleted user stop working.

WordPress: Update Category

Update a category's name, description, slug, or parent; only the fields you fill are changed.

WordPress: Update Comment

Update a comment; only the fields you fill are changed. THE MODERATION NODE: set status to approved to approve a held comment, hold to unapprove, or spam to mark it spam, each reversible by writing the previous status back.

WordPress: Update Media

Update a media item's metadata: title, alt text, caption, description, associated post, or author. The file itself is not changed. Only the fields you fill are sent.

WordPress: Update Page

Update fields on an existing page; only the fields you fill are changed. Publish a draft, re-parent the page, or swap its template.

WordPress: Update Post

Update fields on an existing post; only the fields you fill are changed. The workhorse edit: publish a draft (status=publish), retitle, swap the featured image, or reassign categories.

WordPress: Update Site Settings

Change site settings; only the fields you fill are sent. Reversible by writing the previous values back (read them first with WordPress: Get Site Settings). Needs an Administrator credential.

WordPress: Update Tag

Update a tag's name, description, or slug; only the fields you fill are changed.

WordPress: Update User

Update fields on a user; only the fields you fill are changed. Changing roles or passwords needs an Administrator credential.

WordPress: Upload Media from URL

Upload a file into the media library from a public URL: the node downloads the file (up to 50 MB) and re-uploads the bytes to WordPress, which is how the REST API takes uploads (core has no create-from-URL endpoint of its own). The site's own upload_max_filesize still applies. Returns the new attachment with its media ID and source_url. Reversible with WordPress: Delete Media.

Connecting WordPress takes one credential

WordPress is self-hosted, so the credential is per-site: the site URL, a WordPress username, and an application password that user generates. Application passwords have shipped in WordPress core since 5.6 and authenticate REST API requests served over https using Basic auth. Each one is generated on the user's own profile page in wp-admin, is shown once at creation, and can be revoked there at any time without changing the account's login password. Every request acts with that user's role, so the credential's user decides what the automation can do: an Editor covers content, an Administrator is needed for users, plugins, and site settings.

1

Sign in to wp-admin on your site, open Users, then Profile (or Edit User for another account), and scroll to Application Passwords. A dedicated automation user with the lowest role your workflows need is the tidy setup.

2

Enter a name like Mattering Automations and click Add New Application Password. Copy the generated password now: WordPress displays it once, and the spaces it shows are fine to keep.

3

In Mattering Automations, open Connectors, click Add Connector, choose WordPress, and create a credential with the site URL, the WordPress username, and the application password. The site must be served over https; plain http URLs are refused because Basic auth over plain http exposes the credential.

4

Click Test Connection. Mattering calls the site's own users/me endpoint, which answers for any authenticated user regardless of role: a result with your username proves the credential, an error means the URL, username, or password is wrong or the application password was revoked.

5

All 48 WordPress nodes appear in the canvas palette. Run WordPress: List Posts and WordPress: List Users first; post IDs and user IDs are the two values most downstream nodes ask for.

Common uses for the WordPress MCP

A content pipeline that ends in a draft, not a surprise

WordPress: Create Post defaults to a draft, which is the right default for automation: a workflow can turn a form submission, a task, or an agent's writing into a post that exists but is not public. Set status to future with a date to schedule it, or leave it for a human, and when the review passes, WordPress: Update Post flips status to publish. The same node retitles, swaps the featured image, or reassigns categories, changing only the fields you fill.

Comment moderation without living in wp-admin

WordPress: List Comments with status set to hold is the moderation queue as data: every comment awaiting approval, with its author and content. An agent or a scheduled workflow can read the queue, judge each one, and act through WordPress: Update Comment, the moderation node: status approved to approve, hold to unapprove, spam to flag. Each move is reversible by writing the previous status back, and WordPress: Delete Comment defaults to the trash rather than permanence.

A media library fed from anywhere

Core WordPress has no upload-from-URL endpoint, so WordPress: Upload Media from URL does the work the API will not: it downloads the file from a public URL (up to 50 MB) and re-uploads the bytes to the site, returning the new attachment's media ID and direct file URL. The site's own upload size limit still applies. WordPress: Update Media then sets the alt text, caption, and title, and the media ID slots into the featured-image field on WordPress: Create Post and WordPress: Update Post.

Site audits that land in a database

WordPress: List Plugins returns every installed plugin with its version and active state, WordPress: List Themes does the same for themes, and WordPress: Get Site Settings reads the site title, admin email, timezone, and front-page configuration in one call. A scheduled sweep across your sites can write the results into a Mattering database and open a task when a version changed or a setting drifted. The plugin and settings nodes need an Administrator credential, which is honest: that is who audits a site.

An AI agent that edits with a paper trail

WordPress: Search Site Content finds the page or post that mentions the thing, WordPress: Get Post reads it, and WordPress: Update Post makes the change. WordPress keeps the receipts on its own: every save lands in the revision history, and WordPress: List Post Revisions shows an automation's edits alongside everyone else's, each with its author and timestamp. If a change was wrong, the revision carries the content as of that save, and WordPress: Delete Post defaults to the trash, restorable from wp-admin, rather than to permanence.

Taxonomy housekeeping at list scale

WordPress: List Categories and WordPress: List Tags return every term with its post count, which is the raw material for cleanup: an agent can spot near-duplicate tags, merge them by re-tagging posts through WordPress: Update Post, and retire the empties. WordPress: Create Category and WordPress: Create Tag keep new content filed consistently. The term deletes are flagged destructive because WordPress gives terms no trash, so a workflow gates them behind a condition or an approval step.

Example: A draft arrives: upload the image, create the post, wait for approval, publish

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: an inbound webhook fires with a finished draft, its hero image URL, and the category it belongs in, from a writing pipeline, a form, or an agent.

2

WordPress: Upload Media from URL pulls the hero image into the media library and returns its media ID.

3

WordPress: Create Post creates the post as a draft with the title, content, category, and the new media ID as the featured image. Nothing is public yet.

4

The workflow opens a review task in Mattering Productivity with the draft's preview link, and waits.

5

When the task is approved, WordPress: Update Post sets status to publish and the post goes live.

6

The workflow writes the published URL back onto the task, so the record of what shipped lives next to the rest of the work.

WordPress MCP questions, answered

What WordPress operations are supported?

48 nodes on the WordPress REST API v2: 25 query nodes and 23 action nodes covering posts (list, get, create, update, delete, plus revision history), pages, the media library with upload from URL, comments with full moderation, categories and tags, users, plugin listing and activation, site settings, installed themes, site-wide search, and the taxonomy, post type, and post status registries. Deliberately not shipped: plugin install and delete, theme activation (core's REST surface has no endpoint for it), revision deletes, and the block editor's internal endpoints.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

WordPress has an official MCP adapter. Why use this connector?

WordPress maintains mcp-adapter, its official MCP package built on the Abilities API in core 6.9, and if all you want is an assistant talking to one WordPress site, it is a genuine option. This connector earns its place when WordPress is one step in a larger workflow: the same canvas holds your other connectors and the Mattering platform itself, so a form submission can become a draft, a publish can wait behind an approval task, and a plugin audit can write into a database next to the rest of your work. It also runs against plain core, WordPress 5.6 or later over https, with nothing to install on the site. Use whichever fits, or both.

Does this work with WordPress.com sites?

The connector is built for self-hosted WordPress, where the standard REST API and application passwords ship with core. WordPress.com is a hosted product with its own plans, and whether a given plan exposes the standard REST surface with application passwords is a question for WordPress.com's own documentation. If your site answers at its wp-json route and offers Application Passwords on the profile page, the connector can talk to it.

What can the automation actually do on my site?

Exactly what the credential's user can do, because every request acts with that user's role. A credential from an Editor covers posts, pages, media, and comment moderation but is refused by the user, plugin, and settings nodes, which need an Administrator. Application passwords are also revocable per password on the user's profile page, so cutting an automation off takes one click and does not touch the account's login.

Can an automation permanently delete content?

Only where it says so out loud. Post, page, and comment deletes default to WordPress's trash, restorable from wp-admin, and only bypass it when force is explicitly set. Four nodes are flagged destructive because WordPress gives their targets no trash: media deletes remove the file from the uploads directory, category and tag deletes are immediate, and user deletes require naming another user to inherit the deleted account's posts. The flags exist so workflows can gate those nodes behind conditions or approval steps.

What are WordPress's API rate limits?

WordPress core documents no rate limit of its own on the REST API; the practical bound is your hosting, and managed WordPress hosts commonly throttle API traffic. List endpoints cap per_page at 100 items per request, so wide reads page through results. Since the API is your own site, a heavy sweep competes with your visitors for the same server, which is a better reason to schedule audits off-peak than any quota is.

Can an AI agent publish posts safely?

The defaults are on your side. WordPress: Create Post creates a draft unless a workflow explicitly sets status to publish, so the honest pattern is agent drafts, human approves, workflow publishes, with the approval living as a Mattering task between the create and the update. Every save also lands in WordPress's own revision history, which WordPress: List Post Revisions reads, so an agent's edits carry the same paper trail as a person's.

48 nodes waiting on the canvas

Put WordPress to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. WordPress is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products