Skip to content

Site Agent WordPress MCP Tools.

An AI agent that can’t see your WordPress site works from guesses and pasted snippets. Site Agent is my free plugin that connects your AI client to the site itself, so the agent reads the real content and code before it changes anything.

Get Site Agent Connect Your Client
  • 18 MCP tools
  • OAuth sign-in
  • Staged edits
  • PHP rollback

Free and open source. Clients sign in through WordPress with OAuth, on by default, and every tool that changes something stays off until you switch it on.

  • ChatGPT
  • Claude
  • Gemini
  • Claude Code
  • Cursor
  • VS Code
  • Codex
  • Zed
Site AgentExample tool calls
Direct to WordPress

Stage an Edit to a Live Post

The agent sends the new content with the hash it got when it read the post. The post is published and no status is passed, so WordPress saves the change as an autosave for you to review.

Content writes

The live post changes only when the agent passes a status such as publish.

MCP tool call
{
  "name": "site-agent-save-content",
  "arguments": {
    "post_id": 42,
    "content": "<!-- wp:paragraph --><p>A clearer intro.</p><!-- /wp:paragraph -->",
    "expected_content_sha256": "9f2c6a..."
  }
}

WordPress MCP Tools

Site Agent gives your agent 18 tools, and on Bricks sites it can add Bricks’ own abilities too. The read tools work as soon as Site Agent is enabled. Every tool that changes something sits behind its own switch in Tools > Site Agent.

Read the Site

On with Site Agent
Site context site-context
WordPress, PHP, theme, plugins, page builders, post types and the tools this connection can use.
List content list-content
Search posts and pages, with the latest edits first.
Read content get-content
Block markup, terms, featured image, SEO fields and the builder that stores the layout, by ID, URL or slug.
List terms list-terms
Categories, tags and other terms with their IDs.
List media list-media
Library items with URLs, dimensions and alt text.
List skills list-skills
The builder skills that ship with the plugin, and which builders this site runs.
Read skill get-skill
A builder’s workflow and reference files, read before the agent writes.

Publish Content

Content writes
Save content save-content
Drafts and updates, with terms, featured image, slug, schedule and SEO meta.
Upload media upload-media
Import an image from a URL or file data, with alt text.
Update media update-media
Fix titles, alt text, captions and descriptions.

Inspect Source

Source inspection
List files list-files
Browse plugins, themes and must-use plugins.
Read file read-file
Source code with the hash needed to change it.

Edit Source

Source editing
Write file write-file
Create or replace a file. A PHP change that breaks the site is reverted.
Create directory create-directory
Start a new plugin or theme folder.
Move file move-file
Rename or move a file that still matches its hash.
Delete file delete-file
Remove a file or an empty folder, with the same checks.

Run Code

PHP and WP-CLI
Execute PHP execute-php
Run PHP with WordPress loaded and get the output and return value.
Run WP-CLI run-wp-cli
Foreground commands as the signed-in user, without a shell.

Bricks Builder

Bricks tools
Bricks fast path bricks-*
Bricks’ own tools for page edits, imports and design context, under their own names.
List Bricks abilities bricks-abilities
Every other ability Bricks offers on this site, with its schema on request.
Run Bricks ability run-bricks-ability
Run any of them, with Bricks’ own permission and input checks.

Works With Your Page Builder

An agent that writes block markup into an Elementor or Bricks page changes nothing visitors see, because the real layout lives somewhere else. Site Agent tells the agent where each layout lives and how that builder expects it to be changed.

Page builders, where each one stores its layouts and how the agent changes them
BuilderLayout lives inHow the agent changes it
GutenbergBlock markup in the postContent writes, then a byte-exact read-back
GenerateBlocksBlock markup with its own CSSContent writes, after a serializer check
ElementorJSON in post metaElementor’s own save, sent as small patches
BricksElement arrays in post metaBricks’ own abilities on Bricks 2.4 and later
DiviShortcodes or Divi 5 blocks in the postContent writes, or exact fragment edits

A Skill for Each Builder

Five builder skills ship with the plugin. The agent reads the matching one before it writes, so it follows that builder’s storage and escaping rules instead of guessing.

Layout Data Stays Intact

Content writes refuse raw Elementor, Bricks and Divi layout data. Writing it directly skips the builder’s validation and leaves stale CSS behind, so the skills use each builder’s own save.

Bricks on the Same Connection

On Bricks 2.4 and later, switch on Bricks tools and your agent gets Bricks’ own abilities next to Site Agent’s: page summaries, revisions and CSS regeneration, with Bricks’ permissions still in charge.

Works With Page Blocks Builder and GT Link Manager

Install either of my plugins and Site Agent picks up its skill. Your agent reads the skill, then works through that plugin’s own commands, with the same permission checks as wp-admin.

Page Blocks Builder

