mcp-omni-context
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_context_dataA | Extracts readable code/text from images, single files, or zip archives and returns a strictly-ordered, LLM-ready text dump with a file tree for archives. Images are analyzed sequentially; each one is wrapped in |
| find_imagesA | Scans the system temp, clipboard, Downloads, Desktop, Pictures, Telegram Desktop and the ~/.mcp-omni-context/uploads folders for the most recent image files and returns their paths, newest first. Use this when the user pastes or drops a screenshot with no obvious file path, then pass the returned path(s) to read_context_data. |
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 2 tools
The two tools have clearly distinct purposes: read_context_data extracts content from files/images/archives, while find_images locates image paths. They complement each other without overlapping, so an agent can easily choose the right tool.
Both tool names follow a consistent verb_noun snake_case pattern: read_context_data and find_images. This predictability makes the tool set easy to navigate.
With only 2 tools, the count is slightly below the typical 3-15 range, but it is appropriate for the narrowly scoped purpose of context extraction. Each tool is essential and earns its place.
The tool surface covers the core workflow: reading content from images, files, and archives, plus finding images when no path is provided. There are no significant gaps for the stated domain; minor omissions like other archive formats are acceptable.