A
licenseA
qualityF
maintenanceModel Context Protocol (MCP) server implementation that enables Claude Desktop to interact with Google's Gemini AI models.
6
46 npm
260
MIT
Gemini MCP Server
gemini-mcp-server
直接 API 呼び出しを使用して Google の Gemini モデルと統合する Model Context Protocol (MCP) サーバーの TypeScript 実装。
特徴
Gemini API への直接呼び出しを使用します (非推奨の SDK はありません)
最新のGemini 2.0 Flashモデルをサポート
Claudeとのシームレスな統合のためにMCPプロトコルを実装
自然なやりとりのために会話の文脈を維持する
Related MCP server: Gemini MCP Server
MCPツール
テキストを生成する
サーバーから: gemini
設定可能なパラメータを持つ Gemini モデルを使用してテキストを生成します。
前提条件
Node.js 18以上
Google Gemini APIキー
タイプスクリプト
クロードデスクトップアプリ
インストール
リポジトリをクローンします。
git clone https://github.com/YOUR-USERNAME/gemini-mcp-server.git
cd gemini-mcp-server依存関係をインストールします:
npm install建てる：
npm run buildクロードデスクトップ統合
このサーバーをClaude Desktopで使用するには:
クロードデスクトップを開く
設定 > 開発者
「設定を編集」をクリック
次の構成を追加します。
"gemini": {
"command": "node",
"args": ["path\\to\\dist\\gemini_mcp_server.js"],
"env": {
"GEMINI_API_KEY": "gemini_api_key"
},
"cwd": "path\\to\\gemini-mcp-server"
}交換する：
/path/to/gemini-mcp-serverリポジトリへの絶対パスで指定します。your_api_key_hereに実際の Google Gemini API キーを入力します
これで、サーバーは Claude Desktop の MCP サーバー リストで利用できるようになります。
API実装
このサーバーは、Gemini APIエンドポイントへの直接HTTPリクエストを使用します。APIリクエストの形式はGoogleの公式ドキュメントに準拠しています。
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"}]
}]
}'テスト
サンプル スクリプトを使用して直接 API 実装をテストできます。
node dist/example_direct_api.js "Your prompt here"ライセンス
マサチューセッツ工科大学
Available Tools
1 toolgenerate_textD
| Name | Required | Description | Default |
|---|---|---|---|
| maxOutputTokens | No | ||
| prompt | Yes | ||
| stream | No | ||
| temperature | No | ||
| topK | No | ||
| topP | No |
TDQS
D1/5.0
Behavior1/5
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.
Conciseness1/5
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.
Completeness1/5
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.
Parameters1/5
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.
Purpose1/5
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.
Usage Guidelines1/5
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.
1 tool update
v1.0.0- First observed
generate_text
TDQS
D1.7/5.0
Scored across 1 tool
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count2/5
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.
Completeness1/5
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
ActivityInactive
ResponsivenessNo issues
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
- QuallaaOAuthcom.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Hosted Notion MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Related MCP Servers
- 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.7144 npm12MIT
- 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.246 npm4Apache 2.0