Gemini MCP Server
The Gemini MCP Server is a TypeScript-based server that enables:
Text Generation: Generate text using the Gemini 2.0 Flash model
Customizable Parameters: Configure generation with parameters like temperature, topK, topP, and maxOutputTokens
Streaming Support: Stream text output for real-time responses
Conversation Context: Maintain context for natural continuous interactions
MCP Protocol Integration: Seamlessly integrates with clients like Claude Desktop
Direct API Implementation: Uses direct HTTP requests to the Gemini API
Integrates with Google's Gemini model (specifically Gemini 2.0 Flash) through direct API calls to generate text with configurable parameters while maintaining conversation context.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Gemini MCP Serverexplain quantum computing in simple terms"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
gemini-mcp-server
A TypeScript implementation of a Model Context Protocol (MCP) server that integrates with Google's Gemini model using direct API calls.
Features
Uses direct calls to the Gemini API (no deprecated SDK)
Supports the latest Gemini 2.0 Flash model
Implements MCP protocol for seamless integration with Claude
Maintains conversation context for natural interactions
Related MCP server: Gemini MCP Server
MCP Tools
generate_text
From server: gemini
Generate text using Gemini model with configurable parameters.
Prerequisites
Node.js 18 or higher
Google Gemini API key
TypeScript
Claude Desktop app
Installation
Clone the repository:
git clone https://github.com/YOUR-USERNAME/gemini-mcp-server.git
cd gemini-mcp-serverInstall dependencies:
npm installBuild:
npm run buildClaude Desktop Integration
To use this server with Claude Desktop:
Open Claude Desktop
Go to Settings > Developer
Click "Edit Config"
Add the following configuration:
"gemini": {
"command": "node",
"args": ["path\\to\\dist\\gemini_mcp_server.js"],
"env": {
"GEMINI_API_KEY": "gemini_api_key"
},
"cwd": "path\\to\\gemini-mcp-server"
}Replace:
/path/to/gemini-mcp-serverwith the absolute path to your repositoryyour_api_key_herewith your actual Google Gemini API key
The server will now be available in Claude Desktop's MCP server list.
API Implementation
This server uses direct HTTP requests to the Gemini API endpoint. The API request format follows Google's official documentation:
curl "https://generativelanguage.googleapis.com/v1beta/models/gemini-2.0-flash:generateContent?key=GEMINI_API_KEY" \
-H 'Content-Type: application/json' \
-X POST \
-d '{
"contents": [{
"parts":[{"text": "Explain how AI works"}]
}]
}'Testing
You can test the direct API implementation using the example script:
node dist/example_direct_api.js "Your prompt here"License
MIT
Available Tools
1 toolgenerate_textD
| Name | Required | Description | Default |
|---|---|---|---|
| maxOutputTokens | No | ||
| prompt | Yes | ||
| stream | No | ||
| temperature | No | ||
| topK | No | ||
| topP | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.0- First observed
generate_text
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generate_text' has a distinct purpose by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'generate_text' follows a clear verb_noun pattern.
One tool is too few for a server named 'Gemini MCP Server', which suggests a broader scope like interacting with Gemini AI services. A single text generation tool feels thin and incomplete for such a domain.
The server is severely incomplete for its implied purpose. With only a text generation tool, it lacks essential operations like chat interactions, model selection, or other AI functionalities expected from a Gemini server, leading to significant gaps.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
- QuallaaOAuthcom.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Related MCP Servers
- AlicenseAqualityFmaintenanceModel Context Protocol (MCP) server implementation that enables Claude Desktop to interact with Google's Gemini AI models.681258MIT
- AlicenseAqualityDmaintenanceA TypeScript server that integrates Google's Gemini Pro model with Claude Desktop through the Model Context Protocol, allowing Claude users to access Gemini's text generation capabilities.77012MIT
- FlicenseNot gradedqualityDmaintenanceA server implementing the Model Context Protocol that enables AI assistants like Claude to interact with Google's Gemini API for text generation, text analysis, and chat conversations.-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude Desktop to interact with Google's Gemini 2.5 Pro Experimental AI model, with features like Google Search integration and token usage reporting.2814Apache 2.0
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/IA-Entertainment-git-organization/gemini-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server