Connect your first coding agent.

Install AI Bridge, bind one coding-agent project to one WordPress site, and finish with a verified read-only snapshot. Allow about 10 minutes for the first connection.

Download 0.2.0-beta.4 See what Bridge can do

WordPress6.8–7.1

PHP8.0+

MCP package0.2.0-beta.5

Next action: download the release ZIP.Do not install the repository source or an older artifact when testing this beta.

Install the plugin in four steps.

LiveCanvas must already be active. Picostrap and Picowind/WindPress are detected automatically when present.

Download the release ZIP.
Open the GitHub release above and download livecanvas-forge-ai.zip.
Upload it in WordPress.
Open Plugins → Add New Plugin → Upload Plugin, select the ZIP, then choose Install Now.
Activate AI Bridge.
After activation, open LiveCanvas → AI Bridge.
Confirm the project.
Check the detected theme and framework. Choose Configure and build this site only when the agent should be allowed to write; leave it off for inspection.

AI Bridge project setup ready screen showing the detected framework, local site and coding agent — WordPress confirms the site context before the connection wizard opens.

Connect one project to one site.

Open the folder you actually use in the coding agent. That folder can contain WordPress, or WordPress can live deeper inside it at a path such as app/public.

Direct Mode

Recommended for normal WordPress work. Public HTTPS Codex projects can use OAuth; other environments use secure site-bound pairing.

Local runtime

Use when the agent must read theme files, compile Picostrap or WindPress assets, discover local media, or run local visual checks.

Cursor Qualified

AI Bridge writes or merges one server into the current Cursor workspace. Existing MCP servers remain intact.

Project file.cursor/mcp.json

Reload actionCustomize → MCPs → Reload

Open the correct project folder in Cursor.
Generate the Cursor setup in WordPress and install it directly when the folder is writable.
Open Customize → MCPs, enable livecanvas-forge, then choose Reload.
Ask Cursor to call get_connection_handoff.

OpenCode Qualified

Use the generated project configuration and keep it outside the public WordPress web root whenever the workspace contains a nested WordPress install.

Project fileopencode.json

Diagnosticopencode mcp list

Open the project root in OpenCode.
Run the setup command copied from WordPress, or download and merge opencode.json.
Confirm that opencode mcp list shows one livecanvas-forge server.
Call get_connection_handoff and approve the matching pairing in WordPress.

Claude Desktop Qualified · Free

The Free desktop client passed handoff, snapshot, preview, write and rollback testing. Merge the generated server without replacing unrelated preferences.

macOS config~/Library/Application Support/Claude/claude_desktop_config.json

RestartQuit and reopen Claude Desktop

Choose Claude → Desktop App in AI Bridge.
Use direct install when offered, or merge only mcpServers.livecanvas-forge.
Quit Claude Desktop completely, then reopen it.
Call get_connection_handoff and approve the matching pairing.

Claude Code Setup preview

AI Bridge generates the project-scoped command. This beta has not yet completed a full authenticated Claude Code qualification run.

Install commandclaude mcp add --scope project …

Current evidenceConfiguration and preview only

Choose Claude → Command Line Interface in AI Bridge.
Open a terminal in the correct project and run the exact generated command.
Confirm that claude mcp list shows livecanvas-forge.
Do not treat this client as fully qualified until an authenticated handoff and rollback test pass.

Configuration anatomy: AI Bridge generates this structure for local Cursor projects. The paths below are illustrative. Use the generated file for your site instead of copying this example.

Example · no static secret

{
  "mcpServers": {
    "livecanvas-forge": {
      "command": "node",
      "args": [
        "/project/app/public/wp-content/plugins/livecanvas-forge-ai/mcp/bin/livecanvas-forge-mcp.js",
        "--transport=stdio"
      ],
      "env": {
        "LCFA_AGENT": "cursor",
        "LCFA_AGENT_WORKSPACE_ROOT": "/project",
        "LCFA_WP_ROOT": "/project/app/public"
      }
    }
  }
}

Ready means the connection was proven.

Writing a config file is not enough. AI Bridge waits for the agent handoff and a passing WordPress smoke test.

Ask the agent for the handoff.
Call get_connection_handoff. Stop if the reported site URL or fingerprint is wrong.
Approve the matching request.
Return to WordPress only when AI Bridge shows a matching client and project label.
Run the smoke test.
AI Bridge checks REST reachability, the local MCP runtime when applicable, and the detected MCP package version.
Continue only at Ready.
The Connections screen must show the correct agent, connection mode and verified package.

AI Bridge connection checks showing successful REST, MCP runtime and Cursor handoff results — A real local Cursor qualification run: three successful checks and the expected MCP package.

01Inspect

02Preview

03Apply

04Roll back

Before the first write: verify the site URL and fingerprint, review the preview, keep the audit ID, and confirm that the requested write scope is enabled.

Start with a prompt that has a stopping point.

These prompts tell the agent what to inspect, what it may change, and when it must wait for you.

1. Verify the connection

Call get_connection_handoff, then get_snapshot. Report the site URL, fingerprint, active theme, framework, connection mode, scopes and MCP package version. Do not modify anything. Stop if the site identity or package version does not match the current project.

2. Build a matching Contact page

Inspect the homepage, global header, footer and design-system context. Create a Contact page that matches the existing visual language and remains editable in LiveCanvas. Include contact details, a concise form area and a clear next action. Preview the complete page first. Do not apply until I approve the preview.

3. Install a starter theme safely

Inspect the current theme and Theme Library compatibility. Preview the selected starter theme installation and starter-data import. Confirm the framework, child-theme name, homepage, header, footer and WindPress or Sass build requirements. Stop before apply and show the rollback plan.

4. Make a reversible update

Inspect the target page and identify the smallest safe change. Create a preview and summarize the exact objects or files that would change. Apply only after I approve. Return the audit ID, changed targets and rollback command with the final result.

The agent cannot see livecanvas-forge

Open the same project where AI Bridge installed the config. Trust that folder, enable the MCP server, and reload the MCP process. In Cursor, use Customize → MCPs → livecanvas-forge → Reload.

The handoff reports the wrong site

Stop without writing. Revoke the stale session in WordPress, remove only that site’s livecanvas-forge config entry, then generate a new setup from the correct site.

Reads work but writes are missing

Return to Setup, choose Configure and build this site, save, regenerate the agent setup, revoke the old session and pair again. The old read-only session cannot inherit new write scopes.

The MCP package version does not match

Update the plugin, reload or restart the coding agent’s MCP server, call get_connection_handoff again, then rerun the WordPress smoke test.