Openeye MCP Server

every AR headset maker - HoloLens, Snap Spectacles, Apple, Android - ships a device that can see. none of them ship a brain. every developer building on these platforms has to figure out the intelligence layer themselves, from scratch, every time, for every device. the work doesn't compound. what one team learns on HoloLens doesn't help the team building on WebXR. every deployment is a silo.

People connecting memory tools to Claude, Cursor, VS Code, or another MCP client. The project is written in Python.

VERIFIED ACTIVE

LAST COMMIT 2026-05-19 · ★ 2 · #217 OF 259 MAINTAINED MEMORY · VERIFIED 2026-08-25

MIT · Python servers · how we verify → /methodology

01 · Install Openeye

before you install - you'll need

Set ANTHROPIC_API_KEY, OPENEYE_CONTEXT_OPTIN, OPENEYE_CONTEXT_API_KEY before connecting.

Claude Code

claude mcp add dumbspacecookie-openeye -- npx -y @dumbspacecookie/openeye

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "dumbspacecookie-openeye": {
      "command": "npx",
      "args": [
        "-y",
        "@dumbspacecookie/openeye"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @dumbspacecookie/openeye - published under the repo owner's npm scope (@dumbspacecookie)

registry namespace io.github.dumbspacecookie is GitHub-verified and matches the repo owner

03 · Who maintains Openeye

openeye is maintained by dumbspacecookie. We track 2 MCP servers from dumbspacecookie - 2 actively maintained, 3 combined GitHub stars, oldest repo from May 2026.

04 · Facts

category
memory - ranked #217 of 259 actively-maintained memory servers as of 2026-08-25.
registry
io.github.dumbspacecookie/openeye (active, first published 2026-05-19)
packages
npm:@dumbspacecookie/openeye

05 · Openeye FAQ

What is Openeye?

every AR headset maker - HoloLens, Snap Spectacles, Apple, Android - ships a device that can see. none of them ship a brain. every developer building on these platforms has to figure out the intelligence layer themselves, from scratch, every time, for every device. the work doesn't compound. what one team learns on HoloLens doesn't help the team building on WebXR. every deployment is a silo.

Is Openeye still maintained?

Yes - as of 2026-08-25, its last commit was 2026-05-19. We re-verify nightly.

How do I install Openeye?

Run `npx -y @dumbspacecookie/openeye`. The README documents 3 environment variables (ANTHROPIC_API_KEY, OPENEYE_CONTEXT_OPTIN, OPENEYE_CONTEXT_API_KEY) to set first. Set ANTHROPIC_API_KEY, OPENEYE_CONTEXT_OPTIN, OPENEYE_CONTEXT_API_KEY before connecting. You can also paste the ready-made client config above.

Does Openeye run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

06 · Alternatives to Openeye

Pairs well with

Servers that cover what Openeye doesn't - only shown when the pairing reason fits the companion.

  1. Server Filesystem → filesystem companion filesystem · ★ 38,704
  2. X402 List MCP → filesystem companion filesystem · ★ 58