LocalWP Agent Tools
A add-on that provides an MCP server and project context for AI-powered WordPress development. Works with Claude Code, Cursor, Windsurf, VS Code Copilot, and any MCP client.
Potencia tu agente
Instalación del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
Aún no hay una versión empaquetada en el registro. Sigue el README del repositorio.
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
A add-on that provides an MCP server and project context for AI-powered WordPress development. Works with Claude Code, Cursor, Windsurf, VS Code Copilot, and any MCP client.
A Local add-on that provides an MCP server, skills, and project context for AI-powered WordPress development. Works with Claude Code, Cursor, Windsurf, VS Code Copilot, and any MCP client.
When you click "Enable" on a site in Local, the add-on:
.mcp.json, .cursor/mcp.json, etc.) — auto-configured with the correct HTTP endpoint and the per-install bearer token for each agent (see Authentication below)CLAUDE.md, .cursorrules, etc.) — site context including PHP/MySQL versions, active plugins, theme, and file structure.gitignore — the MCP config files now carry a secret (the bearer token) alongside the generated context files, so all of them are git-ignored and none are committedThen open the site folder in your AI tool of choice and you're ready to go.
The MCP server runs as a single HTTP server inside Local's Electron main process — no separate Node.js processes per site. It serves two kinds of endpoint:
http://localhost:{port}/sites/mcp # global — all of Local
http://localhost:{port}/sites/{siteId}/mcp # one specific site
The server uses the MCP Streamable HTTP transport. The port is stable across restarts (persisted at ~/.local-agent-tools/port, default 24842).
Sites remain registered even when stopped, so the MCP endpoint is always reachable. Tools that need running services (WP-CLI, database) return appropriate errors; file-based tools (config, logs, site info) work regardless. Config is refreshed on each tool call, so starting a site automatically makes database tools work without reconnecting.
Every request to the MCP server needs an Authorization: Bearer <token> header. That header is the only channel; there is no ?token= URL parameter.
The add-on creates the token on first start and stores it at ~/.local-agent-tools/token, with mode 0600 in a 0700 directory. The token survives restarts, and the server checks it in constant time.
The token lives in a headers field inside each generated MCP config file: .mcp.json, .cursor/mcp.json, .windsurf/mcp.json, and .vscode/mcp.json. Each of those files is written with mode 0600, and each file, plus its .backup copy, is added to the project's .gitignore. The add-on refreshes that .gitignore block every time it rewrites the config files, including on startup.
Restart Local once. On start, the add-on rewrites the MCP config file for every enabled site with the current token, so no manual step is needed.
Then restart your MCP client so it picks up the new config. If a client still gets a 401 response, open the site in Local's Agent Tools panel and click Regenerate Config.
To replace the current token:
~/.local-agent-tools/token.The add-on generates a new token on start and rewrites every enabled site's MCP config files with it.
A process running as the same user as Local can read the token file and every MCP config file that carries it. The token stops other users, other machines, and web pages from reaching the MCP server. It does not stop another process running under your own account.
Treat the MCP server as trusted-local: safe from the network and from other accounts on the machine, but not from other software running as you.
Local lets you choose where the add-on writes its project files: Site Root, WordPress Root (app/public), or wp-content. Choosing WordPress Root or wp-content puts the MCP config file, and the token inside it, in the site's web root, where Local's web server can serve it. Prefer Site Root unless you need one of the other locations.
The server only answers requests whose Host header is exactly localhost:{port} or 127.0.0.1:{port}. A hand-written MCP config must use one of those two values.
/sites/mcp is not tied to any site. You configure it once and use it from any directory, so you do not need to open a site folder first.
It serves the tools that do not need a bound site:
list_sites, create_site, and list_service_versions.site_start and friends, which take an explicit siteId.preview_list and preview_destroy address Local itself. preview_start needs a siteId here, because no site is bound to this endpoint.enable_agent_tools, disable_agent_tools, and agent_tools_status.This makes the global endpoint the way to bootstrap. Connect to it, create or find a site, and enable Agent Tools on it. enable_agent_tools returns that site's own endpoint URL for the site-scoped work.
The site-scoped tools are not served here: wp_cli, the log readers, the wp-config tools, get_site_info, and site_health_check. They need a bound site. Calling one on the global endpoint returns an error that points at the per-site endpoint.
The global endpoint uses the same bearer token and the same Host and Origin checks as the per-site endpoints. To add it to Claude Code, using the persisted port and token:
claude mcp add --scope user --transport http local-wp-global \
"http://localhost:$(cat ~/.local-agent-tools/port)/sites/mcp" \
--header "Authorization: Bearer $(cat ~/.local-agent-tools/token)"
--scope user is the part that makes it global. Without it, claude mcp add uses --scope local, which registers the server only for the directory you ran it in. Do not use --scope project for this server: a project-scoped .mcp.json is committed to the repo, and this entry carries the token.
You can also add it by hand, as a top-level mcpServers entry in ~/.claude.json. Cursor, Windsurf, and VS Code use the same shapes as the per-site config the add-on writes.
{
"mcpServers": {
"local-wp-global": {
"type": "http",
"url": "http://localhost:24842/sites/mcp",
"headers": { "Authorization": "Bearer <token from ~/.local-agent-tools/token>" }
}
}
}
claude mcp list confirms it connected.
The global endpoint puts site management and create_site behind one well-known URL. Before, they were reachable only from an enabled site's endpoint. The token still gates every request, so the trust model in What the token does not protect against applies unchanged.
create_site drives the same code path as Local's own Add Site flow, so a new site gets provisioned services and a real WordPress install:
create_site({ name: "Client Redesign", phpVersion: "8.2.29", enableAgentTools: true })
Three things to know:
site_status reports adding → provisioning → running. Poll that until it reports running. Pass wait: true to block instead, only if your client tolerates long tool calls./etc/hosts and macOS/Windows will prompt for administrator credentials. Site creation is never fully unattended.site_status includes a creationError field explaining why.Omit phpVersion, database and webServer to accept Local's own defaults, or call list_service_versions first to see what is available. Versions reported with installed: false are downloaded on demand, which makes creation considerably slower.
With enableAgentTools: true, Agent Tools is turned on for the site once it finishes provisioning — registering it with the MCP server and writing its MCP config and context files, exactly as clicking Enable in the UI does. Use agents to pick which ones (defaults to ["claude"]).
git clone <repo-url> agent-tools
cd agent-tools
npm install --legacy-peer-deps
npm run build
Copy the built add-on to Local's add-ons directory:
# macOS
cp -r . ~/Library/Application\ Support/Local/addons/agent-tools/
# Linux
cp -r . ~/.config/Local/addons/agent-tools/
# Windows (PowerShell)
Copy-Item -Recurse -Force . "$env:APPDATA\Local\addons\agent-tools"
Install production dependencies in the installed location and restart Local:
# macOS
cd ~/Library/Application\ Support/Local/addons/agent-tools/
# Linux
cd ~/.config/Local/addons/agent-tools/
# Windows (PowerShell)
cd "$env:APPDATA\Local\addons\agent-tools"
npm install --production --ignore-scripts
# Then restart Local
# Build the add-on
npm run build
# Watch for changes
npm run watch
After building, sync to the installed add-on:
# macOS
cp -R lib/* ~/Library/Application\ Support/Local/addons/agent-tools/lib/
# Linux
cp -R lib/* ~/.config/Local/addons/agent-tools/lib/
# Windows (PowerShell)
Copy-Item -Recurse -Force lib\* "$env:APPDATA\Local\addons\agent-tools\lib"
Then restart Local to pick up changes.
agent-tools/
├── src/ # Add-on source (TypeScript)
│ ├── main.ts # Main process — lifecycle hooks, IPC, MCP server startup
│ ├── renderer.tsx # Renderer process — React UI
│ ├── mcp-server.ts # HTTP MCP server — routing, session management, Streamable HTTP transport
│ ├── helpers/
│ │ ├── site-config.ts # SiteConfig type and SiteConfigRegistry
│ │ ├── paths.ts # Platform-specific binary resolution (PHP, MySQL, WP-CLI)
│ │ ├── new-site.ts # Pure helpers for create_site: nicename, domain, and path validation
│ │ └── port.ts # Stable port allocation with file persistence
│ └── tools/ # MCP tool implementations
│ ├── index.ts # Aggregates definitions (full vs global), routes handleToolCall()
│ ├── wpcli.ts # wp_cli
│ ├── logs.ts # read_error_log, read_access_log, wp_debug_toggle
│ ├── config.ts # read_wp_config, edit_wp_config
│ ├── site.ts # get_site_info, site_health_check
│ ├── environment.ts # site_start, site_stop, site_restart, site_status, list_sites, create_site, list_service_versions
│ └── agent-tools.ts # enable_agent_tools, disable_agent_tools, agent_tools_status
├── lib/ # Compiled output
├── package.json
└── tsconfig.json
macOS (darwin-arm64 and darwin-x64), Windows, and Linux.
Active: 10up is actively working on this, and we expect to continue work for the foreseeable future including keeping tested up to the most recent version of Local. Bug reports, feature requests, questions, and pull requests are welcome.
A complete listing of all notable changes to Agent Tools are documented in CHANGELOG.md.
Please read CODE_OF_CONDUCT.md for details on our code of conduct, CONTRIBUTING.md for details on the process for submitting pull requests to us, and CREDITS.md for a listing of maintainers, contributors, and libraries for Agent Tools.
A Local add-on that provides an MCP server, skills, and project context for AI-powered WordPress development. Works with Claude Code, Cursor, Windsurf, VS Code Copilot, and any MCP client.
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Localwp Agent Tools se ejecuta localmente por stdio.
Última comprobación: 2026-10-26. A Local add-on that provides an MCP server, skills, and project context for AI-powered WordPress development. Works with Claude Code, Cursor, Windsurf, VS Code Copilot, and any MCP client.
