Zevian for AI coding agents.

You need Node.js 20 or newer and a Zevian account.

1. Create an API key. In the Zevian dashboard, open Connect to your AI agent (or go to app.zevian.tech/settings/api), name the key, and choose Read or Read + write. Copy it: it is shown once. Read + write is only needed to let the agent open pull requests.
2. Add Zevian to your agent. Replace zv_live_YOUR_KEY with your key. The dashboard shows each of these with your key already filled in.

Run this in a terminal, in the project you want to work on.

claude mcp add --env ZEVIAN_API_KEY=zv_live_YOUR_KEY --transport stdio zevian -- npx -y zevian-mcp

claude mcp add --env ZEVIAN_API_KEY=zv_live_YOUR_KEY --transport stdio zevian -- cmd /c npx -y zevian-mcp

Then start Claude Code and type /fix-seo, or ask it to audit your site with Zevian.

Save this as .cursor/mcp.json in your project, or ~/.cursor/mcp.json to use it everywhere.

{
  "mcpServers": {
    "zevian": {
      "command": "npx",
      "args": [
        "-y",
        "zevian-mcp"
      ],
      "env": {
        "ZEVIAN_API_KEY": "zv_live_YOUR_KEY"
      }
    }
  }
}

Add the file to .gitignore if it is in your project, so the key is not committed. Then make sure Zevian is switched on under Customize in the sidebar.

Save this as .vscode/mcp.json in your project, or run MCP: Open User Configuration to use it everywhere.

{
  "servers": {
    "zevian": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "zevian-mcp"
      ],
      "env": {
        "ZEVIAN_API_KEY": "zv_live_YOUR_KEY"
      }
    }
  }
}

Add the file to .gitignore if it is in your project, so the key is not committed. Then start the server from the Zevian entry in the file, trust it when VS Code asks, and ask in the Chat view with an agent, so it can call Zevian's tools.

Three things to ask your agent:

1. “Audit my site with Zevian and fix the errors and warnings.” Or type /fix-seo. The agent finds your site, runs an audit, shows you what is wrong, and applies each fix in your repository.
2. “Check http://localhost:3000/pricing with Zevian before I deploy.” The agent fetches the page from your machine, Zevian lists the problems with their fixes, and the agent can apply them.
3. “Open a pull request that fixes the schema issues from that audit.” The agent shows you which issues it will fix and waits for your yes, then Zevian's GitHub App opens one pull request.

Your agent picks these itself. Each one tells the agent when to use it.

And one prompt, fix-seo (a slash command in Claude Code and similar agents), which audits the site, shows you the errors and warnings, applies each fix in the current repository, and summarizes what changed. It takes an optional domain.

check_page fetches the page from your machine, follows redirects, waits up to 15 seconds, and reads at most 2 MB of HTML. Then it sends Zevian the page's URL, status, HTML and response headers, so Zevian can analyze it. In that step:

• No cookies, ever. The request to your page carries no Cookie or Authorization header, and nothing is stored between calls.
• Credentials are removed before anything leaves your machine. The response headers Set-Cookie, Cookie, Authorization and Proxy-Authorization are dropped, and so is any header whose name contains token, secret, session or key. Zevian only reads the content type, X-Robots-Tag and Link.
• Zevian never fetches your page. It reads only what the package sends. It does not follow links in your HTML or load anything your HTML points to.
• The HTML itself is sent as served. Do not check a page that shows private data you do not want analyzed.
• Only the HTML as served is checked, so content a browser draws with JavaScript is not visible. The result says so when a page is mostly empty before JavaScript runs.

Your API key goes only to Zevian, in the Authorization header, and is never printed or logged.

Daily limits reset at 00:00 UTC. When you hit one, the message says when it resets and where to upgrade. See pricing for the plans.

• ZEVIAN_API_KEY: required. Your key, from the dashboard. Without it the server still starts, and every tool tells the agent how to create one.
• ZEVIAN_API_URL: optional. Defaults to https://app.zevian.tech. It must be https://, except for http://localhost, so your key is never sent unencrypted.

Every request carries a User-Agent of the form zevian-mcp/<version>, so Zevian can tell you when a newer version is available.

The messages come from Zevian and say what to do. The common ones:

If claude mcp add says Invalid environment variable format, the server name is directly after --env. Keep the command as shown, with --transport stdio between them: --env takes several values and would read the name as one.

On native Windows, older versions of Claude Code could not start npx without cmd /c in front of it. Current versions can, and the Windows command above works on both.