Gemini Email Subject Generator MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Set to true for verbose logging | |
| GEMINI_API_KEY | Yes | Your Google Gemini API key | |
| NODEMAILER_EMAIL | Yes | Your email address for sending emails | |
| NODEMAILER_PASSWORD | Yes | Your email app password (for Gmail, use an app password) |
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 |
|---|---|
| generate-thinkingC | Generate detailed thinking process text using Gemini Flash 2 model |
| send-emailC | Send an email with AI-generated subject using Gemini Flash 2 |
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 2 tools
The two tools have completely distinct purposes: one generates thinking process text, while the other sends emails with AI-generated subjects. There is no overlap or ambiguity between these functions, making it impossible for an agent to confuse them.
Both tools use a verb-object naming pattern (generate-thinking, send-email), which is consistent and readable. The minor deviation is the hyphenation style, but this is uniform across both tools, so it does not cause confusion.
With only 2 tools, the server feels thin for its stated purpose of email subject generation. It lacks essential operations like retrieving email history, managing templates, or handling errors, which limits its utility and scope.
The server is severely incomplete for email subject generation. It provides no way to list, update, or delete generated content, and lacks supporting tools for email management (e.g., checking sent emails, setting recipients). This creates significant gaps that will hinder agent workflows.