Skip to main content
Glama
rlaksana

mcp-cli-gemini

by rlaksana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-cli-gemini

No user-submitted related servers found.

    Related Servers

    • Gemini CLI MCP Server

      wminson
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that wraps the Gemini CLI to provide tools for executing prompts, managing chat sessions, and accessing CLI extensions. It supports both local stdio and remote SSE transports for flexible integration with MCP clients.
      1
      -

    • gemini-cli-bridge

      chaodongzhang
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes the local Gemini CLI as an MCP stdio server, providing tools for prompting, web search, file operations, and MCP management, enabling AI clients like Codex CLI and Claude Code to interact with Gemini.
      7
      MIT

    • Gemini CLI MCP/OpenAI Bridge

      Intelligent-Internet
      A
      license
      Not graded
      quality
      F
      maintenance
      Exposes Gemini CLI's built-in tools and external MCP proxies through a unified MCP endpoint while providing an OpenAI-compatible API for Gemini models. It features configurable security modes to safely manage file system operations, web searches, and shell command execution.
      20 npm
      138
      Apache 2.0

    • mcp-consultant

      maxparez
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that interfaces with Gemini and OpenAI CLI tools to enable AI model interactions. It provides a bridge to external AI CLIs with predefined model configurations.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no risk of confusing it with another. The tool's purpose is clearly stated, so an agent can unambiguously select it.

    Naming Consistency5/5

    The single tool name 'gemini' is simple, matches the server name, and follows a consistent pattern. With only one name, there are no inconsistencies to penalize.

    Tool Count2/5

    Exposing only one tool is too few for the apparent scope, as it tries to cover queries, interactive mode, and extension management all in one. This forces the agent to rely on a single catch-all, which is impractical and not a well-structured tool set.

    Completeness2/5

    The single tool is a thin wrapper around the entire CLI, providing no first-class operations for distinct tasks. Agents must manually construct CLI commands, which is error-prone and represents a shallow API surface compared to a more complete, structured set.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources