Oculus MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OCULUS_STATE_FILE | No | Path to Oculus state file. Defaults to $XDG_STATE_HOME/nvim/oculus.json or ~/.local/state/nvim/oculus.json if not set. | |
| OCULUS_TRACKING_FILE | No | Path to Oculus tracking file. Optional; if set, the file must exist and be valid. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tracked_projectsB | Read tracked GitHub/Codeberg projects and their Oculus group hierarchy. |
| list_saved_itemsC | Read saved activity metadata in Oculus order; does not fetch live forge data. |
| list_inspectionsB | Discover persisted inspection IDs before requesting their cached context. |
| get_inspection_contextA | Read a cached AI explanation and up to three suggested patch locations by exact ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The list_* tools target distinct resources (projects, inspections, saved items), and get_inspection_context has a specific retrieval role. However, list_inspections and list_saved_items both concern persisted metadata, which could cause minor initial ambiguity.
All tool names use consistent snake_case with clear list_ or get_ prefixes and noun phrases. The pattern is predictable and readable throughout.
Four tools is lean but reasonable for a focused read-only inspection and cache server. Each tool covers a distinct read operation, though the surface could potentially benefit from additional targeted operations.
The tools cover listing tracked projects, inspections, saved items, and retrieving cached inspection context, but there are no create, update, delete, or refresh operations for these entities. This may be intentional for a read-only surface, but notable lifecycle gaps remain.