Setup and configuration

Overview

You install the plugin, create a key, and point a client that speaks the Model Context Protocol at your site. Claude Desktop, Claude Code, Codex CLI, Gemini CLI and ChatGPT can use that bridge. The policy stays in WordPress.

What you will set up: the plugin, one Read-only key, and one client. Writes stay off until you choose a wider key. See the feature guide for what is included today.

Quickstart

1. Confirm WordPress 6.4 or newer and PHP 8.0 or newer. WordPress documentation covers the site-health screen.
2. Upload the plugin zip from the latest GitHub release and activate it.
3. Open Bridgistic, then Health Check.
4. Create a Read-only key and copy the key id and secret once.
5. Connect one local client and run a site-info read. Confirm the row in Bridgistic, then Logs.

Install the plugin

Download bridgistic-wordpress-plugin.zip from Releases. In WP Admin open Plugins, Add New, Upload Plugin, then Activate. A Bridgistic menu appears. If the health score is poor, fix permalinks and HTTPS before you create a key.

The free plugin is GPL-2.0-or-later. You do not need an account to use the local bridge. Paid plans are sold by Paddle and described on How purchases work.

Create a connection key

Open Bridgistic, then AI / MCP Connections. Choose the client, choose Read-only, and create the key. Copy the key id and the secret. The secret is shown once. You can rotate or revoke the key later without changing the WordPress administrator password.

Three values go to the client: the site URL, the key id, and the key secret. Export Package can bundle a setup zip. Do not commit the secret to a public repository.

Connect an AI client

Local mode is the recommended default. Bridgistic Cloud at mcp.bridgistic.app is a public beta and has not had an independent security review.

• Claude Desktop and Claude Code: desktop and Claude Code.
• Codex CLI: Codex setup.
• Gemini CLI: Gemini setup.
• ChatGPT and other clients: ChatGPT and other MCP clients.

A local Claude Code install from the marketplace looks like this:

/plugin marketplace add Wordpressistic/bridgistic
/plugin install bridgistic@bridgistic-marketplace

After it connects, ask for site info, then open Bridgistic, then Logs. The client tabs on the homepage show the same families.

Scopes and approvals

Read-only can look. It should not publish or delete. Move to a wider preset only when a workflow needs a write. Developer Mode includes database, files and PHP tools and should stay on sites you fully control.

If the key requires approval, the write waits in Bridgistic, then Approvals, until a person allows or denies it. That queue is part of the free plugin.

Playbooks and schedules

A manual playbook runs when you start it. A schedule runs one playbook on a timer. The free plugin allows 3 enabled schedules. Unlimited schedules are still coming soon and are not turned on by a license key in this zip.

Snapshots

The plugin can snapshot before a destructive write, and you can restore. The free screen keeps up to 50 snapshots. Advanced snapshot history is not unlocked in the public plugin. Delete an old snapshot if you need a new one and you are at the cap.

Audit log

Every bridge request can be read in the log for 90 days. The log is not downloadable as an audit export yet. See audit log export. Setup export under Bridgistic, then Export Package, is a connection bundle, not the log.

Plans

Prices on bridgistic.app are the published prices. Free is $0. Lifetime is $49 once for 1 license · 1 site. Pro is $12 a month or $99 a year for 1 license · 5 sites. The refund window is 7 days, described in the refund policy. The WPistic terms also apply to paid plans.

The account dashboard is dashboard.bridgistic.app. It is not required for the local free bridge.

FAQ

More answers sit on the homepage FAQ. If Health Check fails, start there before you change a client config. Support mail is [email protected]. Issues can also go to GitHub.

Publisher