ChatGPT & MCP — Site audits from chat

What you get

• Tools such as run_site_audit so ChatGPT can request a real audit for a URL you provide.
• Two supported connection styles: OAuth (sign in with your Cool Web Tool account) or API token (for hosted MCP bridges such as Smithery).
• Same product limits as the web app: on the free tier, up to three site audits per calendar month when using this MCP path (aligned with dashboard messaging).

Prerequisites (ChatGPT)

ChatGPT connects external apps through Developer mode (Settings → Apps → Developer mode). Create or install an app there, then add your MCP server and OAuth client details as described below.

Point ChatGPT's OAuth configuration at Cool Web Tool's API host. Use the production URLs below (replace only if you use a custom API domain).

After OAuth, ChatGPT can call the MCP server you configure. For our hosted streamable HTTP endpoint, use:

Some MCP hosts ask for a static token instead of per-user OAuth. Create a Cool Web Tool API token in the dashboard, then provide it to the host according to their docs (often an environment variable or connector field).

1. Open your Cool Web Tool dashboard → API / developer settings.
2. Create an API token with permission to run site audits.
3. Paste the token into the MCP connector configuration on Smithery (or your host).
4. Use the MCP URL your host displays for the Cool Web Tool package.

Token-based access still enforces your plan limits and audit quotas server-side.

• Only approve OAuth or paste tokens into official ChatGPT Developer mode flows and MCP hosts you trust.
• Our consent screen should show Cool Web Tool branding when you authorize ChatGPT.
• Site audits run against URLs you explicitly provide; review tool confirmations in ChatGPT before approving sensitive actions.

Related documentation