agent-router
Related Servers
Alternatives to agent-router
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP hosts such as Claude Desktop, Cursor, and Windsurf to call autonomous specialist agents and tools for coding, browser automation, research, media synthesis, and YouTube analysis.1MIT
- AlicenseAqualityDmaintenanceEnables multiple coding agents (Claude Code, Codex, Cursor) to discover each other's sessions, search transcripts, ask questions, and handoff tasks through a shared MCP server.54 npmMIT
- AlicenseNot gradedqualityAmaintenanceConnects AI clients such as Claude Code, Cursor, Codex, ChatGPT, Hermes, and OpenClaw to 2,000+ AI models and data APIs through a local MCP bridge, letting an agent discover, inspect, price, and run tools after a single browser-approved OAuth sign-in. Backed by a read-only catalog, run history, and rollback so calls can be audited and reverted without managing individual API keys.556,724 npmMIT
- AlicenseNot gradedqualityAmaintenanceExposes a governed suite of 38 OAuth-gated tools over one MCP endpoint, letting web-based AI chat clients read and edit files, run whitelisted shell commands, search, and use Git, SQLite, browser automation, DevTools, background tasks, ports, clipboard, notifications, and localhost services on the user's own machine. It also allows local IDEs and automation tools to connect directly over localhost for offline, low-latency access.MIT
- AlicenseNot gradedqualityCmaintenanceExposes MCP tools that let AI coding sessions running in Antigravity, Codex, and OpenCode discover each other on the same machine, send messages, and receive wakes-up with replies. Supports session-isolated addressing by agent ID or project, pending/channel inbox reading, threaded replies, and clearing of answered or failed conversations.MIT
- AlicenseNot gradedqualityBmaintenanceExposes specialized agents as MCP tools so users can manage and triage Jira tasks, analyze repositories for health and conventions, generate commit/PR/DevOps patterns, assemble reports, produce slides and infographics, and run semantic search over a knowledge base. Everything is invokable directly from inside a coding session in Claude Code, Cursor, or Claude Desktop.1MIT
TDQS
Scored across 8 tools
Most tools have clearly distinct roles: discovery (list_peers vs probe_peers), execution by transport (call_api, call_cli, route), and job inspection (list_jobs vs job_status). The main overlap is slack_api versus call_api, since Slack is itself a catalog peer reachable via call_api; the descriptions hint at this but don't draw a crisp boundary. call_cli/route are well separated by platform-vs-agent peer scope.
All names are snake_case, but the convention mixes verb-first (call_api, call_cli, list_peers, list_jobs, probe_peers) with noun-first (slack_api, job_status) and a bare verb (route). Groups like call_* and list_* are internally consistent, but there's no single predictable pattern across the set.
Eight tools is well within the sweet spot and each maps to a distinct facet: peer discovery, transport probing, three execution channels, and job listing/status. No obvious padding or redundancy beyond the Slack/API overlap.
Discovery and execution are covered, but the job lifecycle is only half present: you can list and inspect jobs yet there is no explicit create/launch, cancel, or retry operation (route opens an extension instead of launching headlessly). Peer detail (get_peer) is also absent, so agents may hit dead ends after list_peers.