Local MCP Gemini Automation Engine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USE_UV | No | Flag to use uv package manager | 1 |
| GEMINI_MODEL | No | The Gemini model to use (e.g., gemini-2.5-flash) | gemini-2.5-flash |
| GEMINI_API_KEY | Yes | Your Google AI Studio API Key |
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 |
|---|---|
| mcp_read_documentB | Reads a document and returns its contents. |
| mcp_edit_documentA | Overwrites or updates a document's total content with new text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| format | Rewrites the contents of the document in Markdown format. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mcp_list_documents | Lists all available document IDs. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one reads documents and the other edits/overwrites them. There is no overlap or ambiguity in their intended actions.
Both tool names follow a consistent verb_noun pattern with a common 'mcp_' prefix: mcp_read_document and mcp_edit_document. Naming is uniform and predictable.
With only 2 tools, the set is on the thin side for a server named 'Gemini Automation Engine.' While the tools are focused, the count feels minimal and may not justify a broader automation scope.
The domain appears to be document management, but the surface only covers reading and editing. Missing operations like create, delete, or list documents represent significant gaps that would hinder agents from performing basic lifecycle tasks.