Best for
- Developers familiar with Claude Code, the Claude Agent SDK, or multi-agent workflows
- Teams needing self-learning routing, swarm coordination, and project-level code analysis
- Users building agent applications with the TypeScript API
A
Agentic-Flow
Community
Self-learning multi-agent orchestration for Claude Code.
GitHub source repository ↗
42FMRS · D
A developer-tools MCP service profile based solely on the supplied README. It is suited to Claude Code workflows involving agent routing, swarms, learning memory, and development automation. No server manifest was provided, so the transport and complete tool inventory cannot be confirmed; alpha status, permissions, and licensing should be verified before deployment.
Agentic-Flow v2 is a Node.js and TypeScript framework for AI-agent orchestration. Its README claims 66 self-learning agents, 213 MCP tools, multi-agent swarms, memory and vector search, task routing, background workers, and Claude Code integration.
Tools
swarm_init
Initializes multi-agent swarm coordination.
agent_spawn
Creates an agent.
task_orchestrate
Orchestrates task execution.
memory_usage
Views or manages memory usage.
neural_train
Performs neural learning or training operations.
neural_patterns
Processes neural patterns.
github_repo_analyze
Analyzes a GitHub repository.
github_pr_manage
Manages or reviews a GitHub pull request.
benchmark_run
Runs performance benchmarks.
bottleneck_analyze
Analyzes performance bottlenecks.
token_usage
Reports token usage.
Setup
Requires Node.js 18+ and npm 8+. Install with npm install agentic-flow@alpha, then start the MCP service with npx agentic-flow@alpha mcp start. You can also run npx agentic-flow init to initialize a project, followed by hooks pretrain and hooks build-agents. The README provides a Claude Code mcpServers configuration example.
claude_desktop_config.json
{"mcpServers":{"agentic-flow":{"command":"npx","args":["agentic-flow@alpha","mcp","start"]}}}
Fit and risk
Not for
- Users who only need one simple MCP tool
- Environments that do not permit project-level command execution or codebase access
- Production environments requiring a verified stable release rather than an alpha version
Required permissions
- Access to project files and file structure for initialization, pretraining, code analysis, and edit-related hooks
- Execution of npm, npx, build, test, and other user-triggered shell commands
- Git history access during pretraining, plus repository or pull-request access when GitHub tools are used
- Permission for the MCP client to start the local npx-configured service
Risks and side effects
- The README calls the project production-ready, but installation examples and the roadmap still use alpha releases; stability should be verified
- Self-learning memory may store project-related task inputs, outputs, scores, critiques, and token data
- Agents and background workers may perform broad code analysis, command execution, or automation
- Performance, accuracy, and cost-saving figures are project-reported claims and are not independently verified by the supplied material
- Repository metadata lists the license as unknown, while the README claims MIT; verify the repository LICENSE before use
Troubleshooting
- Confirm Node.js 18 or newer and npm 8 or newer
- Confirm agentic-flow@alpha is installed and run commands from the repository root or target project
- Check the generated .claude/settings.json and its mcpServers command and arguments
- For source installation, run npm run build or npm test to check the setup
- For native acceleration, verify that @ruvector/attention rebuilt successfully; the README also describes WASM and JavaScript fallbacks
Use cases
Task routing and software development in Claude Code projects
Parallel code review, testing, and CI/CD automation
Enterprise document processing, search, and workflow automation
Research analysis and multi-agent collaboration
Supported clients
Claude CodePartial support