AI Image Analysis MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging (optional) | |
| NODE_ENV | No | Environment mode (optional, e.g., development) | |
| SUPABASE_URL | No | Supabase project URL (optional, for cloud features) | |
| GEMINI_API_KEY | Yes | Your Google Gemini API key | |
| SUPABASE_ANON_KEY | No | Supabase anonymous key (optional, for HTTP client) | |
| SUPABASE_SERVICE_KEY | No | Supabase service role key (optional) | |
| SUPABASE_FUNCTION_NAME | No | Supabase function name (optional) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_imageB | Securely analyze an image using Google Gemini AI with automatic type detection and security validations |
| upload_to_supabaseB | Upload image or analysis results to Supabase Storage with security validation |
| get_security_statusA | Get current security configuration and audit information |
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 responsibility: analyzing an image, uploading to storage, and retrieving security status. There is no meaningful overlap in their primary actions.
All names are snake_case and start with a verb, but 'upload_to_supabase' introduces a destination-specific pattern while the others follow a simpler verb_noun structure. This is a minor deviation from an otherwise consistent convention.
With 3 tools, the server is tightly scoped to its core image analysis, storage, and security purposes. Each tool earns its place without redundancy or bloat.
The core workflow of analyzing an image and uploading results is covered, and the security status tool adds useful oversight. Minor gaps exist around retrieving or managing previously uploaded assets, but these are not critical for the server's stated purpose.