Bridgistic

Bridgistic connects an AI assistant to a WordPress site through signed, scoped-key requests with approvals, logs and snapshots.

What you can do

• Connect an assistant to a WordPress site using a public key id and secret from the site's Bridgistic admin setup.
• Work against one site, or switch between several sites through an optional connections registry file that maps aliases to site URL, key id and secret.
• Rely on the server's signed requests, scoped keys, approval step, logging and snapshots as described by the provider.
• Adjust stderr log verbosity (error, warn, info, debug) for troubleshooting.
• No individual tools are listed in the manifest, so the exact WordPress actions available are not documented here.

When to use it

Use it when you want an assistant to work with a WordPress site and prefer key-scoped, signed access with approvals and an audit trail over handing out full admin credentials. It also suits people managing several WordPress sites from one assistant session.

Requirements

Runs locally as an npm package over stdio on a desktop machine. Needs a WordPress site with the Bridgistic plugin and a key created in WP Admin, plus the required environment variables BRIDGISTIC_SITE_URL, BRIDGISTIC_KEY_ID and BRIDGISTIC_KEY_SECRET. Optionally set BRIDGISTIC_CONNECTIONS to a JSON file for multiple sites and BRIDGISTIC_LOG_LEVEL for verbosity. Network access to the site is required.