Zevian MCP server

Read from the package source without running it. The installed server may list more.

• check_page

  Call this to check one page's SEO, including pages Zevian cannot reach: localhost, staging, or anything not yet published. The page is fetched from this machine (cookies and credentials are never sent, and sensitive response headers are removed before anything goes to Zevian), then analyzed. Returns the page's issues, each with its fix. It reads the HTML as served, so content a browser draws with

• get_audit

  Call this to read an audit started with run_audit: its status, scores and counts, and its issues worst first, each with an issue_id for get_fix. Filter by severity (error, warning, info) or category (seo, geo, aeo, schema). Lists up to 25 issues by default and 100 at most, with the total. If the audit is still running it says so: call it again in a minute.

• get_fix

  Call this to get instructions for fixing one issue (an issue_id from get_audit or check_page): the kind of change, which files to look in, the exact target values and limits, and why. Apply it in the user's own repository: search for the current value before you edit, and follow the constraints. It returns instructions, not a diff. If the user would rather have Zevian make the change, use open_fix

• get_fix_pr

  Call this to check a pull request started with open_fix_pr, when open_fix_pr returned a pr_id instead of a url: its status (queued, running, open, failed), its url once open, and the reason if it failed.

• get_impact

  Call this to see how a site performs in Search Console and Bing over the last N days (7 to 180, default 28), and the before and after of each merged Zevian pull request: clicks, impressions and position, where a positive position_gain means the page moved up. Needs a site_id from list_sites. Paid plans only.

• list_sites

  Call this first, to get the site_id the other tools need. Lists the sites connected to this Zevian account with each site's SEO and AI scores, open issue count, connected GitHub repository, and whether the plan has paused it.

• open_fix_pr

  Opens one pull request on the user's connected GitHub repository that fixes 1 to 20 issues from the same site, using Zevian's GitHub App. This changes their repository: ask the user to confirm before you call it, and tell them which issues it will fix. It needs a key with write access, and counts against the monthly pull request allowance. Waits up to about 45 seconds; if the pull request is not o

• run_auditwrite action

  Call this to audit a connected site, or one page of it, with Zevian's crawler. Needs a site_id from list_sites. For localhost, staging or any page that is not published on the site's domain, use check_page instead. Waits up to about 45 seconds for the result; if the audit is still running it returns an audit_id, and you should call get_audit with it in a minute. It crawls the site but changes noth

• Code scan11 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Zevian: common questions

Is Zevian MCP server safe?

With care: it is graded C, so read the findings first (58/100). Read the Zevian safety report

How do I install Zevian?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Zevian need an API key?

Yes. The registry entry asks for ZEVIAN_API_KEY.

Is Zevian maintained?

The latest release is v0.1.0.

What can I use instead of Zevian?

Servers from other publishers that do the same job: Crawlie MCP server, pseolint MCP server and Librecrawl — Technical SEO Audit MCP Server. Compare all Zevian alternatives.