Back to MCP directory
publicPublicdnsLocal runtime

gemini-mcp-server

一个TypeScript服务器,通过模型上下文协议将Google的Gemini Pro模型与Claude桌面端集成,使Claude用户能够访问Gemini的文字生成能力。

article

README

gemini-mcp-server

smithery badge

A TypeScript implementation of a Model Context Protocol (MCP) server that integrates with Google's Gemini Pro model.

Gemini Server MCP server

MCP Tools

generate_text

From server: gemini

Prerequisites

  • Node.js 18 or higher
  • Google Gemini API key
  • TypeScript
  • Claude Desktop app

Installation

Installing via Smithery

To install Gemini MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @georgejeffers/gemini-mcp-server --client claude

Manual Installation

  1. Clone the repository:
git clone https://github.com/GeorgeJeffers/gemini-mcp-server.git
cd gemini-mcp-server
  1. Install dependencies:
npm install
  1. Build:
npm run build

Claude Desktop Integration

To use this server with Claude Desktop:

  1. Open Claude Desktop
  2. Go to Settings > Developer
  3. Click "Edit Config"
  4. Add the following configuration:
{
  "name": "gemini",
  "command": "node",
  "args": ["dist/gemini_mcp_server.js"],
  "env": {
    "GEMINI_API_KEY": "your_api_key_here"
  },
  "cwd": "/path/to/mcp-gemini-server"
}

Replace:

  • /path/to/mcp-gemini-server with the absolute path to where you cloned this repository
  • your_api_key_here with your actual Google Gemini API key

The server will now be available in Claude Desktop's MCP server list.

License

MIT

Author

GeorgeJeffers

READY-TO-PASTE CONFIG

MCP client config generator

Choose your client, fill the required environment variables, then copy a config generated from this server's published metadata

terminal
data_object

This entry does not contain a standard command or remote URL, so a safe client config cannot be generated automatically

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client