WindCodex Forge – Read-Only AI Diagnostics

Yes. This plugin has no code-execution capability and no tool that can change your site's content, settings, users, plugins, theme, files, or database tables.

No. This plugin only exposes read-only tools – database reads, file reads, and read-only content-block inspection. There is no write or code-execution capability anywhere in the codebase. The one exception is the memory tools, which save and delete notes in the plugin's own table.

OAuth only. Most platforms register themselves automatically via the discovery URLs shown on the Connection tab. If auto-registration fails, paste the Client ID/Secret from that same tab into the platform's Advanced/OAuth settings instead. The Connection tab lists every app that's ever connected, who it's currently acting as, and lets you revoke any one of them individually.

Only Administrators, by default. Anyone else who reaches the consent screen is told their account isn't allowed to connect. To let Editors connect too, change Settings > WindCodex Forge > General > Who can connect. Even then, the file and database tools still require an Administrator.

No. There's no license key and no account, and nothing is sent to WindCodex. It talks to the AI platform you connect, over the OAuth connector you set up yourself. The one exception is the screenshot tool (wp_take_screenshot), which asks a public WordPress.com screenshot service to render a page, so that page's URL is sent to that service and the page must be publicly reachable. You can switch that tool off on the Tools tab.

Rows from any table in your WordPress database, plus schema introspection (table listing and column structure). The AI never sends SQL: it names a table, the columns it wants, and simple conditions (e.g. option_name LIKE 'woocommerce_%'), and the plugin builds the query itself – table and column names are checked against your actual schema, and every value is passed through $wpdb->prepare(). It can only ever produce a single SELECT on one table, so it cannot change data, read files, or write to disk. Login credentials are never returned: requests that name password hashes, password-reset keys, session tokens, or application passwords are refused, and any value that looks like a password hash – or an option/meta value whose name looks like a password, secret, API key, or token – is replaced with [redacted].

Those of the WordPress user who logged in and approved the connection on the consent screen – there is no shared or fallback account. If that user later loses the role allowed to connect, or is deleted, the connection stops working immediately. Every tool call is recorded on the Activity tab with its arguments and whether it succeeded, and you can revoke any connected app from the Connection tab at any time.

wp_remember, wp_list_memories, and wp_forget let one AI conversation save a fact or preference about the site so a completely separate, future conversation can pick it up automatically – useful for naming conventions, past decisions, or site-specific quirks. It's plaintext and capped at 200 entries per site, not intended for secrets.

Any platform that supports the Model Context Protocol (MCP) as a client, including Claude and ChatGPT. Connection uses standard OAuth, so most platforms auto-register themselves from the discovery URLs on the Connection tab.

The File read tool is scoped to wp-content (themes, plugins, uploads) only – it cannot read files outside of that directory, such as wp-config.php or core WordPress files.