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

Gemini MCP Server

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

제미니-mcp-서버

Google의 Gemini 모델과 직접 API 호출을 사용하여 통합되는 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 키

  • 타입스크립트

  • 클로드 데스크톱 앱

설치

  1. 저장소를 복제합니다.

지엑스피1

  1. 종속성 설치:

npm install

  1. 짓다:

npm run build

Claude 데스크톱 통합

Claude Desktop과 함께 이 서버를 사용하려면:

  1. 클로드 데스크톱 열기

  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 구현

이 서버는 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"

특허

MIT

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
    197 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