gemini-jev-bridge
Related Servers
Alternatives to gemini-jev-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Codex to delegate coding and code-review tasks to Gemini through a configurable relay using the Antigravity SDK. Supports model discovery, read-only or edit modes, and live task progress in a side panel.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex users to delegate engineering, refactoring, auditing, and test execution tasks to Google Antigravity CLI as a persistent autonomous subagent, with tools for managing sessions and running prompts.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to delegate heavy coding and image-generation work to Gemini through the Antigravity CLI using a Google AI Pro subscription instead of an API key, while Claude writes briefs, reviews results, and sends corrections. It runs jobs asynchronously in a guarded work folder, continues the same Gemini conversation for fixes, and reports status, output, and token usage back to the caller.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Antigravity to delegate concrete local coding tasks to Codex CLI with durable sessions, background execution, native chat links, and event-driven receipts.MIT
- AlicenseNot gradedqualityBmaintenanceLets Codex delegate coding and review tasks to Gemini/Antigravity, Claude Code, and DeepSeek Harness through their native SDKs, while managing connections, isolated Git worktrees, and live task progress from a local panel.1MIT
- AlicenseAqualityCmaintenanceEnables Codex to delegate bounded code analysis, review, isolated edits, multimodal research, and native image generation to supervised Antigravity workers, with queued execution, retries, and inspectable patches.232MIT
TDQS
Scored across 3 tools
The three tools have largely distinct roles: bridge_status is a readiness probe, delegate_task runs a Gemini task with a Jev review, and jev_evaluate queries Jev directly. There is mild overlap since both delegate_task and jev_evaluate involve Jev evaluation, but the descriptions make the boundaries (full delegated workflow vs. narrow standalone questions) reasonably clear.
All names use snake_case, which is good, but the structural pattern is mixed: bridge_status is noun_noun, delegate_task is verb_noun, and jev_evaluate is a namespace-prefixed noun_verb. Readable and not chaotic, but not a predictable verb_noun convention throughout.
Three tools is slightly thin but appropriate for a narrow Gemini/Jev bridge whose scope is status checking, task delegation, and evaluation. Each tool earns its place without redundancy.
The surface covers the core bridge lifecycle: check readiness, delegate a task with review, and run standalone evaluations. Minor gaps exist (e.g., no way to cancel, poll, or manage in-flight delegated tasks), but agents can work around these for the stated purpose.