MCP Server
Connect an AI assistant to your WebPixie account with the Model Context Protocol (MCP) to ask about and manage your sites and uptime monitors.
WebPixie has an MCP server. MCP (Model Context Protocol) is a standard way for an AI assistant to connect to other tools. Once an assistant is connected, it can read your monitoring data and, if you allow it, make changes in your workspaces.
MCP access is available on every plan, including Free.
What an Assistant Can Do
An assistant works with the same areas you see in the dashboard. It can read:
- uptime monitors: status, check history, and uptime summaries
- sites: details and which checks are turned on
- SSL certificates: details, expiry dates, and the certificates seen for a domain
- domain and DNS: registration and expiry details and DNS records
- links and sitemaps: crawled links with their status, and the pages listed in your sitemap
- incidents: open and past incidents and the check details behind them
- analysis findings, by area
With read and write access, it can also create, update, pause, resume, or delete uptime monitors, add, update, or remove sites, and add notes to incidents.
Account, billing, and team management stay in the WebPixie dashboard and are not available to assistants.
AI assistants can make mistakes. Check important changes before relying on them.
How It Works
- Add the server address to an AI platform or tool such as Claude, ChatGPT, Codex, or VS Code. See Connect Your Assistant for step-by-step guides.
- Sign in with your WebPixie account.
- On the consent screen, choose the workspaces the assistant can reach and whether it gets read-only or read and write access for each one. See Access and Permissions.
- Ask. See Using MCP for example prompts.
Learn More
Read more about the MCP server on the WebPixie website.