gemini-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is gemini-mcp-server?

The gemini-mcp-server is a TypeScript implementation of a Model Context Protocol (MCP) server that integrates with Google's Gemini Pro model.

how to use gemini-mcp-server?

To use the gemini-mcp-server, clone the repository, install the dependencies, build the project, and configure it with the Claude Desktop app using your Google Gemini API key.

key features of gemini-mcp-server?

  • TypeScript implementation for robust development
  • Integration with Google's Gemini Pro model
  • Easy setup and configuration with Claude Desktop

use cases of gemini-mcp-server?

  1. Developing applications that require advanced AI capabilities through Google's Gemini model.
  2. Integrating AI functionalities into existing projects using the MCP protocol.
  3. Facilitating communication between different AI models and applications.

FAQ from gemini-mcp-server?

  • What are the prerequisites for using gemini-mcp-server?

You need Node.js 18 or higher, a Google Gemini API key, TypeScript, and the Claude Desktop app.

  • Is there a license for gemini-mcp-server?

Yes, it is licensed under the MIT license.

  • How can I contribute to the gemini-mcp-server project?

You can contribute by forking the repository, making your changes, and submitting a pull request.

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

Recommend Servers

View All
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.

21 hours ago