# Install Rivelant

Rivelant is an SEO and AI visibility platform. This page tells an AI agent how to connect Rivelant’s MCP server, so it can read the user’s site audits, rankings, Search Console data and AI answers, and start improving their site.

The user sent you here. Follow the steps in order, do what you can yourself, and ask the user only for what needs them (approving sign-in, restarting an app).

- Server: https://app.rivelant.com/mcp (remote, streamable HTTP)
- Sign-in: OAuth in the browser. API key as a fallback.
- This page: https://rivelant.com/install.md · updated 2026-11-13
- For people: https://rivelant.com/integrations

**Shorter page for your agent** (same steps, only yours): [Claude](https://rivelant.com/install/claude.md) · [Codex & ChatGPT](https://rivelant.com/install/codex.md) · [Cursor](https://rivelant.com/install/cursor.md) · [GitHub Copilot](https://rivelant.com/install/github-copilot.md) · [Gemini CLI](https://rivelant.com/install/gemini-cli.md) · [OpenClaw](https://rivelant.com/install/openclaw.md) · [Hermes](https://rivelant.com/install/hermes.md) · [Grok](https://rivelant.com/install/grok.md). If yours is listed, read that page instead and stop reading this one.

## Rules

- Add exactly one MCP server, named `rivelant`. Change nothing else, and keep the user’s other servers as they are.
- If a `rivelant` server already exists, check it and fix it instead of adding a second one.
- Never ask for an API key in the chat, never print one, and never write one into a repository. Keys go in an environment variable or the client’s secret settings.
- Do not create projects or run paid research until the connection is verified (step 3).
- Rivelant tools say when they use credits. Ask the user before a batch over 2,000 credits. Rivelant cannot buy credits; do not try.
- Reply in the user’s language.

## 1. Connect

Find your agent below and follow its steps.

Not listed? Any client that supports remote MCP servers works: add https://app.rivelant.com/mcp as a streamable HTTP server named `rivelant`, using your client’s own command or config. Check its `--help` or documentation first rather than guessing flags.

### Claude Code

1. **Add the server.** Add --scope user to use it in every project.

```
claude mcp add --transport http rivelant https://app.rivelant.com/mcp
```

2. **Sign in.** Run /mcp in Claude Code, pick rivelant and approve access in your browser.

```
/mcp
```

3. **No browser sign-in? Use an API key.** Create a key in Rivelant’s settings, keep it in an environment variable and pass it as a header.

```
claude mcp add --transport http rivelant https://app.rivelant.com/mcp \
  --header "Authorization: Bearer $RIVELANT_API_KEY"
```

- **Load the tools:** Claude Code loads new MCP servers when a session starts. If the rivelant tools are not available yet, ask the user to run /mcp and pick rivelant (this also signs in), or to restart Claude Code.
- **Check it is there:** `claude mcp list` shows rivelant as connected or as needing authentication.
- **Claude Code documentation:** https://code.claude.com/docs/en/mcp

### Codex

1. **Add the server.**

```
codex mcp add rivelant --url https://app.rivelant.com/mcp
```

2. **Sign in.** Approve access in your browser. Add --no-browser on a remote machine.

```
codex mcp login rivelant
```

3. **Or edit config.toml.** In ~/.codex/config.toml. With an API key, keep it in RIVELANT_API_KEY and add the bearer_token_env_var line.

```
[mcp_servers.rivelant]
url = "https://app.rivelant.com/mcp"
# bearer_token_env_var = "RIVELANT_API_KEY"
```

- **Load the tools:** Codex loads MCP servers when a session starts. If the rivelant tools are not available yet, ask the user to start a new Codex session.
- **Check it is there:** `codex mcp list` shows rivelant; in the terminal UI, /mcp lists its tools.
- **Codex documentation:** https://developers.openai.com/codex/mcp

### Cursor

1. **Add the server to mcp.json.** Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json for this one.

```
{
  "mcpServers": {
    "rivelant": { "url": "https://app.rivelant.com/mcp" }
  }
}
```

2. **Sign in.** Cursor supports Rivelant’s browser sign-in: when it asks, approve access. If it connects without asking, use an API key instead.

3. **No browser sign-in? Use an API key.** Keep the key in RIVELANT_API_KEY and add a header to the same entry.

```
"rivelant": {
  "url": "https://app.rivelant.com/mcp",
  "headers": { "Authorization": "Bearer ${env:RIVELANT_API_KEY}" }
}
```

- **Load the tools:** Cursor reads mcp.json changes on its own. If the tools do not appear, ask the user to switch rivelant off and on in Cursor’s MCP settings.
- **Check it is there:** rivelant is listed and enabled in Cursor’s MCP settings; connection errors appear under Output › MCP Logs.
- **Cursor documentation:** https://cursor.com/docs/context/mcp

### GitHub Copilot

1. **Add the server.** From a terminal, or run “MCP: Add Server” from the Command Palette.

```
code --add-mcp '{"name":"rivelant","type":"http","url":"https://app.rivelant.com/mcp"}'
```

2. **Sign in.** VS Code opens your browser to approve access the first time Copilot connects.

3. **Check it.** Run “MCP: List Servers” from the Command Palette and look for rivelant.

- **Load the tools:** Ask the user to start or restart rivelant from “MCP: List Servers” in the Command Palette.
- **Check it is there:** “MCP: List Servers” shows rivelant as running.
- **GitHub Copilot documentation:** https://code.visualstudio.com/docs/agents/reference/mcp-configuration

### Gemini CLI

1. **Gemini CLI: add the server.** Use --transport http; without it Gemini CLI expects a local server.

```
gemini mcp add --transport http rivelant https://app.rivelant.com/mcp
```

2. **Gemini CLI: sign in.**

```
/mcp auth rivelant
```

3. **Antigravity CLI: add it to mcp_config.json.** Then open /mcp to sign in and check the connection.

```
{
  "mcpServers": {
    "rivelant": { "serverUrl": "https://app.rivelant.com/mcp" }
  }
}
```

- **Load the tools:** If the tools are not listed, ask the user to restart Gemini CLI. In Antigravity CLI, open /mcp to install, sign in and reload.
- **Check it is there:** `gemini mcp list` (or /mcp list) shows rivelant; in Antigravity, /mcp shows its status.
- **Gemini CLI documentation:** https://geminicli.com/docs/tools/mcp-server/

### OpenClaw

1. **Add the server.** Set the transport; without it OpenClaw assumes an older connection type.

```
openclaw mcp add rivelant --url https://app.rivelant.com/mcp --transport streamable-http
```

2. **Sign in.** Set the server’s auth to oauth, then sign in while the gateway is stopped.

```
openclaw mcp set rivelant '{"url":"https://app.rivelant.com/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw gateway stop
openclaw mcp login rivelant
openclaw gateway start
```

3. **Check it.**

```
openclaw mcp doctor rivelant --probe
```

- **Load the tools:** Run `openclaw mcp reload`. A gateway running on another host needs its own reload or restart.
- **Check it is there:** `openclaw mcp doctor rivelant --probe` reports the server as reachable.
- **OpenClaw documentation:** https://docs.openclaw.ai/tools/mcp

### Hermes

1. **Add Rivelant to config.yaml.**

```
mcp_servers:
  rivelant:
    url: "https://app.rivelant.com/mcp"
    auth: oauth
```

2. **Sign in.** Hermes opens your browser on first connect. On a server without a browser, add --flow device.

```
hermes mcp login rivelant
```

3. **Reload and check.**

```
/reload-mcp
hermes mcp test rivelant
```

- **Load the tools:** Run /reload-mcp. A running gateway also picks up config changes within about a minute.
- **Check it is there:** `hermes mcp test rivelant` connects and lists the tools.
- **Hermes documentation:** https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp

### Grok Build

1. **Add the server.**

```
grok mcp add --transport http rivelant https://app.rivelant.com/mcp
```

2. **Sign in.** Grok Build opens your browser the first time it uses Rivelant. You can also sign in from /mcps.

3. **Check it.**

```
grok mcp doctor rivelant
```

- **Load the tools:** Open /mcps in Grok Build to load and sign in to the server.
- **Check it is there:** `grok mcp list` shows rivelant and `grok mcp doctor rivelant` passes.
- **Grok Build documentation:** https://docs.x.ai/build/features/mcp-servers

### Chat apps: Claude app, ChatGPT, grok.com

These add connectors in their settings, which an agent cannot reach. If you are one of them, give the user the steps for their app.

#### Claude app

Claude app adds connectors in its settings, which you cannot reach. Give the user these steps instead of trying to run anything.

1. **Open connectors.** In Claude, go to Customize › Connectors › Add › Add custom connector.

2. **Add Rivelant.** Name it Rivelant, paste the address below, choose “Sign in now” and approve access in your browser.

```
https://app.rivelant.com/mcp
```

3. **Turn it on in a chat.** Click + at the bottom left, open Connectors and switch on Rivelant.

- **Load the tools:** Start a new chat and switch Rivelant on under + › Connectors.
- **Check it is there:** Rivelant shows as connected under Customize › Connectors.
- **Claude app documentation:** https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp

#### ChatGPT

ChatGPT adds connectors in its settings, which you cannot reach. Give the user these steps instead of trying to run anything.

1. **Add a custom MCP server.** Go to chatgpt.com/plugins, click + and choose “Add custom MCP server”.

2. **Connect Rivelant.** Name it Rivelant, paste the address below, choose OAuth and approve access in your browser.

```
https://app.rivelant.com/mcp
```

3. **Use it in a new chat.** Start a new chat and ask your first question.

- **Load the tools:** Refresh the connection under Plugins, then start a new chat.
- **Check it is there:** Rivelant shows its tools under chatgpt.com/plugins.
- **ChatGPT documentation:** https://developers.openai.com/plugins/deploy/connect-chatgpt

#### grok.com

grok.com adds connectors in its settings, which you cannot reach. Give the user these steps instead of trying to run anything.

1. **Add a custom connector.** Go to grok.com/connectors and choose New Connector › Custom.

2. **Connect Rivelant.** Paste the address below and sign in to approve access.

```
https://app.rivelant.com/mcp
```

3. **Ask in a new chat.** Start a new chat and ask your first question.

- **Load the tools:** Start a new chat on grok.com.
- **Check it is there:** grok.com lists Rivelant under Connectors.
- **grok.com documentation:** https://docs.x.ai/grok/connectors

## 2. Sign in

- **OAuth (preferred).** Your client opens Rivelant’s sign-in page in the browser; the user approves access. New users can create a free account on that page and come straight back. If the client does not open it by itself, use its sign-in command from step 1.
- **API key (fallback).** Only when the client has no browser sign-in, or runs on a machine without a browser. The user creates a key at https://app.rivelant.com/settings under API keys and stores it as `RIVELANT_API_KEY` or in the client’s secret settings. Send it as `Authorization: Bearer <key>` (`x-api-key: <key>` also works).
- **No browser on this machine?** Rivelant does not support device-code sign-in. Use an API key.

## 3. Verify

1. Make sure the Rivelant tools are loaded in this session (see “Load the tools” for your agent).
2. Call `whoami`, then `list_projects`. Both are free.
3. If the tools cannot be loaded without the user (a restart, a new session), stop and tell them the one thing to do. Do not retry in a loop. Tell them that afterwards they can say **“continue Rivelant setup”** and you will pick up at step 3.

Track three things separately: installed, signed in, verified. A configured server is not proof this session can use it. Do not claim it works until `whoami` succeeds.

## 4. Start optimizing

Once verified, take the first real step for the user:

1. **Find the site.** If `list_projects` returns a project, use it. If not, find the website’s URL: look in the repository you are working in (a CNAME file, the site URL in the framework config, `homepage` in package.json, the README, deployment settings), otherwise ask. Confirm it with the user, then call `create_project` with that domain. It uses no credits.
2. **Audit it.** Call `run_site_audit` with the defaults. Do not turn on JavaScript rendering or Lighthouse unless the user asks; rendering uses credits. Poll `get_audit_status` until it finishes (usually a few minutes), then read `get_audit_issues`.
3. **Report the top three fixes**, most impact first, in plain words.
4. **If you can edit the site’s code**, offer to fix them, and show the changes before committing anything.

The user can then ask, for example:
- “Which searches are we close to winning?” (needs Google Search Console connected in Rivelant)
- “Which questions does ChatGPT answer without naming us?”
- “Find keywords worth targeting for my site.”

## 5. Reply

Keep the final reply under 120 words:

**Status** — connected, or the one thing blocking it.
**What I found** — the top fixes from the audit, if it ran.
**Next** — one or two things the user can ask next.

Leave out file paths, versions, tool names and other integrations unless they explain a problem.

## If something goes wrong

- **“Needs authentication” or 401:** run the sign-in step again.
- **Tools do not show up:** load them as described for your agent; it may take a restart.
- **Your client cannot add remote MCP servers:** tell the user, and point them to https://rivelant.com/integrations.
- **Anything else:** support@rivelant.com
