OpenRouter Image MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (info, debug, etc.) | info |
| MAX_IMAGE_SIZE | No | Maximum image size in bytes (default: 10MB) | 10485760 |
| RETRY_ATTEMPTS | No | Number of retry attempts for API calls | 3 |
| OPENROUTER_MODEL | No | The OpenRouter model to use for image analysis | google/gemini-2.0-flash-exp:free |
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key (required) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_imageC | Analyze images using OpenRouter's vision models. Supports various input formats including base64, file paths, and URLs. |
| analyze_webpage_screenshotB | Specialized tool for analyzing webpage screenshots. Extracts content, layout information, and interactive elements from web pages. |
| analyze_mobile_app_screenshotA | Specialized tool for analyzing mobile app screenshots. Provides insights into UI design, user experience, platform conventions, and app functionality. |
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 3 tools
Each tool has a clearly distinct purpose: analyze_image handles general image analysis, analyze_mobile_app_screenshot focuses specifically on mobile app UI/UX insights, and analyze_webpage_screenshot targets webpage content and layout extraction. There is no overlap or ambiguity between these three specialized functions.
All three tools follow a consistent verb_noun pattern with 'analyze_' prefix and descriptive suffixes (image, mobile_app_screenshot, webpage_screenshot). The naming is perfectly uniform and predictable across the entire toolset.
With only 3 tools, the set feels somewhat thin for an image analysis server. While the tools cover distinct use cases, there are likely missing operations like batch processing, different analysis modes, or result formatting that would make the surface more complete.
The tools cover three specific analysis scenarios well, but there are notable gaps in the image analysis domain. Missing are tools for basic operations (e.g., image metadata extraction, format conversion), alternative analysis methods, or post-processing capabilities that would provide more comprehensive coverage.