Relvato

Relvato MCP server

Website monitoring your AI agent can run: add a site, set up and tune its monitors, run them, explain what broke and fix it with you.

Developer docs · Official MCP Registry · relvato.com

Relvato is a website monitoring platform. Its monitors cover uptime and SSL; user flows like sign-up, login, cart and checkout; security (vulnerable plugins, signs of a hack, changed files, new admins); Core Web Vitals and real-user speed; visual regressions and broken links; SEO and AI search, including your Google Search Console and Bing Webmaster Tools numbers; domain, DNS and email records; and legal compliance (cookie consent, accessibility). They run in a real browser on any website, go deepest on WordPress & WooCommerce, and run again every time the site changes.

This is Relvato's hosted Model Context Protocol server. There's nothing to install or run: point your MCP client at the URL and sign in to Relvato, or use a Relvato API key. This repository holds the connection details, the registry entry (server.json) and the Claude plugin (.claude-plugin/, skills/). The server itself runs at Relvato.

Sign in (no key needed)

Sign-in works in clients that identify themselves with a Client ID Metadata Document (CIMD): Claude (claude.ai, Desktop, and Claude Code 2.1.81 or later), ChatGPT and VS Code. Relvato doesn't offer dynamic client registration, so a client that can only register itself that way (Cursor for now, the Gemini CLI, Docker's MCP gateway), or that has no sign-in at all (DeepSeek Harness), uses an API key instead.

In a client that supports it, add the endpoint with nothing else. The first time the client uses it, it opens Relvato's sign-in:

1. Sign up (there's a free plan) or sign in.
2. Allow the client to read your sites and results and to make changes: add and configure sites and monitors, change schedules and run scans.
3. If you belong to an organization, pick which of its workspaces to connect. Your personal workspace isn't offered there, so use an API key for it.

Discovery follows the MCP authorization spec. A 401 points to /.well-known/oauth-protected-resource/api/mcp, and the authorization server is https://clerk.relvato.com (client_id_metadata_document_supported; no registration endpoint). The scopes are relvato:read, relvato:write and user:org:read.

Or use an API key

For scripts, for clients that can't sign in (no CIMD support), or for your personal workspace while you're in an organization:

1. Open API access from the account menu, or go to app.relvato.com/api-access.
2. Create a key:

• Full access lets the agent add and configure sites and monitors, run them, review results and apply the fixes runs propose.
• Read-only lets it read everything: sites, health and uptime, performance, runs, monitors, WordPress updates and activity, fix briefs and alert settings. With a read-only key the client only sees the read tools.

1. Send it as Authorization: Bearer rlv_… (or x-api-key: rlv_…). A key is shown once. Keep it out of files you commit.

Connect

Claude (claude.ai, Desktop, mobile)

Settings → Connectors → Add custom connector. Enter the URL https://app.relvato.com/api/mcp, then Connect and sign in.

Claude Code

The plugin (recommended): the server plus six skills, three for any conversation about your sites and three for working from a code repo.

claude plugin marketplace add Relvato/relvato-mcp

claude plugin install relvato@relvato

Then run /mcp, choose plugin:relvato:relvato, then Authenticate. The skills:

Already added Relvato on claude.ai? With a Claude subscription, that connector shows up in Claude Code too. The skills work with either connection.

The plugin has no code of its own: it adds Relvato's hosted MCP server (https://app.relvato.com/api/mcp) and these skills, which are written instructions for Claude. Claude sends your requests to that server only, after you sign in to Relvato. Starting runs counts toward your plan's monthly runs, so the skills ask before they start any.

Just the server:

claude mcp add --transport http relvato https://app.relvato.com/api/mcp

Then run /mcp, choose relvato, then Authenticate. With an API key instead:

claude mcp add --transport http relvato https://app.relvato.com/api/mcp --header "Authorization: Bearer rlv_your_key"

Cursor

In ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), with an API key. Cursor doesn't support Client ID Metadata Documents yet, so it can't use Relvato's sign-in:

{

"mcpServers": { "relvato": { "url": "https://app.relvato.com/api/mcp", "headers": { "Authorization": "Bearer rlv_your_key" } } } }

Once Cursor supports CIMD, the URL alone will be enough: Cursor will offer to sign in.

VS Code

In .vscode/mcp.json. VS Code offers to sign in:

{

"servers": { "relvato": { "type": "http", "url": "https://app.relvato.com/api/mcp" } } }

With an API key, VS Code can ask for it once and store it securely, so it never sits in the file:

{

"inputs": [ { "type": "promptString", "id": "relvato-key", "description": "Relvato API key (rlv_…)", "password": true } ], "servers": { "relvato": { "type": "http", "url": "https://app.relvato.com/api/mcp", "headers": { "Authorization": "Bearer ${input:relvato-key}" } } } }

Gemini CLI

Install the extension from its own repository, Relvato/relvato-gemini (it moved there in 3.5.2; if you installed it from this repository, run gemini extensions uninstall relvato first):

gemini extensions install https://github.com/Relvato/relvato-gemini

It asks for your Relvato API key (create one) and keeps it in your system keychain; it never sits in a file. To change it later: gemini extensions config relvato. The Gemini CLI can't use Relvato's sign-in (it supports only dynamic client registration, which Relvato doesn't offer), so the extension uses the key.

Without the extension, add the server to ~/.gemini/settings.json:

{

"mcpServers": { "relvato": { "httpUrl": "https://app.relvato.com/api/mcp", "headers": { "Authorization": "Bearer rlv_your_key" } } } }

DeepSeek Harness

Add the dsh-plugin-relvato bundle to a profile, with your API key in RELVATO_API_KEY (your environment or ~/.dsh/.env):

dsh plugin --profile web add dsh-plugin-relvato

It's on npm; github:Relvato/dsh-plugin-relvato installs it straight from GitHub.

dsh's MCP client sends headers and has no sign-in, so it uses the key. The tools appear as mcp__relvato__ .

Cline

In cline_mcp_settings.json (MCP Servers → Configure), with an API key:

{

"mcpServers": { "relvato": { "type": "streamableHttp", "url": "https://app.relvato.com/api/mcp", "headers": { "Authorization": "Bearer rlv_your_key" } } } }

Agents that set servers up themselves can follow llms-install.md.

Any other client

Add a remote HTTP (streamable HTTP) server with the endpoint above. If the client supports MCP sign-in with Client ID Metadata Documents (CIMD), that's all. Otherwise (including clients that only do dynamic client registration) add an Authorization: Bearer rlv_… header. In the common mcp.json format:

{

"mcpServers": { "relvato": { "type": "http", "url": "https://app.relvato.com/api/mcp", "headers": { "Authorization": "Bearer rlv_your_key" } } } }

Tools

58 tools, grouped by job in the order tools/list sends them. read tools work with any connection; full access tools need a full-access key, or a sign-in that allowed changes.

Set up

Read

| site_overview | Plain-language health verdict: what needs attention, every monitor with its latest run and schedule, plan usage and, on WordPress, the