← All docs

Connect your AI assistant

Connect Claude, ChatGPT, Codex, or another MCP client using the site's instructions.

Before connecting

Install and activate Checknaut Pro, enter your licence at Checknaut → Licensing, then open Tools › AI assistant. The AI connector is part of Checknaut Pro; the free plugin has none. The connector turns on the first time a licence is activated. Which tools your assistant can use depends on your licence and your builder, and the connection test shows what is available on your site. Use the instructions your own install shows: client menus, plan eligibility and supported authentication can change. Checknaut does not provide an AI subscription.

Connect a hosted assistant

  1. Copy the connector URL from the AI assistant screen.
  2. Open your assistant's custom connector or MCP-server settings and add that URL.
  3. Select the authentication method the AI assistant screen names.
  4. Complete connection setup, then start a new chat with Checknaut enabled.
  5. Ask the assistant to read the site context and confirm the site URL before making changes.

Key in the URL or OAuth?

If the AI assistant screen says the key is included in the URL, follow its no-sign-in instructions; do not choose OAuth for that address. If the site is configured for OAuth, follow its sign-in flow. The plugin also supports token headers for clients that can configure them. Do not mix methods by guessing.

Treat a connector URL containing a key as a password. Do not put it in public docs, screenshots, tickets, repositories, or shared chats. Rotate a leaked key on the AI assistant screen and reconnect the clients that used it.

Claude, ChatGPT, and Codex

Use the plugin's client-specific setup panel. Claude and ChatGPT custom connectors depend on the account and client features available to you. Codex and other MCP clients need their own server configuration. Verify eligibility with the provider before buying Pro specifically for that workflow.

First prompt

Read the site's context and setup. Confirm the site URL, builder, current version, available tools, and safety restrictions. Then run a read-only homepage review. Do not edit anything yet.

What does the assistant receive?

It receives the content and results it requests through the tools. That information can then pass to your chosen AI provider under your agreement with that provider. Checknaut does not call an AI provider on its own.

Missing tools or failed connection

Open Tools › Diagnostics and run the connection test. Confirm the URL and authentication, client eligibility, plugin activation and builder. Check the licence when a paid tool is unavailable; the Builder Pack and Privacy Pack tools come with the licence. After updating the plugin, reconnect or refresh the client so it loads the current tool list. Tool names start with checknaut_. An assistant that still uses an old station_ or divi_ name gets an “Unknown tool” error and should refresh its tool list. Never assume a visible connector is a verified working connection.

If the licence lapses

The audit, fix, read, snapshot and rollback tools keep working, as long as the account the assistant acts as is not an Administrator. Choose an Editor under Acts as to keep using them. The Pro tools come back when you renew.

Pause or revoke

Use the plugin's pause control to stop AI connections, or rotate the token or revoke the relevant OAuth client on the AI assistant screen. Do not publish your key to make setup easier.

Need help with your install? Contact support. Related: Getting started.

Reviewed for Checknaut 2.0.0 on 31 October 2026.