Pages and sections in your own HTML, CSS and JavaScript

  • Create a draft page from sections, with or without the theme header and footer.
  • Read and change one section at a time. A hash check stops the agent from overwriting newer edits.
  • Changes to a published page are staged as your autosave.
  • Create, render and place reusable library blocks.

Page Blocks Builder 4.2 or newer, with PHP execution on in Site Agent.

See Page Blocks Builder

GT Link Manager

Branded short links such as /go/product

  • Create links with the redirect type and nofollow or sponsored attributes.
  • Check for an existing link before adding a duplicate.
  • Set country-based destinations and sort links into categories.
  • Read click analytics, for administrators.

GT Link Manager 1.10 or newer, with PHP execution on in Site Agent.

See GT Link Manager

Other plugins can add their own read-only skills through the site_agent_skills filter.

Safety Checks on Every Change

An agent with write access will get something wrong sooner or later. I built Site Agent so the common mistakes are caught, or easy to undo, before your visitors see them.

Live Posts Stay Live

When the agent edits a published post, the change is saved as an autosave you review in the editor, and the agent can read it back to check it. The live post changes only when the agent passes a status.

Broken PHP Gets Reverted

PHP is checked for syntax and compile errors first. After saving, Site Agent loads your site and puts the old file back if the change causes a fatal error.

No Silent Overwrites

Every update needs the hash from the agent’s last read. If you or another tool changed the post or file since then, the write is refused.

Errors the Agent Can Fix

Failed PHP and tool calls return the real message and line number, so the agent can correct its own code instead of guessing.

Limits per Password

Each Application Password can be limited to the tools it needs, such as content writes for a chat app and developer tools for your local coding agent.

A Record of Every Call

The audit history keeps the last 100 calls with the tool, target, password name and result. It never stores content, code or credentials.

Site Agent Application Password access table where each password can be limited to content writes, source inspection, source editing, PHP execution or WP-CLI execution, with password names redacted
Tap the screenshot to open it at full size.

Choose Your Agent’s Access

Access starts switched off. You turn on Site Agent, pick the tool groups the task needs and save.

Every tool call then checks:

  • an administrator account (a super administrator on multisite)
  • the switch for that tool group
  • the tool groups you approved for that client, or the limit on its Application Password

Revoking a connection in Tools > Site Agent ends it everywhere, including sessions that are already open.

Read the Access Model
Tool groups, their default state and the number of tools in each
Tool groupDefaultTools
Read the siteOn7
Content writesOff3
Source inspectionOff2
Source editingOff4
PHP executionOff1
WP-CLI executionOff1
Bricks toolsOff2+

SITE_AGENT_DISABLED in wp-config.php blocks every tool.

SITE_AGENT_ALLOW_EXECUTION set to false blocks the tools that change code. Content tools and source inspection keep working.

DISALLOW_FILE_EDIT blocks every source and developer tool.

Bricks tools need Bricks 2.4 or later with its AI/MCP abilities switched on, and add Bricks’ own fast-path tools to the 2 listed.

Site Agent settings screen in WordPress with a separate switch for Site Agent, URL authentication, content writes, source inspection, source editing, PHP execution, WP-CLI execution and audit history
Tap the screenshot to open it at full size.

Developer Tools Need a Trusted Client

I recommend a staging site with a current backup for the developer tools. They run with server privileges and aren’t a sandbox:

  • PHP can change the database and files.
  • Source edits change executable code.
  • WP-CLI can change the WordPress installation.

Connect Your AI Client

OAuth is on by default, so connecting takes 4 steps and there’s no token to copy.

  1. Install the Plugin

    Upload the ZIP from your account in Plugins > Add New, then open Tools > Site Agent.

  2. Choose the Tools

    Enable Site Agent and the tool groups your task needs, then save.

  3. Add the Endpoint

    Add https://your-site.com/wp-json/site-agent/v1/mcp to your client as a remote MCP server, with no credentials.

  4. Approve the Client

    Sign in to WordPress, check the tool groups it should have and choose Allow. You land back in your client, connected.

Site Agent consent screen in WordPress: ChatGPT asks to connect, with checkboxes for content edits, reading and changing source files, running PHP and WP-CLI, and Allow and Deny buttons
The consent screen your client opens. You pick what it can do, then choose Allow.

OAuth Sign-In Default

On by default. Clients that follow the MCP authorization spec find Site Agent’s sign-in on their own. You approve each client on a WordPress consent screen and pick its tool groups. Access tokens last an hour, refresh tokens rotate, and you can revoke a connection in Tools > Site Agent.

Application Password Header

Not recommended. A client that can’t sign in can send Authorization: Basic BASE64_TOKEN, which keeps the password out of URLs. Tools > Site Agent warns while one is in use, and the agent is told to suggest OAuth.

Authenticated URL

