Connect Pingpile to your AI assistant

Pingpile is an MCP server. Connect Claude, ChatGPT or any assistant that speaks MCP, and ask it whether anything is down, what is wrong with a sitemap, or to check a site now, change an interval or add a site. It sees and changes what you can on your dashboard, for your own account only.

Server URL

https://pingpile.com/mcp

Streamable HTTP, OAuth 2.1 with dynamic client registration and PKCE. You sign in to Pingpile and approve the assistant on a consent page; nothing to install, no API key.

Claude (web and desktop)

Open Settings, then Connectors, and choose Add custom connector.
Paste the server URL above and choose Connect.
Sign in to Pingpile (with Google or a code by email) and approve Claude.

Claude Code

claude mcp add --transport http pingpile https://pingpile.com/mcp, then /mcp in Claude Code to sign in.

Other assistants

Add a remote MCP server (sometimes called a custom connector) with the server URL; the assistant opens Pingpile's sign-in and consent page.

Try asking

Is anything down?
Which of my sitemaps have problems, and what is wrong with them?
Check example.com now.
Show the broken pages in the sitemaps of example.com.
Check all my sites every 15 minutes, except the shop: every 5.
Add mycompany.com and tell me which sitemaps you found.

Every tool

Tool	What it does	Kind
Status overview `get_status`	Is anything down? Sites up and down, open incidents, sitemap problems, pages that are not indexable, the check budget, alert email settings and the connected Google accounts. Start here.	Reads
List sites `list_sites`	Every site with its state, last check, response time, uptime (24 h, 7 d, 30 d), interval, timeout and maintenance window.	Reads
Site details `get_site`	One site in full: state and settings, uptime over 24 h to 90 days, uptime per day for the last 30 days, the latest incidents, its sitemaps, and sitemap pages that failed their last check.	Reads
List sitemaps `list_sitemaps`	Sitemaps with their health: URL count and minimum, the latest fetch and its change, protocol validation, what Search Console reports, and how many of their pages failed.	Reads
Sitemap URLs `get_sitemap_urls`	The URLs in one sitemap, 100 per page, with lastmod and the result of their latest check. Filter: all, new (added in the latest fetch), broken, unchecked, removed. Also returns the count per filter.	Reads
List incidents `list_incidents`	Outages, newest first: when each started and ended and why. Optionally for one site, or open ones only.	Reads
Check a site now `check_site`	Check one site's home page now (status, response time, error pages, indexability) and report the result. At most once every 30 seconds per site.	Changes; fetches your sites or sends mail
Check a sitemap now `check_sitemap`	Fetch one sitemap now: validate it, count its URLs, compare with the previous fetch and check a sample of its pages. At most once a minute per sitemap.	Changes; fetches your sites or sends mail
Check every site now `check_all`	Check every monitored site and a sample of sitemap pages now. At most once every 5 minutes.	Changes; fetches your sites or sends mail
Sync Search Console `sync_search_console`	Pull the sites and sitemaps from Search Console again, for example right after adding a property or submitting a sitemap there. Sitemap files are fetched over the next few minutes. At most once every 5 minutes.	Changes; fetches your sites or sends mail
Add a site by its address `add_site`	Monitor a site that is not in the user's Search Console, by its address (example.com or a full URL). It is checked like any other site, on the same budget, and its sitemaps are found in its robots.txt or at /sitemap.xml. The pages its sitemaps list are only checked once the site is proven the user's, which means adding it to Google Search Console and connecting that account.	Changes; fetches your sites or sends mail
Remove a site added by its address `remove_site`	Stop monitoring a site that was added by its address (history is kept). Search Console sites can only be switched off.	Removes
Add a sitemap `add_sitemap`	Add a sitemap to a site added by its address (a Search Console site's sitemaps come from Search Console).	Changes
Change sites `update_sites`	Change one or more sites at once: monitoring on or off, check interval (minutes, or "auto" to let the budget decide), timeout, whether redirects are followed, and for one site its display name. The whole change must fit the daily check budget, or nothing changes; a change that needs no more checks always works. Switching monitoring off ends open incidents.	Changes
Set a maintenance window `set_maintenance_window`	A daily window with no checks and no alerts for one site, e.g. 01:00 to 02:00 every night, in the user's time zone. 15 minutes to 6 hours. Needs a paid unit; clearing one never does.	Changes
Change a sitemap `update_sitemap`	Change one sitemap: monitoring on or off, how often it is fetched, and the minimum URL count below which it alerts (null removes the minimum).	Changes
List workspaces `list_workspaces`	The workspaces the user is in (personal first), which one the tools act on now, the members and open invitations of the current one, and who owns it. Sites, plan and alerts belong to a workspace.	Reads
Switch workspace `switch_workspace`	Make another of the user's workspaces the current one, for these tools and the web app alike.	Changes
Create a workspace `create_workspace`	A new workspace owned by the user, for a company or client, and make it current. Its sites come from the Google accounts connected to it, which happens in the web app.	Changes
Move a Google account `move_google_account`	Move one of the user's own Google accounts from the current workspace to another of theirs, with the sites it lists. Only out of a workspace the user is alone in: in a team the others rely on its sites.	Changes; fetches your sites or sends mail
Invite to the workspace `invite_to_workspace`	Email an invitation to join the current workspace (not a personal one). The link works once, for 7 days. Removing members, handing over ownership and closing a workspace are done by the owner in the web app.	Changes; fetches your sites or sends mail
Alert emails on or off `set_alert_emails`	Whether the user gets an email when a site goes down or comes back, or a sitemap or indexing problem starts or ends.	Changes

Every tool is annotated: reads are read-only, and the one that removes something is marked destructive, so the assistant asks first. Tools that fetch your sites or send an email say so.

What an assistant cannot do

Connect or see Google accounts or their keys, buy or change paid units, see other people's workspaces, or reach anything outside your own account.

Privacy and disconnecting

An assistant gets only what its tools return, when it asks. Tokens are stored hashed. Disconnect any app under Connected apps in your Pingpile menu, at any time. More in the privacy policy and the terms.