What is LocalWP Agent Tools?
LocalWP Agent Tools is an add-on for the Local WordPress app from 10up. Enabling it on a site registers that site with a local MCP server and writes MCP config and context files, so an AI tool gets WP-CLI, log, config and site tools.
It is an add-on for Local, the desktop WordPress development app. When you click Enable on a site, the add-on registers it with an MCP server running in Local's main process and writes the config files your AI tool needs.
The README lists four things it does: register the site, write MCP config such as .mcp.json and .cursor/mcp.json, generate project context files, and update .gitignore so files carrying the token are not committed.
What the add-on writes and serves
- A single HTTP MCP server for all sites, with a global endpoint and one endpoint per site.
- MCP config files for Claude Code, Cursor, Windsurf and VS Code Copilot.
- Context files with PHP and MySQL versions, active plugins, theme and file structure.
- A bearer token stored with owner-only permissions, required on every request.
Who it is for
Best for
- Developers who build and debug WordPress sites locally in Local.
- Teams that want an agent to run WP-CLI and read logs with site context already supplied.
- Agencies spinning up disposable preview copies to test a change.
Not for
- Live sites. It controls sites running inside Local on your own machine.
- Setups without Local 9.0 or later.
Use it with UiChemy
Agent Tools helps with local WordPress development. UiChemy Composer has its own MCP that works on your own WordPress site. For getting design work into WordPress, see AI to WordPress for freelance designers. Click Get Started on uichemy.com.
Connect LocalWP Agent Tools: An MCP Server Inside Local to your AI client
git clone <repo-url> agent-tools && cd agent-tools && npm install --legacy-peer-deps && npm run buildBuild from source
The README's install path is from source: clone, run npm install with the legacy peer deps flag, then npm run build.
Copy into Local's add-ons folder
Copy the built add-on into the add-ons directory for your OS, named agent-tools, then run npm install --production --ignore-scripts there.
Restart Local and enable
Restart Local, open a site and click Enable in the Agent Tools panel. The add-on writes MCP config and context files for the agents you pick.
Open the site folder
Open the site folder in your AI tool. Config files hold a bearer token and are git-ignored. Prefer the Site Root install location so the token is not in the web root.
Client configuration
{
"mcpServers": {
"local-wp-global": {
"type": "http",
"url": "http://localhost:24842/sites/mcp",
"headers": { "Authorization": "Bearer <token from ~/.local-agent-tools/token>" }
}
}
}Endpoints and ports
http://localhost:24842/sites/mcpDefault port 24842, persisted in ~/.local-agent-tools/porthttp://localhost:{port}/sites/{siteId}/mcpOne site, bound tools includedWhat you can do with it
- One server for every siteA single HTTP server runs inside Local, with no separate Node process per site.
- Global endpointConnect once to list sites, create a site and enable Agent Tools on it, then use the returned site endpoint.
- Per-client configConfig files are written for each client in the README's supported agents table, such as Cursor, Windsurf and VS Code Copilot, each paired with a context file.
- Token protectionEvery request needs a bearer token, and Host and Origin headers are checked. The README says another process running as your user can still read the token.
- Guarded WP-CLIwp_cli blocks destructive commands and flags that run code or reach remote hosts.
- Disposable previewsClone a site into a preview with its own domain and endpoint, then destroy it with a tool that refuses to delete regular sites.
Tools it exposes
wp_cli
Runs WP-CLI commands, blocking destructive commands and the --exec, --require, --ssh and --http flags.
read_error_log
Reads and parses the PHP error log.
read_access_log
Reads the nginx access log.
wp_debug_toggle
Turns WP_DEBUG, WP_DEBUG_LOG and SCRIPT_DEBUG on or off.
read_wp_config
Parses wp-config.php constants, redacting secrets by default.
edit_wp_config
Adds or changes a wp-config.php constant, with a backup.
get_site_info
Returns paths, URLs, database config, versions, plugins and theme.
site_health_check
Checks database connectivity, permissions, WP_DEBUG and log sizes.
site_start
Starts a site's services.
create_site
Creates a new WordPress site in Local.
preview_start
Clones a site into a disposable preview with its own database and endpoint.
enable_agent_tools
Enables Agent Tools on a site and writes its config.
Frequently asked questions
What is LocalWP Agent Tools?
It is a 10up add-on for Local that runs an MCP server for your local WordPress sites. It gives an AI tool 21 tools for WP-CLI, logs, wp-config, site start and stop, site creation and preview sites.
How do I install LocalWP Agent Tools?
The README gives a from-source install: clone the repository, run npm install with the legacy peer deps flag, run npm run build, copy the add-on into Local's add-ons folder, install production dependencies there and restart Local.
What does LocalWP Agent Tools require?
Local 9.0 or later and an MCP compatible AI tool. The README lists support for macOS on arm64 and x64, Windows and Linux, and names Claude Code, Cursor, Windsurf and VS Code Copilot.
How is the LocalWP MCP server secured?
Every request needs an Authorization bearer token stored with 0600 permissions, and the server answers only localhost or 127.0.0.1 host headers. The README warns that another process running as your user can read the token.
Does LocalWP Agent Tools work on live sites?
No. It controls sites that run inside Local on your own machine. The tools start and stop local services, read local logs and edit local wp-config files, so there is no live site connection involved.
Can an agent create a new site with LocalWP Agent Tools?
Yes. create_site uses the same code path as Local's Add Site flow. It returns before provisioning finishes, so site_status must be polled, and Local may ask for an administrator password to update hosts.
Is LocalWP Agent Tools free and open source?
The repository is licensed GPL-2.0-or-later, and the README labels its support level as active. The install path it describes is a build from source, with no one click installer described in the README.
What are alternatives to LocalWP Agent Tools?
For a similar local focus see the WordPress Developer MCP Server. For plugin based access on a site see Novamira or WP MCP Ultimate. For page builders see Respira WordPress MCP and the Figma MCP server. For page builders see Respira WordPress MCP and the Figma MCP server.


