mcpField
V
Voris

Voris

Local
docs.voris.aiData & Analytics0Updated 15w ago
RepositoryVisit website

About Voris

Voris is a small local proxy that connects MCP clients to the hosted Voris analytics server. It forwards protocol messages without implementing tools or accessing the database; the hosted service handles authentication, scopes, rate limits, and auditing.

Key features

  1. 01Bridge stdio to hosted HTTPS endpoint
  2. 02Forward JSON-RPC messages
  3. 03Scope a connection to one site
  4. 04Keep protocol output separate from diagnostics

Use cases

  1. 01Connect a local MCP client to Voris
  2. 02Use Voris analytics from an editor agent or CLI

MCP support

The package bridges a local MCP client's stdio connection to the hosted Voris MCP server over Streamable HTTP. The hosted server provides the tools and enforces access controls.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "ai-voris": {
      "command": "npx",
      "args": [
        "-y",
        "@voris-ai/mcp"
      ],
      "env": {
        "VORIS_API_KEY": "<VORIS_API_KEY>"
      }
    }
  }
}
Run commandnpx -y @voris-ai/mcp
Environment variables to set
VORIS_API_KEYSecretYour Voris MCP API key. Generate one in the Voris dashboard under Settings > AI Connections.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@voris-ai/mcp0.0.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

@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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.