AI Studio MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_MODEL | No | Gemini model to use | gemini-2.5-flash |
| GEMINI_API_KEY | Yes | Your Google AI Studio API key | |
| GEMINI_TIMEOUT | No | Request timeout in milliseconds (default: 300000 = 5 minutes) | 300000 |
| GEMINI_MAX_FILES | No | Maximum number of files per request | 10 |
| GEMINI_TEMPERATURE | No | Temperature for generation (0-2). Lower values produce more focused responses, higher values more creative ones | 0.2 |
| GEMINI_MAX_OUTPUT_TOKENS | No | Maximum output tokens | 8192 |
| GEMINI_MAX_TOTAL_FILE_SIZE | No | Maximum total file size in MB | 50 |
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 |
|---|---|
| generate_contentA | Generate content using Gemini with optional file inputs, code execution, and Google search. Supports multiple files: images (JPG, PNG, GIF, WebP, SVG, BMP, TIFF), video (MP4, AVI, MOV, WebM, FLV, MPG, WMV), audio (MP3, WAV, AIFF, AAC, OGG, FLAC), documents (PDF), and text files (TXT, MD, JSON, XML, CSV, HTML). MIME type is auto-detected from file extension. Example usage: PDF to Markdown conversion: With Google Search: With Code Execution: Combining features with thinking mode: |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generate_content' has a clearly defined and distinct purpose.
A single tool inherently has perfect naming consistency. The tool name 'generate_content' follows a clear verb_noun pattern and there are no other tools to create inconsistency.
A single tool for an 'AI Studio MCP Server' feels too thin for the apparent scope. The tool handles multiple complex features (content generation, file processing, search, code execution), suggesting these might be better exposed as separate tools for clarity and agent usability.
The server's domain appears to be AI content generation and processing, but with only one tool, the surface is severely incomplete. There are obvious gaps for operations like listing models, managing sessions, checking status, or handling errors—common needs in such a domain that would require separate tools.