MCP Gemini Server

Created By
MCP-Mirrora year ago
Mirror of
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, you need to install it via Smithery or manually set it up by cloning the project, installing dependencies, building the project, and configuring your MCP client with the server settings.

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 to optimize prompts and manage cached content.

Use cases of MCP Gemini Server?

  1. Integrating Gemini's text generation capabilities into applications.
  2. Managing conversational AI interactions with stateful chat.
  3. Handling files and caching for efficient data management in AI applications.

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.

  • Is there support for Vertex AI credentials?
    No, the server does not support Vertex AI authentication; it only works with Google AI Studio API keys.

  • How do I handle errors?
    The server returns structured errors using the MCP standard McpError type, which includes error codes and messages for troubleshooting.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago