MCP Gemini Server

Created By
bsmi021a year ago
This project provides a dedicated MCP (Model Context Protocol) server that wraps the @google/genai SDK. It exposes Google's Gemini model capabilities as standard MCP tools, allowing other LLMs (like Cline) or MCP-compatible systems to leverage Gemini's features as a backend workhorse.
Overview

What is MCP Gemini Server?

MCP Gemini Server is a dedicated server that wraps the @google/genai SDK, exposing Google's Gemini model capabilities as standard MCP tools. It allows other LLMs or MCP-compatible systems to leverage Gemini's features as a backend workhorse.

How to use MCP Gemini Server?

To use the MCP Gemini Server, clone the project, install dependencies, build the project, and configure your MCP client with the server settings. Ensure you have a valid API key from Google AI Studio.

Key features of MCP Gemini Server?

  • Core text generation capabilities (standard and streaming).
  • Function calling to execute client-defined functions.
  • Stateful chat management across multiple turns.
  • File handling for uploading, listing, retrieving, and deleting files.
  • Caching mechanisms to optimize prompts.

Use cases of MCP Gemini Server?

  1. Integrating Gemini model capabilities into various applications.
  2. Enabling advanced conversational AI features in chat applications.
  3. Managing and processing files in conjunction with AI model interactions.

FAQ from MCP Gemini Server?

  • What are the prerequisites for using MCP Gemini Server?
    You need Node.js (v18 or later) and an API Key from Google AI Studio.

  • Can I use Vertex AI credentials?
    No, the server only supports Google AI Studio API keys for file handling and caching APIs.

  • What types of errors can I expect?
    Common errors include invalid API keys, invalid parameters, and issues related to file handling.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bsmi021
Star
3
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago