vr-org-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@vr-org-mcpwhat are the latest VR deals?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
vr-org-mcp
Read-only Model Context Protocol server for 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, curated headset deals, buyer-guide answers, and top-game and top-app lists.
Ten tools. Zero keys. Zero writes. Zero payments.
Install
Run it directly with npx (no global install needed):
npx vr-org-mcpClaude Desktop
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-mcpRelated MCP server: sellthenews-mcp
Tools
Tool | What it returns |
| Latest VR / AR / XR headlines from the live feed, with optional category filter and keyword match |
| Topics currently trending across the feed |
| Summaries of VR.org's own editorial articles, newest first |
| Metadata and canonical URL for one original by slug |
| Curated product picks with prices, badges, and retailer links |
| Side-by-side of two headsets (partial names accepted) |
| Current ranked top VR games list |
| Current ranked top VR apps and utilities list |
| The news sources VR.org aggregates, with counts |
| Canonical short answer plus pillar-page link for a common question |
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:
Sanitized. Control characters and zero-width / direction-override characters are stripped from every string.
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 errors are returned as structured, non-echoing objects rather than raw stack traces.
Configuration
Env var | Default | Purpose |
|
| Override the base URL (only useful for staging) |
| (none) | Optional suffix appended to the outbound User-Agent |
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 emittingLicense
MIT. A VR.org project.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/evanatpizzarobot/vr-org-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server