multimodal-reader-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | Yes | Google Generative AI API key | |
| MULTIMODAL_READER_MODEL | No | Override default model for all requests | gemini-2.5-flash |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_mediaB | Read a local audio or video file and return structured analysis. |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with another. The tool's purpose is clearly described as reading local audio/video files.
The single tool name 'read_media' follows a consistent verb_noun pattern, though with only one tool, consistency is trivially satisfied.
A single tool feels too thin for a server claiming to be 'multimodal.' The name implies broader media coverage, but only one generic reading operation is provided, which is too few for the apparent scope.
The tool only supports audio and video, leaving out images and other media types that multimodal implies. There are also no supporting operations like format listing or metadata retrieval, creating significant gaps for a reader.