30 days free. No credit card. Full access from the moment you connect your site.

Start free trial

Connect Cline to WordPress

Connect Cline to WordPress — AcrossAI setup guide

Connect Cline — the open-source autonomous coding agent for VS Code — to your own WordPress site over the Model Context Protocol. Cline talks to your site directly — there is no relay in between, no account to create, and your credentials never leave your machine. Setup takes about a minute once MCP Manager is installed.

Free plugin · No account · Runs on your own server · Any WordPress host

Config file

cline_mcp_settings.json

Top-level key

mcpServers

Where to edit it

Cline sidebar → MCP Servers

Before you start

You need AcrossAI MCP Manager installed and active on the WordPress site you want Cline to reach, plus an administrator account on that site. If you have not installed it yet, follow the Get Started guide first — it takes about a minute, and the MCP server ships bundled with the plugin.

On the editor side you need VS Code with the Cline extension installed, and Node.js on the same machine, because the connection runs through an npx bridge. Nothing is installed permanently — npx fetches the bridge on demand.

How to connect Cline to WordPress

Step 1

Open Quick Connect and copy the config

In wp-admin go to AcrossAI → MCP, open the server you want to expose, and start Quick Connect. Pick Cline, or any client that uses the mcpServers format — the JSON is identical. Everything below is generated for you with your real site URL and username already filled in; the snippets here are only so you know what to expect.

Step 2

Generate an Application Password

Click Generate password in the wizard. This creates a standard WordPress Application Password — not your login password — scoped to this connection and revocable at any time from your user profile.

The password is shown once, at creation. Copy it whole, including the spaces — WordPress accepts them. If you lose it, generate a new one rather than trying to recover it.

Step 3

Open cline_mcp_settings.json from the Cline sidebar

You do not normally hunt for this file on disk. In VS Code, open the Cline sidebar, go to MCP Servers, and choose Configure MCP Servers. Cline opens cline_mcp_settings.json in an editor tab for you — that is the intended route, and it is why the file’s location inside VS Code’s extension storage rarely matters.

Paste the entry from Quick Connect under the mcpServers key and save. If you already have other MCP servers configured, add this one alongside them rather than replacing the file. The generated config looks like this, with your own values in place of the placeholders:

{
  "mcpServers": {
    "your-site-mcp-adapter-default-server": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
      "env": {
        "WP_API_URL": "https://example.com/wp-json/acrossai/mcp",
        "WP_API_USERNAME": "your-wp-username",
        "WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
      }
    }
  }
}

Working against a local development site with a self-signed certificate? Add "NODE_TLS_REJECT_UNAUTHORIZED": "0" to the env block. Never do this for a production site.

Step 4

Refresh the server list and check the tools

Save the file, then go back to MCP Servers in the Cline sidebar and refresh the list. Your site should appear with a green status and a count of the tools it exposes. Ask Cline something harmless to confirm it is live — “Which plugins on this site need updating?” is a good first test.

What Cline can do once it is connected

With Abilities Manager installed alongside it, Cline reaches 350+ abilities across 14 toolsets — rising past 800 once it detects the plugins you already run. From inside VS Code, without switching to a browser tab, it can:

  • Read and edit content — posts, pages and any custom post type with their meta and revisions, and surgically edit a page’s block tree without rewriting the page.
  • Debug a broken site — read the debug log with secrets redacted, check Site Health, list recent fatal errors and un-pause what WordPress auto-disabled.
  • Inspect the database — schema and table sizes, index health, bloated autoloaded options, or EXPLAIN on a slow query.
  • Manage plugins, themes and core — search WordPress.org, install, update, roll back, and verify files against official checksums.
  • Work with files — inside an allowlist you define, with a dangerous-extension blocklist and optional pre-image backups of everything it touches.
  • Reach the plugins you already run — WooCommerce, Elementor, ACF, Rank Math, Yoast, WPCode and more, each registering only when that plugin is active.

Every ability runs WordPress’s own capability check for the calling user, so Cline can never do anything your account could not already do. See the full platform overview for the complete catalogue.

Frequently asked questions

Is connecting Cline to WordPress free?

Yes. AcrossAI MCP Manager and Abilities Manager are both free and GPL on WordPress.org, and there is no AcrossAI account to create. Cline is open source and brings its own model provider — AcrossAI never charges for AI inference, because none of it runs here.

Does my site data pass through AcrossAI servers?

No. Cline connects straight to your own domain and every request terminates at your /wp-json/ route. There is no relay, no gateway and no telemetry. Whatever Cline reads is still processed by the model provider you have configured in Cline, so treat it as you would any other prompt.

Does it work on any WordPress host?

Yes, provided you can reach wp-admin. Shared hosting, VPS and managed WordPress all work, because everything runs inside your own install. MCP Manager needs WordPress 7.0 or later and PHP 8.1 or later; Abilities Manager needs WordPress 6.9 or later.

Can Cline break my site?

Every ability runs WordPress’s own capability check for the calling user, so Cline can never exceed what your account can already do. Higher-risk operations refuse to run without an explicit confirmation flag, file access is confined to an allowlist you define, and any ability can be disallowed site-wide. Cline’s own auto-approve list is worth reviewing too: leave WordPress tools on manual approval until you trust the flow.

How do I disconnect Cline again?

Revoke the Application Password from your WordPress user profile, or delete the entry from cline_mcp_settings.json and refresh the MCP Servers list. Access is re-checked on every request, so revoking takes effect immediately even if the config is still on the machine.

Troubleshooting

Your edits to the file do nothing

Cline reads cline_mcp_settings.json when it loads its server list, not continuously. Save the file, then open MCP Servers in the Cline sidebar and refresh the list — that is what re-reads the config and restarts the bridge. If the entry still does not appear, reload the VS Code window. Editing the file in a plain text editor outside VS Code is the usual reason people think nothing happened.

You edited VS Code’s mcp.json by mistake

VS Code has its own MCP support, configured in .vscode/mcp.json (or the user-level equivalent) under a servers key. Cline does not read that file — it has its own, cline_mcp_settings.json, under mcpServers. The two look similar enough that it is easy to paste into the wrong one and see no change in Cline. Always reach the file through Cline sidebar → MCP Servers → Configure MCP Servers, which opens the right one.

The server appears but has no tools

That is the connection working and the catalogue being empty. Either Abilities Manager is not installed — MCP Manager will serve an empty catalogue quite happily — or the abilities exist but are not exposed to this particular server. Open AcrossAI → MCP, select the server, and check its Tools and Abilities tabs. After changing what a server exposes, refresh the MCP Servers list in Cline: MCP clients receive their tool list once, at connection time.

Authentication fails

Application Passwords are shown once and are not your login password. Generate a fresh one from Quick Connect rather than retyping an old one, and copy it complete with spaces. If the request is being refused rather than failing, check the server’s access rules — a new server requires manage_options until you add a rule, and the gate fails closed. Access is also re-checked on every request, so a role change takes effect straight away.

npx is not found

The bridge runs through npx, which ships with Node.js. Install Node.js on the machine running VS Code and reload the window. If Node is installed through a version manager such as nvm, VS Code may not inherit your shell’s PATH — in that case point command at the absolute path to npx. Launching VS Code from the terminal with code . rather than from the dock is the other common fix.

Connect a different AI client

The same server works with every MCP client — only the config file and top-level key change. See the guides for Cursor, VS Code, Claude Desktop, Claude Code, GitHub Copilot, Windsurf, Zed, Codex and every other client.

Not installed yet?

Install MCP Manager on your site, then come back and run Quick Connect.


Keep reading