Server URL
Use this remote MCP server URL:app.sitepulse.dev with your installation hostname.
What MCP can do
The SitePulse MCP server can:- List your teams and discover
team_idvalues - List and inspect monitored sites
- Read latest checks and detailed check results
- Read active and historical issues
- Read uptime and performance reports
- Queue a manual check for an enabled tool
Start with
sitepulse.list_teams. Most other tools need a team_id, site_uuid, check_uuid, or issue_uuid returned by another MCP call.Connect a client
Open Settings -> MCP in the SitePulse dashboard. The page shows install options and ready-to-copy config for each supported client.Cursor
Cursor
Copy the generated
mcp.json from Settings -> MCP.In Cursor, open Settings -> Tools & MCP, then add a custom MCP server and paste the config. Cursor uses mcp-remote, so Node.js must be available on your machine.VS Code
VS Code
Click Add to VS Code from Settings -> MCP, or copy the generated
mcp.json if you prefer manual setup.This requires a VS Code MCP extension that supports remote MCP servers.Claude
Claude
In Claude Desktop or claude.ai, add a custom connector and paste the SitePulse MCP server URL.Claude Desktop can also use the generated
claude_desktop_config.json snippet with mcp-remote.Codex
Codex
Run:Complete the browser OAuth flow, then start a new Codex thread so the tools are loaded.
Other MCP clients
Other MCP clients
Use the server URL if your client supports remote HTTP MCP servers with OAuth.If the client reads
mcp.json, copy the generic config from Settings -> MCP.Authentication
OAuth is the preferred connection method. When your MCP client starts sign-in, SitePulse asks you to authorize the client in your browser. The MCP connection acts as your SitePulse user. Team membership, role permissions, email verification, and active subscription access still apply.Token fallback
Some MCP clients do not support OAuth reliably. For those clients, create a token config from Settings -> MCP.MCP token scopes
MCP token fallback grants these scopes:| Scope | Description |
|---|---|
teams:read | Read teams and team summaries |
sites:read | Read sites, monitoring settings, and reports |
checks:read | Read check runs and results |
issues:read | Read issues |
checks:run | Queue manual check runs |
Tools
| Tool | Description |
|---|---|
sitepulse.list_teams | Lists teams you can access. Call this first. |
sitepulse.list_sites | Lists sites for a team with latest-check summaries. |
sitepulse.get_site | Gets one site with monitoring settings, latest checks, and active issues. |
sitepulse.list_checks | Lists recent checks for a site. |
sitepulse.get_check | Gets one normalized check result. |
sitepulse.list_issues | Lists active or historical issues. |
sitepulse.get_issue | Gets issue detail with related site and check context. |
sitepulse.run_check | Queues one manual check for a site. |
sitepulse.get_uptime_report | Gets uptime report data for today, 30 days, or 90 days. |
sitepulse.get_performance_report | Gets performance report data for today, 30 days, or 90 days. |
sitepulse.run_check only works for tools enabled on the site. It also respects plan limits, manual-check quotas, and rate limits.Resources and prompts
The server also exposes resources for team summaries, site summaries, latest site checks, issue details, and check-tool docs. Prompt templates help AI clients analyze site health, triage team issues, explain check failures, and recommend monitoring settings.Troubleshooting
Tools do not appear
Tools do not appear
Restart your MCP client after adding SitePulse. Some clients only load tools when a new window, chat, or thread starts.
OAuth fails
OAuth fails
Try the token fallback from Settings -> MCP. Cursor, Claude Desktop, and similar desktop clients can usually connect through
mcp-remote.Permission errors
Permission errors
Confirm that your SitePulse account belongs to the team, your email is verified, your team has active plan access, and your role can view or run the requested item.