Skip to main content
Glama
donghae0414

Codex Gemini MCP

by donghae0414
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Codex Gemini MCP

No user-submitted related servers found.

    Related Servers

    • Mi MCP Server

      RoyserVillanueva
      A
      license
      Not graded
      quality
      C
      maintenance
      A TypeScript-based MCP server that connects with MCP clients like Claude, VS Code, and Cursor, providing tools like echo, sum, time, and customizable prompts.
      3 npm
      MIT

    • remote-mcp-server

      jspmern
      F
      license
      Not graded
      quality
      D
      maintenance
      A TypeScript-based MCP remote server with HTTP transport, token authentication, and support for tools, prompts, and resources.
      -

    • MCP-TS-DEMO

      pjqdyd
      A
      license
      D
      quality
      D
      maintenance
      A TypeScript MCP server demo supporting local Stdio and remote Streamable HTTP, demonstrating tool invocation for AI agents.
      2
      MIT

    • Orchestration MCP

      dufangshi
      F
      license
      A
      quality
      D
      maintenance
      A TypeScript MCP server for launching, tracking, and managing external coding-agent runs across local and remote backends like Codex and Claude Code. It allows top-level agents to orchestrate subagents through tools for spawning tasks, polling events, and handling interactive sessions.
      7
      2
      -

    • MCP Tools

      joehuangcoding
      A
      license
      Not graded
      quality
      D
      maintenance
      A local Model Context Protocol (MCP) server that exposes custom tools to Claude Desktop, enabling direct interaction with your local environment. It provides a framework for building and integrating custom TypeScript tools into the Claude interface.
      4 npm
      MIT
    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

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as sending prompts to a local Codex CLI, making it impossible for an agent to misselect between non-existent alternatives.

    Naming Consistency5/5

    A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare it against. The name 'ask_codex' follows a clear verb_noun pattern and stands alone without any conflicting conventions.

    Tool Count2/5

    One tool is too few for a server named 'Codex Gemini MCP', which suggests a broader scope or multiple functionalities. A single tool feels thin and limited, failing to provide a comprehensive surface for interacting with a Codex CLI beyond basic prompting.

    Completeness2/5

    The tool surface is severely incomplete for the implied domain of a Codex CLI interface. While 'ask_codex' covers basic prompting, there are obvious gaps such as configuration management, session handling, or advanced querying capabilities that would be expected in a more robust integration.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources