Procedure verification for AR/XR with memory, visual sessions, and DPO trajectory export.
Procedure verification for AR/XR with memory, visual sessions, and DPO trajectory export. Exposed over MCP by the openeye mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
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.
Everything the assistant can do here goes through one of these:
capability — OpenEyesearch_memory — FTS5 search across all past agent sessionssearch_frames — FTS5 search across all past frame descriptionsrecall_skill — retrieve relevant procedural skills for the current taskwrite_skill — persist a new skill doc after completing a complex taskstart_visual_session — begin a tracked AR/XR sessionend_visual_session — close a visual sessionlog_frame — record a frame's scene descriptionverify_step — record a step result — pass / fail / uncertainprovider — env varOPENEYE_HOME — ~/.openeyeOPENEYE_PORT — 7770Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 8 environment variables: ANTHROPIC_API_KEY, OPENEYE_CONTEXT_OPTIN, OPENEYE_CONTEXT_API_KEY, GROQ_API_KEY, OPENEYE_BIND_HOST, OPENEYE_SIDECAR_TOKEN, OPENEYE_CLOUD_URL, OPENEYE_CLOUD_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Openeye's toolset — capability, search_memory, search_frames and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dumbspacecookie; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| capability | OpenEye |
| search_memory | FTS5 search across all past agent sessions |
| search_frames | FTS5 search across all past frame descriptions |
| recall_skill | retrieve relevant procedural skills for the current task |
| write_skill | persist a new skill doc after completing a complex task |
| start_visual_session | begin a tracked AR/XR session |
| end_visual_session | close a visual session |
| log_frame | record a frame's scene description |
| verify_step | record a step result — pass / fail / uncertain |
| provider | env var |
| OPENEYE_HOME | ~/.openeye |
| OPENEYE_PORT | 7770 |
| OPENEYE_BIND_HOST | 127.0.0.1 |
| OPENEYE_SIDECAR_TOKEN | — |
{
"mcpServers": {
"openeye": {
"command": "npx",
"args": ["-y", "@dumbspacecookie/openeye"],
"env": {
"ANTHROPIC_API_KEY": "your-value",
"OPENEYE_CONTEXT_OPTIN": "your-value",
"OPENEYE_CONTEXT_API_KEY": "your-value",
"GROQ_API_KEY": "your-value",
"OPENEYE_BIND_HOST": "your-value",
"OPENEYE_SIDECAR_TOKEN": "your-value",
"OPENEYE_CLOUD_URL": "your-value",
"OPENEYE_CLOUD_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
| OPENEYE_CONTEXT_OPTIN | Configuration value read at startup. | Optional |
| OPENEYE_CONTEXT_API_KEY | Credential the server authenticates with. | Yes |
| GROQ_API_KEY | Credential the server authenticates with. | Yes |
| OPENEYE_BIND_HOST | Endpoint or connection string the server talks to. | Optional |
| OPENEYE_SIDECAR_TOKEN | Credential the server authenticates with. | Yes |
| OPENEYE_CLOUD_URL | Endpoint or connection string the server talks to. | Yes |
| OPENEYE_CLOUD_KEY | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.