Skip to main content
Glama
jiassia

gemini2codex

by jiassia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to gemini2codex

No user-submitted related servers found.

    Related Servers

    • codex-worker-runtime

      ykanbe
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Codex to delegate bounded work to external LLMs through role-based MCP tools, with worker health checks and audit logging.
      MIT

    • Claude Codex Connector

      tejask-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude and Codex agents to delegate implementation, testing, research, or review tasks to each other through local MCP tools, while supporting persistent sessions, isolated editing workspaces, and reviewed integration. It also allows progress tracking, cancellation, model selection, and management handoff between providers.
      2
      MIT

    • personal_agent

      huanggeyu717-beep
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to delegate explicitly assigned subtasks to a local runtime that executes them with user-configured models such as DeepSeek, Qwen, or Claude. All project modifications are gated behind generated diffs and human approval before being applied.
      MIT

    • Standalone Agent Orchestrator

      muratangin187
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to delegate work to nested subagents running on Codex and Claude Code, keeping each task's session, turn history and results durable in SQLite while the main chat continues. Supports async or blocking waits, mid-session context updates, git worktree isolation, read-only-by-default permission inheritance, and cancelling whole subagent trees.
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 14 tools

    Disambiguation2/5

    There are multiple overlapping pairs: gemini_spawn_agent vs gemini_agent_submit both start Gemini work, gemini_send_message vs gemini_followup_task both communicate with an existing agent, gemini_wait_agent vs gemini_agent_status both observe progress/results, and gemini_interrupt_agent vs gemini_agent_cancel both stop work. Descriptions help distinguish agent-oriented from task-oriented flows, but an agent can easily misselect between the parallel APIs.

    Naming Consistency2/5

    All names use the gemini_ prefix and snake_case, but the action/resource ordering is inconsistent: gemini_spawn_agent, gemini_list_agents, gemini_wait_agent, and gemini_interrupt_agent use verb_noun, while gemini_agent_submit, gemini_agent_status, and gemini_agent_cancel use noun_verb. Prose tools like gemini_polish, gemini_rewrite, gemini_review, and gemini_write also break the agent/task noun pattern, making the naming scheme only partially predictable.

    Tool Count4/5

    Fourteen tools is within a reasonable range for a server covering agent lifecycle, task lifecycle, prose operations, and health checks. The count is slightly inflated by two overlapping lifecycle families, but it is not excessive for the apparent scope.

    Completeness3/5

    The surface covers agent spawn/list/message/follow-up/wait/interrupt, task submit/status/cancel, prose write/polish/rewrite/review, and health probing. However, task listing is missing, and agent lifecycle lacks an explicit get/delete or terminate operation, which can create recovery gaps if IDs are lost or stale agents accumulate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources