@mrrlin-dev/external-agents
Related Servers
Alternatives to @mrrlin-dev/external-agents
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceRoute prompts intelligently across Claude, Gemini, and GPT-4o, automatically picking the best model for every task while minimizing token cost.512 npmMIT
- AlicenseCqualityAmaintenanceRoutes coding tasks across multiple AI CLIs (Copilot, Claude Code, Gemini, etc.) with cost-aware tier routing and parallel wave orchestration.552Apache 2.0
- FlicenseNot gradedqualityAmaintenanceIntelligently routes AI tool calls (search, extract, browse) to the cheapest capable provider by default with automatic failover and audit receipts, enabling cost-effective agent workflows.2-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to delegate tasks to cheaper models via the OpenRouter API, with live pricing, cost-tier auto-selection, and policy-based delegation.24 npmMIT
- AlicenseAqualityBmaintenanceEnables agents and users to route prompts to the cheapest reachable free or paid model across providers, compare costs, list filtered models, and receive fallback chains and cached routing results without calling any LLM API.4MIT
- AlicenseAqualityAmaintenanceRoutes your AI tasks to the best available model across 20+ providers — automatically selecting based on task type, budget, and subscription pressure. Supports text, image, video, and audio with built-in cost optimization and fallback chains.60190 PyPI96MIT
TDQS
Scored across 8 tools
Most tools have distinct purposes, but list_agents and get_state both return agent status information, potentially causing confusion. The routing notes in descriptions help clarify usage, but the overlap is noticeable.
Tool names mostly follow a verb_noun pattern (e.g., pick_agents, get_stats), but 'ping' and 'dispatch' are single verbs, breaking consistency. The mix of verbs like 'list', 'get', 'probe', 'set' is acceptable but not uniform.
With 8 tools, the server is well-scoped for its purpose of managing external agents. Each tool serves a specific function without being overloaded, fitting within the ideal 3-15 range.
The tool surface covers core operations: selection, dispatch, probing, state management, credentials, and stats. Missing are batch operations or credential removal, but these are minor gaps for the described domain.