PubPilot AI connector
Last revised: 18th Nov 2026
The PubPilot connector lets Claude or ChatGPT read your PubPilot account and, when you confirm, change your monitoring. You ask in plain words, for example "why did this alert fire?" or "which rules does my site need?", and your AI answers from your alerts, rules and ads.txt status. Setup steps and copy-ready prompts are on PubPilot in Claude and ChatGPT. For help, see Support.
Connector address and clients
Address: https://app.pub-pilot.com/api/mcp. It is a remote MCP server over Streamable HTTP. It works with Claude (claude.ai and the Claude desktop app, as a custom connector) and with ChatGPT on the web (as a custom MCP server). You need a PubPilot account. Reading works on every plan; writing a rule needs a plan that has that kind of rule (on-page rules are on Pro and Enterprise, Google Ad Manager alerts need Ad Manager connected).
Sign-in and access
- OAuth 2.1 with dynamic client registration and PKCE (S256 only). You sign in with your PubPilot account and allow the connection.
- Access tokens last one hour. Refresh tokens last 30 days and change on every use; using an old one again ends the connection.
- Tokens and codes are stored only as one-way hashes.
- The connector acts as you: your organisation comes from your sign-in, and every read and write is limited to it. No tool can reach another organisation.
- Two scopes,
readandwrite. Viewers in your organisation get the read tools only. - To disconnect, remove PubPilot in your AI app's connector settings. To switch AI access off for a user, write to [email protected].
Tools
Twelve read tools. They change nothing.
| Tool | What it does |
|---|---|
get_account | Account, plan and limits |
list_domains | Your domains, their ads.txt status and how many rules each has |
list_alerts | Alerts, open and resolved |
get_alert | One alert, with why it fired |
list_js_rules | On-page rules |
get_js_rule | One on-page rule with its recent events |
list_gam_alerts | Google Ad Manager alerts with their latest run |
get_gam_alert | One Google Ad Manager alert with its recent runs |
get_ads_txt | ads.txt status, issues and required lines per domain |
list_ads_txt_scans | Past ads.txt scans of one domain (kept 7 days) |
list_changes | Changes made through the connector, newest first |
get_setup_guide | How to check a page and pick rules |
Ten write tools. Each one takes two calls. The first changes nothing and returns the exact change and a one-time token; your AI shows you the change and sends the second call only after your yes. The token works once, for that exact change, and expires after 10 minutes.
| Tool | What it does |
|---|---|
create_js_rule | Create an on-page rule |
update_js_rule | Change an on-page rule |
set_js_rule_active | Pause or resume an on-page rule |
delete_js_rule | Delete an on-page rule |
create_gam_alert | Create a Google Ad Manager alert |
update_gam_alert | Change a Google Ad Manager alert |
set_gam_alert_active | Pause or resume a Google Ad Manager alert |
delete_gam_alert | Delete a Google Ad Manager alert |
update_ads_txt | Change ads.txt monitoring, for example add a required line |
undo_change | Undo a change made through the connector |
Custom code in a rule is accepted only in a small read-only subset of JavaScript: no network calls, cookies, storage, loops, eval or timers. PubPilot never fetches your pages for the AI. Facts about a page come from a read-only snippet you run in your own browser's console.
Prompts
Eight named prompts. Each tells your AI which tools to call and to apply nothing until you agree.
| Tool | What it does |
|---|---|
setup_monitoring | Set up monitoring for my site |
setup_guide | How to check my page and pick rules |
explain_alert | Why did this alert fire |
weekly_health_check | Weekly health check |
audit_rules | Audit my rules |
review_rule | Review this rule |
review_gam_alerts | Check my GAM alerts |
check_ads_txt | Check my ads.txt |
Checks on a schedule
On a paid Claude plan (Pro, Max, Ultra, Team or Enterprise) you can create a scheduled task that calls the PubPilot connector, for example every weekday morning, and sends you what it finds. Scheduled tasks run in the cloud. If a PubPilot tool is set to always ask, the task may wait for your approval, so allow the read tools for unattended runs (Claude help). ChatGPT's scheduled tasks can use connected apps where your plan and workspace allow it (OpenAI help). Alerts by email, Slack and in the app keep running either way.
What data the connector reads
Only what a tool call asks for, from your own organisation: your account and plan, domains, alerts, on-page rules and their events, Google Ad Manager alerts and their runs, ads.txt status and scans, and the connector's change history. The results go to the AI app that made the call. Anthropic or OpenAI then handle them under their own terms. PubPilot does not receive your conversation with the AI, only the tool calls.
What we log
- Every tool call, with the user and organisation, the AI app that made it, the tool, a one-way hash of its parameters (never the parameters themselves), whether it worked, its size and how long it took.
- Every change made through the connector, with who made it, when, and the item before and after, so you can list it and undo it.
- A daily count of calls per user and tool.
How long we keep it
- Raw call logs: 12 months, then deleted. After that we keep only aggregate usage counts.
- The change history stays with your account, so a change can still be listed and undone.
- Write previews and their tokens: deleted a day after they expire.
- Sign-in records: deleted a day after the last token they hold expires.
We do not sell this data, and we do not use your data to train AI models. The full terms are in the privacy policy.