llm-vision-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STEPFUN_API_KEY | Yes | Your StepFun API key | |
| STEPFUN_API_MODE | No | API mode: standard or step_plan | standard |
| STEPFUN_BASE_URL | No | Base URL for the StepFun API | https://api.stepfun.com/v1 |
| STEPFUN_TIMEOUT_MS | No | Timeout in milliseconds | 120000 |
| STEPFUN_VISION_MODEL | No | Vision model to use | step-1o-turbo-vision |
| STEPFUN_USE_STEP_PLAN | No | Enable Step Plan mode (legacy, use STEPFUN_API_MODE instead) | |
| STEPFUN_DEFAULT_DETAIL | No | Default detail level: high or low | high |
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 |
|---|---|
| analyze_imageB | General-purpose image understanding for photos, screenshots, documents, objects, scenes, and visual questions. |
| extract_text_from_imageB | OCR for screenshots, documents, terminal output, logs, code snippets, forms, and UI text. |
| diagnose_error_screenshotB | Analyze error screenshots, stack traces, console output, IDE errors, terminal failures, and crash dialogs. |
| understand_technical_diagramB | Explain architecture diagrams, flowcharts, UML, sequence diagrams, ER diagrams, network diagrams, and system maps. |
| analyze_data_visualizationB | Interpret charts, graphs, tables, dashboards, metrics screenshots, and data visualizations. |
| ui_to_artifactA | Convert UI screenshots into implementation notes, layout structure, design specs, or recreation prompts. |
| ui_diff_checkA | Compare expected and actual UI screenshots for visual regression, missing elements, layout differences, typography, color, spacing, and priority. |
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 understanding task: general analysis, OCR, error diagnosis, diagram explanation, data visualization, UI-to-code conversion, and UI diffing. The specialized scopes prevent confusion, even though analyze_image is broad, it serves as a catch-all rather than overlapping with specific tools.
Most tools follow a verb-first naming pattern (analyze_image, extract_text_from_image, diagnose_error_screenshot, understand_technical_diagram, analyze_data_visualization), but two tools (ui_to_artifact, ui_diff_check) are noun-first. Despite this minor deviation, all names are readable and use consistent snake_case.
With 7 tools, the server is well-scoped for image understanding. Each tool covers a distinct sub-domain (general analysis, OCR, errors, diagrams, data viz, UI artifacts, UI comparison), and no tool feels redundant or unnecessary.
The tool surface is comprehensive for an image understanding server, covering general understanding, text extraction, error diagnosis, diagram interpretation, data visualization analysis, UI-to-code conversion, and UI regression checking. There are no obvious missing operations within the stated domain.