Voris

What Voris MCP server does

The Voris MCP server gives local MCP clients an interface to hosted Voris web analytics. The supported use cases include querying analytics metrics, retrieving citations, and scaffolding tracking. The local package does not implement those operations itself; it acts as a transport bridge to the hosted service.

Each connection is associated with one site through its Voris MCP connection key. This makes the server suitable for agents that need site-specific analytics access rather than a shared, multi-site database connection.

How it works

A client launches voris-mcp as a subprocess and communicates with it through standard input and output using MCP. The proxy sends those JSON-RPC messages to the hosted endpoint over Streamable HTTP and returns the responses to the client.

The default remote endpoint is https://mcp.voris.ai/mcp. Requests authenticate with the configured key as a bearer token. Authentication, scope enforcement, rate limiting, auditing, and database access are performed by the hosted Voris service, not by the local proxy.

Standard output is reserved for the MCP protocol stream. Diagnostic messages go to standard error so they do not interfere with client communication.

Setup and configuration

Set VORIS_API_KEY in the environment used to launch the process:

VORIS_API_KEY=vor_mcp_… voris-mcp

Create the key in the Voris dashboard under Settings → AI Connections. In Claude Desktop, configure the server as a subprocess and pass the key through the env object:

{
  "mcpServers": {
    "voris": {
      "command": "voris-mcp",
      "env": { "VORIS_API_KEY": "vor_mcp_…" }
    }
  }
}

Use --endpoint <url> or --endpoint=<url> to replace the default hosted URL, primarily for local development. If VORIS_API_KEY is missing, the process writes an error message to standard error and exits with status code 1.

Tools and capabilities

The Voris MCP server exposes the hosted Voris capabilities for:

• Querying web analytics metrics
• Obtaining citations for analytics results
• Scaffolding tracking setup

The proxy forwards these operations rather than defining local tool implementations. The available enforcement and access scope come from the hosted service and the key used for the connection.

Limitations and notes

The package is currently not published to npm. The repository contains the build and tarball tests, while public npm distribution is planned for a later phase. Until distribution is available, users should generate a key and copy the hosted-connection snippet from the Voris dashboard.

This package does not provide local database access or local enforcement logic. Reaching the hosted endpoint is therefore part of normal operation. One connection is limited to exactly one site according to its key, and the endpoint override should be treated as a development option unless a different deployment is explicitly provided.