A
licenseNot graded
qualityC
maintenanceAn MCP server that lets any MCP-capable agent spawn and drive Claude Code sessions — effectively turning Claude Code into an orchestratable sub-agent fleet.
84 npm
MIT
agent-nero
by sanchez314c
Related Servers
Alternatives to agent-nero
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server to dynamically load Claude Code skills into AI agents565 npm14MIT
- AlicenseNot gradedqualityCmaintenanceA universal MCP server for spawning agents with any OpenAI-compatible LLM, supporting cloud and local models, and integrating with Claude Code, OpenCode, and Codex CLI.MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that injects a team of subagent interns, web search, and image generation capabilities into Claude Code using the Agy engine.MIT
- AlicenseNot gradedqualityDmaintenanceA multi-agent MCP server that enables AI coding agents (Claude Code, Codex CLI, Gemini CLI) to communicate with each other.MIT
- FlicenseNot gradedqualityCmaintenanceA local MCP server that coordinates Claude Code CLI as subagents, providing tools to spawn, message, wait for, and interrupt agents.-
TDQS
A4/5.0
Scored across 10 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: interacting with agents, managing memory, configuring, spawning, killing, resetting, and status. No two tools overlap in functionality.
Naming Consistency5/5
All tools follow the consistent prefix 'nero_' and use a verb_noun pattern (e.g., nero_spawn, nero_kill, nero_memory_read). No mixing of conventions.
Tool Count5/5
With 10 tools, the set is well-scoped for managing persistent agents and a shared memory bus. Each tool serves a necessary role without redundancy.
Completeness5/5
The tools cover the full lifecycle of agents (create, configure, interact, reset, kill) and shared memory (read, write, dump). No obvious gaps in the intended functionality.
Maintenance
ActivityInactive
ResponsivenessNo issues