GeminiSearchBridgeMCP
Facilitates the generation of up-to-the-minute responses by leveraging the Gemini API in conjunction with Google Search capabilities, necessitating integration within auxiliary AI environments such as Cline for operational deployment.
Author

Lorhlona
Quick Info
Actions
Tags
Gemini Search MCP Server
An MCP server engineered to produce replies utilizing the most current data synthesized from the Gemini API and Google Search services.
Crucial Notice: This server component cannot function independently. It mandates coupling with sophisticated AI assistants, for instance, Cline. The powerful Gemini search utility only becomes accessible once this repository is loaded into such an AI environment.
Gemini APIとGoogle検索を活用し、最新の知見に基づいた回答を生成するために設計されたMCPサーバーです。
重要なお知らせ: このMCPサーバーは単体での動作保証はありません。本機能を利用するには、Clineのような高度なAIアシスタント環境との連携が必須となります。このプロジェクトをAIアシスタントに組み込むことで、Gemini検索機能が有効化されます。
Core Capabilities
Available Tool
search- Delivers answers by consulting Gemini 2.0 intelligence fused with live Google Search results- Accepts a search query as input and outputs the synthesized response from Gemini alongside pertinent retrieved search artifacts
機能概要
ツール
search- Gemini 2.0とGoogle検索を統合して質問に回答- 検索クエリを入力として受け付け、Geminiによる応答と関連性の高い検索結果を返却します
Deployment Procedure
-
Obtain necessary dependencies: bash npm install
-
Compile the source code: bash npm run build
-
Configure requisite environment variables: Establish a file named
.envin the project's primary directory, populating it as follows:
GEMINI_API_KEY=your_api_key_here
Key Acquisition Note: Your required Gemini API credential can be procured via Google AI Studio.
Iterative Development
For continuous, automated recompilation during active development phases: bash npm run watch
Integration Guide
To integrate this functionality with the Claude Desktop application, implement the subsequent configuration block:
Windows Path: %APPDATA%/Claude/claude_desktop_config.json
{ "mcpServers": { "gemini": { "command": "node", "args": ["path/to/gemini-search-server/build/index.js"], "env": { "GEMINI_API_KEY": "your_api_key_here" } } } }
Diagnostics
As communication between MCP servers occurs over standard input/output streams (stdio), utilizing the specialized MCP Inspector is strongly advised for troubleshooting:
bash npm run inspector
The Inspector utility will furnish a specific URL enabling access to diagnostic interfaces through a web browser.
Governing License
The source code herein is distributed under the provisions of the MIT License. However, acknowledgement is required that this implementation relies upon the Google Gemini API, which is strictly governed by Google's official Terms of Service. Utilization of this MCP server necessitates adherence to both the MIT License governing our code and the stipulated terms for the Gemini API.
セットアップ手順
-
必要なパッケージのインストール: bash npm install
-
ソースコードのビルド: bash npm run build
-
環境変数の設定: プロジェクトのルートディレクトリに
.envファイルを作成し、以下の内容を記述してください:
GEMINI_API_KEY=your_api_key_here
備考: Gemini APIキーはGoogle AI Studioから入手可能です。
開発サイクル
開発中の自動的な再ビルドを有効化する場合: bash npm run watch
導入方法
Claude Desktop環境で利用可能にするには、下記の構成設定を追加してください:
Windows: %APPDATA%/Claude/claude_desktop_config.json
{ "mcpServers": { "gemini": { "command": "node", "args": ["path/to/gemini-search-server/build/index.js"], "env": { "GEMINI_API_KEY": "your_api_key_here" } } } }
デバッグ手法
MCPサーバー間の通信はstdioを介して行われるため、デバッグにはMCP Inspectorの活用を強く推奨します:
bash npm run inspector
Inspectorツールは、ウェブブラウザ経由でデバッグインターフェースへアクセスするためのURLを提供します。
ライセンス情報
本プロジェクトのソースコードはMIT Licenseに基づき公開されています。 しかしながら、本プロジェクトがGoogle Gemini APIを利用している事実は、Googleの利用規約の適用も受けることを意味します。このMCPサーバーを利用する際は、コードに対するMITライセンスと、Gemini APIに対するGoogleの規約の両方を遵守する必要があります。
WIKIPEDIA: Cloud computing is "a paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand," according to ISO. It is commonly referred to as "the cloud".
== Characteristics == In 2011, the National Institute of Standards and Technology (NIST) identified five "essential characteristics" for cloud systems. Below are the exact definitions according to NIST:
On-demand self-service: "A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider." Broad network access: "Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations)." Resource pooling: " The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand." Rapid elasticity: "Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear unlimited and can be appropriated in any quantity at any time." Measured service: "Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service. By 2023, the International Organization for Standardization (ISO) had expanded and refined the list.
== History ==
The history of cloud computing extends to the 1960s, with the initial concepts of time-sharing becoming popularized via remote job entry (RJE). The "data center" model, where users submitted jobs to operators to run on mainframes, was predominantly used during this era. This was a time of exploration and experimentation with ways to make large-scale computing power available to more users through time-sharing, optimizing the infrastructure, platform, and applications, and increasing efficiency for end users. The "cloud" metaphor for virtualized services dates to 1994, when it was used by General Magic for the universe of "places" that mobile agents in the Telescript environment could "go". The metaphor is credited to David Hoffman, a General Magic communications specialist, based on its long-standing use in networking and telecom. The expression cloud computing became more widely known in 1996 when Compaq Computer Corporation drew up a business plan for future computing and the Internet. The company's ambition was to superch
