Voris

Official registry Marketing and sales

Voris privacy-native web analytics for AI agents: query metrics & citations, scaffold tracking.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @voris-ai/mcp
Claude Code
claude mcp add voris -e 'VORIS_API_KEY=<your voris_api_key>' -- npx -y @voris-ai/mcp@0.0.2
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "voris": {
            "command": "npx",
            "args": [
                "-y",
                "@voris-ai/mcp@0.0.2"
            ],
            "env": {
                "VORIS_API_KEY": "<your voris_api_key>"
            }
        }
    }
}

Environment variables

  • VORIS_API_KEY required secret Your Voris MCP API key. Generate one in the Voris dashboard under Settings > AI Connections.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

@voris-ai/mcp

voris-mcp — a thin stdio ⇄ HTTPS proxy that connects a local MCP client (Claude Desktop, an editor agent, a CLI) to the hosted Voris MCP server at https://mcp.voris.ai/mcp.

It forwards JSON-RPC messages verbatim between the client's stdio channel and the hosted endpoint over Streamable HTTP. It contains no tool logic and no database access — all enforcement (authentication, scopes, rate limits, audit) lives in the hosted server. One connection is scoped to exactly one site, by your key.

Usage

Your MCP client launches voris-mcp as a subprocess and speaks MCP over its stdin/stdout. Provide your key via the environment:

VORIS_API_KEY=vor_mcp_… voris-mcp

Example Claude Desktop configuration:

{
  "mcpServers": {
    "voris": {
      "command": "voris-mcp",
      "env": { "VORIS_API_KEY": "vor_mcp_…" }
    }
  }
}
Options
  • VORIS_API_KEY (required) — your Voris MCP connection key, generated in Settings → AI Connections. It is sent as Authorization: Bearer … to the hosted endpoint. If it is unset, voris-mcp writes a message to stderr and exits with code 1.
  • --endpoint <url> — override the hosted endpoint (default https://mcp.voris.ai/mcp). Mainly for local development; also accepts --endpoint=<url>.

All diagnostics are written to stderr; stdout carries only the MCP protocol stream, so it stays clean for the client.

Status

This release does not publish voris-mcp to npm. The package is built and tarball-tested here; public npm distribution ships in the next phase (A042). Until then, generate your key and copy the hosted-connection snippet from the Voris dashboard.

Frequently asked questions

What is Voris?

Voris privacy-native web analytics for AI agents: query metrics & citations, scaffold tracking.

How do I install Voris?

It runs on your machine. In Claude Code: claude mcp add voris -e 'VORIS_API_KEY=<your voris_api_key>' -- npx -y @voris-ai/mcp@0.0.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Voris need an API key?

Yes. It expects VORIS_API_KEY, which you set in its configuration.

Is Voris open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Voris?

It is published by Rocket-Venture-Labs. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.