VR.org VR / AR / XR Reader

vr-org-mcp

Read-only Model Context Protocol server for [VR.org](https://vr.org), a dedicated VR / AR / XR news publication and aggregator.

It gives any MCP-compatible agent (Claude Desktop, Claude Code, Cursor, Continue, and others) one-call access to live VR, AR, and XR news, VR.org's original editorial (including full article text), the VR/AR/XR events calendar, curated headset deals, buyer-guide answers, and top-game and top-app lists.

Eleven tools, five resources, and three prompts. Zero keys. Zero writes. Zero payments.

Install

Run it directly with npx (no global install needed):

npx vr-org-mcp

Claude Desktop

One-click: download the .mcpb bundle from the latest release and double-click it to install into Claude Desktop. Or configure manually:

Add to your claude_desktop_config.json:

{

"mcpServers": { "vr-org": { "command": "npx", "args": ["-y", "vr-org-mcp"] } } }

Claude Code

claude mcp add vr-org -- npx -y vr-org-mcp

Cursor

Add to .cursor/mcp.json:

{

"mcpServers": { "vr-org": { "command": "npx", "args": ["-y", "vr-org-mcp"] } } }

Hosted remote endpoint (no install)

VR.org also runs the same tools as a remote server over MCP's streamable-HTTP transport, so web clients (ChatGPT connectors, Claude.ai connectors) can use it with no local install:

https://vr.org/mcp

Human setup walkthrough for every client: vr.org/connect.

Tools

Resources

Browsable MCP resources an app can attach as context:

Prompts

How it works

Every tool composes VR.org's public JSON API (https://vr.org/api/*) into a single agent-friendly response. The server is a thin proxy: it holds no secrets, writes nothing, and cannot move money.

Threat model

VR.org's editorial is controlled, but the live feed also carries third-party RSS headlines. To keep a malicious or compromised upstream headline from manipulating the calling model, every tool output is:

1. Sanitized. Control characters and zero-width / direction-override characters are stripped from every string.
2. Capped. Serialized responses are limited to 50 KB so a large payload cannot flood the agent's context window.

Inputs are validated before any outbound request and every free-text parameter is length-capped at the schema layer. Errors are returned as structured, non-echoing objects rather than raw stack traces; on the rare path where an error string reaches the caller it runs through the same output scrub as a tool result, with any credential-shaped substring redacted and the text capped, and is flagged with isError.

Configuration

The API base URL is fixed to https://vr.org in source and cannot be overridden, so the server can only ever talk to VR.org.

Development

npm install

npm run dev # run from source over stdio npm run build # compile to dist/ npm test # run the offline test suite npm run typecheck # type-check without emitting

Changelog

0.5.0

Protocol upgrade. Requires Node.js 20 or newer.

• The server now runs on the MCP SDK v2 (@modelcontextprotocol/server) and speaks the 2026-07-28 protocol revision. Clients on the 2025 revisions connect exactly as before: the opening message decides which revision a connection uses.
• Node.js 18 is no longer supported, because the v2 SDK needs Node.js 20. If you are pinned to Node 18, stay on 0.4.4.
• The install is much smaller. The old SDK pulled in an HTTP stack this stdio server never used, more than 80 packages of it. The production dependency tree is now three packages, and npm audit is clean with no overrides.
• The hosted endpoint at https://vr.org/mcp moved to the same protocol on the same day. It also answers at /mcp directly now instead of redirecting to /api/mcp, which halves the round trips for clients configured with the short URL.
• No tool, resource or prompt changed.

0.4.4

search_vr_news now matches on words instead of one exact phrase.

• The keyword filter used to require the whole query to appear, as typed, somewhere in a headline or snippet. Agents tend to send queries like "steam frame release date" or "best vr headset 2026", and those came back empty even when the feed was full of matching stories. In a replay of 25 realistic queries against the live feed, 18 returned nothing.
• A query is now split into keywords. Filler ("what is the latest", "news", "today", years and month names) is dropped, and every remaining keyword has to appear in the headline, snippet, tags, category or source name, in any order. Plurals match singulars, punctuation is ignored ("half-life alyx" finds "Half-Life: Alyx"), and a model name typed without its space still matches ("psvr2" finds "PS VR2"). Numbers and two-letter terms match whole words only, so "quest 3" does not return Quest 3S stories.
• Headline matches are listed first, newest first inside each group.
• When a query is sent, the response adds match (all_terms, partial, none, or latest for a query that was all filler), terms (the keywords actually used) and total_matches. If nothing matches every keyword, the closest matches are returned and labelled partial with a hint. A call with no query returns exactly what it did before.
• The hosted endpoint at https://vr.org/mcp carries the same matcher.

0.4.3

Maintenance release.

• The vr_explain tool description now names the newer topics it can answer ("steam frame price", "meta vr glasses"), so an agent reading the tool list knows to ask for them. The hosted endpoint at https://vr.org/mcp carries the same wording.
• The release workflow now publishes through npm trusted publishing (OIDC) and only falls back to a token if that is rejected. Provenance is attached as before.

0.4.2

vr_explain and the vrorg://guides resource now answer from VR.org's live explainer feed, so they stay current between releases.

• The answers used to be a list compiled into the package in July 2026. By October most realistic topics ("steam frame", "steam frame price", "meta vr glasses", "quest 4") returned no_explainer, and several of the answers that did exist were out of date. The list is now fetched from https://vr.org/api/explainers and cached for ten minutes, the same way deals and events are, so a guide refresh on the site reaches agents without a package release.
• Every fetched entry is validated before use (keys must be a non-empty list of non-empty strings, and the link must be on https://vr.org) and passes through the same sanitizer as other upstream text. If the fetch fails or returns nothing valid, the built-in list answers instead. That list now mirrors the site's current 34 guides, up from 10, so an offline server still gives current answers. A failed fetch is remembered for one minute so an outage does not slow down every call.
• Matching is unchanged: the longest key contained in the topic wins, so "steam frame price" reaches the price page and not the Steam Frame hub.
• The explain_vr_topic prompt no longer offers 'passthrough' as an example topic, which had no answer. It and the no_explainer hint now suggest 'steam frame'.
• The get_vr_deals description names all five catalog sections: headsets, AR and XR glasses, accessories, haptics and body tracking, gaming hardware.
• Bumps @modelcontextprotocol/sdk from 1.30.0 to 1.32.1 and refreshes the ip-address and proxy-addr pins. The advisories behind this sit in the SDK's OAuth client and HTTP transport, which this stdio server never loads. npm audit on the production dependencies reports zero vulnerabilities.

0.4.1

Fixes from a September 2026 audit, matched on the hosted endpoint at vr.org/mcp.

• get_vr_article now returns the whole article. body_html was cut at the general 4,096-character string cap, which truncated most articles mid-tag while still reporting ok: true. It now has its own 45,000-character cap, and the 50 KB response cap still applies. The article also carries updated, the date a correction was applied, which the hosted endpoint already returned.
• vr_explain no longer answers short topics with the wrong guide. A topic like "vr" or "3" used to match inside a longer key and return "PSVR2 vs Quest 3" with confidence; the reverse match now needs four or more characters starting on a word boundary.
• compare_vr_headsets matches "Pimax Dream Air SE" correctly. The pimax alias was a prefix match that rewrote every Pimax query to Crystal.
• Reading vrorg://news/latest no longer shrinks keyword search to 25 items for the next minute (the two shared a cache key with different request sizes).
• A malformed slug in vrorg://article/{slug} now says "not found" instead of "temporarily unavailable, retry shortly".
• Refreshed transitive dependency pins (hono, fast-uri, qs) for npm audit.

0.4.0

Content provenance. Feed results now carry a provenance field on every item, either vr_org_editorial (written and edited by VR.org) or third_party_feed (a headline or snippet relayed verbatim from an outside publisher). Any response containing relayed text also carries a content_notice saying to