A
licenseB
qualityA
maintenanceMCP server that lets AI models invoke CLI agents (Gemini, Codex, Claude, OpenCode) as tools — with parallel execution, retries, and structured output parsing.
1
2,074 PyPI
4
MIT
agent-link-mcp
by mikusnuz
Related Servers
Alternatives to agent-link-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that bridges coding agents (Claude Code, Codex, Gemini CLI) via ACP for pair programming, enabling agents to consult each other as tools.3-
MCP Rubber Duckofficial
AlicenseAqualityDmaintenanceAn MCP server that bridges multiple LLMs (OpenAI-compatible APIs and CLI coding agents) for collaborative debugging and diverse AI perspectives.12454 npm6MIT- AlicenseNot gradedqualityFmaintenanceEnables AI agents to communicate, coordinate, and collaborate on complex tasks through a local MCP server.3 npm8ISC
- AlicenseNot gradedqualityDmaintenanceA multi-agent MCP server that enables AI coding agents (Claude Code, Codex CLI, Gemini CLI) to communicate with each other.MIT
- AlicenseNot gradedqualityAmaintenanceA standalone MCP server that lets AI agents such as Claude Code, Gemini CLI, Codex, and Kimi CLI read, type into, and send messages to each other's terminal panes, enabling coordinated multi-agent workflows without manual copy-pasting. It talks directly to tmux, so no external dependencies or framework rewrites are needed.42 npmMIT
TDQS
A3.9/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a clear, distinct purpose: spawn, spawn multiple, list, get status, reply to clarification, kill. No overlap between get_status and list_agents, and spawn_agent vs spawn_agents are differentiated by number of agents.
Naming Consistency4/5
Most tools follow verb_noun pattern (e.g., get_status, kill_agent, list_agents, spawn_agent, spawn_agents). 'reply' is a verb-only exception, but it's a common pattern for interactive tools and does not cause confusion.
Tool Count5/5
6 tools is well within the optimal 3-15 range, covering the core operations for managing AI agent sessions without being bloated or sparse.
Completeness4/5
The tool surface covers the full agent lifecycle: spawning (solo and parallel), listing, status checking, interactive dialogue (reply), and termination. Minor gaps like retrieving results from completed agents are handled by spawn/reply outputs, so no critical missing functionality.
Maintenance
ActivityMaintained
ResponsivenessNo issues