{
  "markdown": "# @voris-ai/mcp\n\n`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`.\n\nIt 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.\n\n## Usage\n\nYour MCP client launches `voris-mcp` as a subprocess and speaks MCP over its stdin/stdout. Provide your key via the environment:\n\n```\nVORIS_API_KEY=vor_mcp_… voris-mcp\n```\n\nExample Claude Desktop configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"voris\": {\n      \"command\": \"voris-mcp\",\n      \"env\": { \"VORIS_API_KEY\": \"vor_mcp_…\" }\n    }\n  }\n}\n```\n\n### Options\n\n- **`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`.\n- **`--endpoint <url>`** — override the hosted endpoint (default `https://mcp.voris.ai/mcp`). Mainly for local development; also accepts `--endpoint=<url>`.\n\nAll diagnostics are written to **stderr**; stdout carries only the MCP protocol stream, so it stays clean for the client.\n\n## Status\n\n**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.\n",
  "bytes": 1695,
  "sha": "8243a0854be962a19551f528f38f0ab8b74f3f17c88b8507231137bdd372be34",
  "repo_slug": "rocket-venture-labs/voris-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_ai_voris_mcp_server_3a659b7c/readme"
}