Hydra Vision MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYDRA_MODEL | No | Vision model | public/kimi-k3 |
| HYDRA_TOP_P | No | Nucleus sampling | 0.6 |
| HYDRA_API_KEY | Yes | Upstream provider key. Required for analysis. | |
| HYDRA_BASE_URL | Yes | API root; /chat/completions is appended. Required for analysis. | |
| HYDRA_MAX_TOKENS | No | Output limit; adjust for your provider's model | 131072 |
| HYDRA_TIMEOUT_MS | No | Request timeout | 300000 |
| HYDRA_TEMPERATURE | No | Sampling temperature | 0.8 |
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 |
|---|---|
| ui_to_artifactA | Convert UI screenshots into various artifacts: code, prompts, design specifications, or descriptions. Use this tool ONLY when the user wants to:
Do NOT use for: screenshots containing text/code to extract, error messages, diagrams, or data visualizations. |
| extract_text_from_screenshotA | Transcribe visible text from screenshots without repairing or beautifying the source. Use this tool ONLY when the user has a screenshot containing text and wants to extract it. This tool specializes in OCR for code, terminal output, documentation, and general text extraction. Do NOT use for: UI design conversion, error diagnosis, or diagram understanding. |
| diagnose_error_screenshotA | Diagnose and analyze error messages, stack traces, and exception screenshots. Use this tool ONLY when the user has an error screenshot and needs help understanding or fixing it. This tool specializes in error analysis and provides actionable solutions. Do NOT use for: code extraction, UI analysis, or diagram understanding. |
| understand_technical_diagramA | Analyze and explain technical diagrams including architecture diagrams, flowcharts, UML, ER diagrams, and system design diagrams. Use this tool ONLY when the user has a technical diagram and wants to understand its structure or components. This tool specializes in interpreting visual technical documentation. Do NOT use for: UI screenshots, error messages, or data visualizations/charts. |
| analyze_data_visualizationA | Analyze data visualizations, charts, graphs, and dashboards to extract insights and trends. Use this tool ONLY when the user has a data visualization image and wants to understand the data patterns or metrics. This tool specializes in interpreting visual data representations. Do NOT use for: UI mockups, error messages, or technical architecture diagrams. |
| ui_diff_checkA | Compare two UI screenshots to identify visual differences and implementation discrepancies. Use this tool ONLY when the user wants to compare an expected/reference UI with an actual implementation. This tool is specialized for UI quality assurance and design-to-implementation verification. Do NOT use for: general image comparison, error diagnosis, or analyzing single UIs. |
| analyze_imageA | General-purpose image analysis for scenarios not covered by specialized tools. Use this tool as a FALLBACK when none of the other specialized tools (ui_to_artifact, extract_text_from_screenshot, diagnose_error_screenshot, understand_technical_diagram, analyze_data_visualization, ui_diff_check) fit the user's need. This tool provides flexible image understanding for any visual content. |
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 7 tools
Each tool targets a distinct image type or task (UI conversion, OCR, error diagnosis, technical diagrams, data viz, UI diff, general fallback) and descriptions explicitly state boundaries with 'Do NOT use for' exclusions, so an agent can easily select the right tool. The fallback is clearly defined as a last resort, preventing overlap.
All names use snake_case, but 5 of 7 follow a verb_noun pattern while 'ui_to_artifact' and 'ui_diff_check' start with a noun/adjective and use non-verb constructions. This mixed convention is readable but not fully consistent.
7 tools is well-scoped for an image analysis server, with six specialized tools covering common visual tasks plus one explicit fallback. Each tool has a clear purpose and no tool feels redundant.
The surface covers major screenshot and diagram analysis needs (UI conversion, OCR, error diagnosis, technical diagrams, data viz, UI diff) and includes a general fallback for uncovered cases. Minor gaps exist, such as structured data extraction from charts or non-UI image comparison, but agents can work around these via the fallback.