Not recommended. Apps that only accept a URL get the endpoint with ?auth=BASE64_TOKEN added. URLs can end up in logs and browser history, and MCP’s authorization guidance discourages tokens in them, so give this route a dedicated password you can revoke.

Setup by Client

Replace your-site.com with your domain. Every client below signs in with OAuth, so there’s no token to paste.

ChatGPT

ChatGPT connects to MCP servers in developer mode on paid plans and signs in with OAuth.

  1. Enable Site Agent in Tools > Site Agent. OAuth connections are on by default.
  2. In ChatGPT, open Settings and turn on Developer mode. OpenAI’s guide lists the switch under Security and login.
  3. Add a new app with the plus button, name it Site Agent, paste the endpoint as the MCP server URL and choose OAuth.
  4. Sign in to WordPress when ChatGPT asks, check the tool groups and choose Allow.
  5. In a chat, pick Developer mode from the + menu and select Site Agent.

OpenAI offers developer mode to Plus, Pro, Business, Enterprise and Education accounts on the web. ChatGPT connects from OpenAI’s servers, so your site must be public over HTTPS.

MCP server URL
https://your-site.com/wp-json/site-agent/v1/mcp
WordPress 6.9+With the Abilities API
PHP 8.0+On the web server
HTTPSRequired for remote clients
AdministratorSuper administrator on multisite

Site Agent Is Free

The free checkout gives you the complete plugin and a license for automatic updates.

The code is public and GPL-licensed, and every tool works without activating the license. The license only connects your site to the update service, so new versions arrive in your Plugins screen.

Browse the Source on GitHub
$0Plugin and update license
  • All 18 tools and the safety checks
  • OAuth sign-in, on by default
  • Skills for Page Blocks Builder and GT Link Manager
  • Skills for Gutenberg, GenerateBlocks, Elementor, Bricks and Divi
  • Bricks’ own abilities on Bricks 2.4 and later
  • Automatic updates with the free license
  • WordPress 6.9 or newer and PHP 8.0 or newer
Get Site Agent

The download and license key appear in your account after the free checkout.

Before You Connect

These are the questions worth settling before you give an agent access to a site.

Which AI clients can connect?

Any client that supports remote MCP servers over Streamable HTTP. Clients that support MCP’s OAuth sign in through WordPress with no token to copy, and that’s the default.

For a client without OAuth, an Application Password in a header or URL still works, but Tools > Site Agent marks it as not recommended.

Is it safe to give an AI agent write access?

It is safe enough for content work on most sites, because edits to live posts are staged and every update is checked against the last read. The developer tools are a different matter. They run with server privileges, so I’d keep them on a staging site with a backup and give production passwords content access only.

What happens when the agent edits a published post?

The change is saved as your autosave. WordPress shows it in the editor next to the live version, and you decide whether to restore and publish it. The agent can update the live post directly only by passing a status, and it should do that only when you’ve asked for it.

Does it work with Elementor, Bricks or Divi?

Yes. Site Agent tells the agent which builder stores each page’s layout, and the matching skill explains how to change it. Content writes refuse raw Elementor, Bricks and Divi layout data, because writing it directly skips the builder’s validation and cache refresh.

  • On Bricks 2.4 and later, switch on Bricks tools and the agent works through Bricks’ own abilities.
  • Elementor changes need the PHP tool, because Elementor’s own save runs in PHP.
  • Divi pages are edited like other post content.
Does it work with Page Blocks Builder and GT Link Manager?

Yes. Each plugin ships a skill that Site Agent lists automatically. The agent reads it, then runs the plugin’s own commands through the PHP tool, so PHP execution has to be on.

  • Page Blocks Builder 4.2 and later: build pages, edit sections and manage library blocks.
  • GT Link Manager 1.10 and later: create, update and organize short links, and read click analytics.
Where does my site’s data go?

Your AI client connects directly to WordPress. Site Agent has no hosted proxy and no telemetry. The client and its AI provider handle tool results under their own privacy policy.

Automatic updates send gauravtiwari.org:

  • your license key and activation
  • your site URL
  • the plugin, WordPress and PHP versions

PHP and WP-CLI can also make outbound requests when the agent asks them to.

What can the file tools reach?

The file tools work only inside these folders in wp-content:

  • plugins
  • themes
  • mu-plugins

Hidden files and symlinks are blocked, and so are credential files such as wp-config.php and auth.json. Site Agent can’t edit its own files. Source code can still contain secrets, which is why source inspection has its own switch.

How do updates work?

Complete the free checkout, then activate the license on the Site Agent screen. New versions then appear in your Plugins screen like any other update. The license controls updates only, and you can always install a release ZIP by hand.

Start With a Staging Site

Connect your agent, check what it can read, then switch on more tools when the task needs them.

Get Site Agent View the Source