Skip to main content
Glama
deenesjakoruzh
IA-Entertainment-git-organization

Gemini MCP Server

by IA-Entertainment-git-organization
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gemini-mcp-服务器

模型上下文协议 (MCP) 服务器的 TypeScript 实现，使用直接 API 调用与 Google 的 Gemini 模型集成。

特征

  • 直接调用 Gemini API（无需弃用的 SDK）

  • 支持最新的 Gemini 2.0 Flash 型号

  • 实现 MCP 协议，与 Claude 无缝集成

  • 保持对话上下文以实现自然互动

Related MCP server: Gemini MCP Server

MCP 工具

生成文本

来自服务器：gemini

使用具有可配置参数的 Gemini 模型生成文本。

先决条件

  • Node.js 18 或更高版本

  • Google Gemini API 密钥

  • TypeScript

  • 克劳德桌面应用程序

安装

  1. 克隆存储库：

git clone https://github.com/YOUR-USERNAME/gemini-mcp-server.git
cd gemini-mcp-server

  1. 安装依赖项：

npm install

  1. 建造：

npm run build

Claude 桌面集成

要将此服务器与 Claude Desktop 一起使用：

  1. 打开 Claude 桌面

  2. 前往“设置”>“开发者”

  3. 点击“编辑配置”

  4. 添加以下配置：

"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 实现

该服务器使用直接 HTTP 请求连接到 Gemini API 端点。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 tool
generate_textD
NameRequiredDescriptionDefault
maxOutputTokensNo
promptYes
streamNo
temperatureNo
topKNo
topPNo

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. 1 tool updatev1.0.0
    • First observedgenerate_text
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

Resources

Related MCP Connectors

Related MCP Servers

  • Gemini MCP Server

    georgejeffers
    A
    license
    A
    quality
    D
    maintenance
    A 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.
    7
    220 npm
    12
    MIT

  • MCP Gemini Server

    amitsh06
    F
    license
    Not graded
    quality
    D
    maintenance
    A 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.
    -

  • Gemini MCP Server

    dakrin
    A
    license
    B
    quality
    D
    maintenance
    A 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.
    2
    46 npm
    4
    Apache 2.0

Appeared in Searches