A
licenseD
qualityC
maintenanceEnables Codex to delegate implementation tasks to Kimi Code while managing server lifecycle and authentication automatically.
11
1
MIT
kimi-swarm-bridge
by ryanameier
Related Servers
Alternatives to kimi-swarm-bridge
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables integrating an AI-powered agile squad with MCP-compatible clients like Antigravity, Claude Desktop, and Cursor over Stdio or SSE.-
- AlicenseAqualityDmaintenanceBridges any MCP client (like Claude Code, Zed, VS Code) to any ACP coding agent, enabling multi-agent orchestration from a single chat interface.24126 npm11Apache 2.0
- AlicenseNot gradedqualityBmaintenanceBridges Kimi Code CLI to OpenAI Computer Use, enabling Kimi to control local macOS applications via MCP.7 npm7MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for cross-platform agent onboarding. Registers external agents, translates intents from LangChain, CrewAI, AutoGen, and A2A formats, and proxies cross-ecosystem transactions.MIT
- AlicenseAqualityCmaintenanceMCP server that turns Kimi K2.6 Turbo into an agentic coding assistant with tools for file operations, shell commands, and code search.42MIT
- AlicenseNot gradedqualityCmaintenanceExposes authorized ChatGPT, DeepSeek, Kimi, and Grok web sessions to agents as MCP tools, including chat and local file attachments over HTTP or stdio.7MIT
TDQS
A4.4/5.0
Scored across 14 tools
Disambiguation4/5
Tools have largely distinct purposes, but there is some overlap between discovery tools (kimi_find_recent_session vs kimi_recent_sessions) and between delegation variants (kimi_delegate_task vs kimi_delegate_and_wait). The descriptions clarify the differences and intended usage, so selection should be reliable with careful reading.
Naming Consistency5/5
All tool names follow the consistent 'kimi_' prefix + snake_case verb_noun pattern, such as kimi_delegate_task, kimi_get_handoff, and kimi_swarm_settings. No mixed conventions or inconsistent verb styles are present.
Tool Count5/5
With 14 tools, the server is well-scoped for its bridge role, covering status, delegation, monitoring, recovery, settings, and finalization. Each tool serves a distinct operational need without redundancy or bloat.
Completeness4/5
The surface covers the full lifecycle of delegating to Kimi: check readiness, delegate (async/sync), wait, retrieve handoff, review, recover after disconnect, continue, and abort. Minor gaps like a separate 'list all sessions with filtering' beyond the raw find are mitigated by kimi_recent_jobs and kimi_recent_sessions.
Maintenance
ActivityMaintained
ResponsivenessNo issues