Relvato

What Relvato MCP server does

Relvato MCP server exposes Relvato's hosted monitoring service to MCP-compatible clients. Relvato runs checks in a real browser against websites, including sign-ups, logins, checkout, payments, page speed, search visibility, and security. The service works with any website, while WordPress and WooCommerce sites support deeper setup and maintenance workflows.

Agents can create or verify sites, choose monitoring goals, add checks, and adjust schedules. They can also read current and historical health, performance data, monitor configuration, run details, visual comparisons, notifications, status-page settings, and heartbeat activity. Some tools can change monitoring or follow proposed WordPress updates, so access level matters.

How it works

The repository does not contain the monitoring service itself. It provides connection details, the MCP registry entry, and client-specific assets such as the Claude Code plugin and Gemini CLI extension. The hosted endpoint is https://app.relvato.com/api/mcp, using stateless JSON-RPC over streamable HTTP.

Authentication is handled either through Relvato sign-in or an API key. Sign-in uses OAuth 2.1 and is available in clients that support Client ID Metadata Documents. API keys use an Authorization: Bearer rlv_... header or the equivalent x-api-key header. Read-only keys expose read tools; full-access keys can also add and configure sites and monitors, run scans, and apply fixes proposed by runs.

Setup and configuration

Add the hosted HTTP endpoint to the MCP client rather than installing a local server. Claude, VS Code, and Claude Code can use the sign-in flow described in the project documentation. Cursor, Gemini CLI, Cline, and DeepSeek Harness use an API key; Gemini CLI also provides an extension, and Claude Code provides an optional plugin with setup, post-deploy checking, and failure-fixing skills.

After connecting, the agent can add a website. The setup step depends on the site: WordPress sites require the Relvato plugin connection, while other sites require domain verification through a DNS record or meta tag. WooCommerce sites can be recalibrated when product, checkout, or currency details change. API keys are shown once and should not be committed to project files.

Tools and capabilities

The exposed tools cover several operational areas:

• Site onboarding, verification, monitoring goals, check selection, recommendations, and WooCommerce calibration.
• Health summaries, pass rates, trends, uptime incidents, Core Web Vitals, monitor details, runs, findings, image comparisons, and fix briefs.
• Monitor schedules, visual-monitor pages and masks, check-specific settings, group pauses, resumptions, and post-update reruns.
• WordPress update windows, safe updates, quarantine sessions, activity logs, notifications, site settings, alert routing, status-page settings, and heartbeats.

The get_fix_prompt tool supplies a run's troubleshooting brief, while get_run reports findings, proposed fixes, visual comparisons, and plugins that may be updated. Tools that modify sites or monitoring require full access or an authorized sign-in with write permissions.

Limitations and notes

Relvato MCP server is hosted, so the repository is not a self-hosted monitoring implementation. A client must support remote streamable HTTP and either Relvato's sign-in method or API-key headers. Clients without Client ID Metadata Document support cannot use the sign-in flow and need an API key.

Read-only credentials cannot make changes. Some information is intentionally withheld by tools: site settings do not expose secret values, alert settings omit URLs and secrets, and status-page settings do not return private links or recipient addresses. Monitoring runs consume the account's monthly quota, and plan limits determine which checks can be added or resumed.