The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Timps Swarm listing page.
One install-mcp command puts 161 AI specialists into every coding tool you use — as parallel sub-agents, not just MCP tools.
Quick Start · Sub-agents · 161 Agents · MCP Setup · CLI · Architecture
4 agents dispatched in parallel vs sequential — 3× speedup (64s vs 192s)
npx timps-swarm audit ./ finds CVEs, hardcoded secrets, and OWASP issues. No backend, no config, no API key.install-mcp command writes the MCP config for 9 IDEs (Claude Code, Cursor, Windsurf, Continue, Aider, Cline, Zed, VS Code, Gemini, Codex, Amp, Warp) and registers every agent as a native sub-agent so Claude Code / Cursor / Codex can dispatch them in parallel via Task(subagent_type=...).npm install -g timps-swarm ships a Node.js MCP stdio proxy (cli/lib/mcp-proxy.js) that talks to any running FastAPI server (local or remote via TIMPS_API_URL). The Python repo is optional.Hand this repo to any coding agent and it will set itself up.
SETUP.mdis written as an instruction set (not just docs) — when a user clones the repo and tells Claude Code, opencode, Codex, Cursor, Windsurf, or any other agent to "read SETUP.md and set me up", the agent installs the backend, registers thetimps-swarmMCP server for whatever tool it's running in, and starts dispatching the 161 specialist agents in parallel.
Then wire it into your coding agents:
install-mcp auto-detects every AI tool on your machine and:
timps-swarm MCP server entry into every detected IDE config (with an explicit env: block forwarding ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY, GROQ_API_KEY, TIMPS_API_URL, OLLAMA_HOST, REDIS_URL)..md file per TIMPS tool into ~/.claude/agents/, ./.claude/agents/, and ~/.codex/agents/.Restart your tool — 161 agents appear as MCP tools and as parallel sub-agents.
Run without installing (zero setup):
install-mcp is the only command you need:
By default this writes:
npx timps-swarm mcp)..md files into ~/.claude/agents/, ./.claude/agents/, ~/.codex/agents/ (one per MCP tool) so Claude Code's Task(subagent_type="timps_kubernetes_navigator"), Cursor Composer, and Codex can dispatch them in parallel.All writes are idempotent (re-running updates the existing file) and reversible via uninstall-mcp (which only removes the timps-swarm key and the timps-*.md files — your other config is untouched).
| Tool | Config written |
|---|---|
| Claude Code | ~/.claude/mcp.json |
| Cursor | ~/.cursor/mcp.json |
| Windsurf | ~/.windsurf/mcp.json |
| Continue | ~/.continue/config.json |
| Zed | ~/.config/zed/settings.json |
| Aider | ~/.aider.conf.yml |
| Goose | ~/.config/goose/config.yaml |
| Gemini CLI | ~/.gemini/settings.json |
| Codex CLI | ~/.codex/config.json |
| Amp | ~/.amp/mcp.json |
| Warp | ~/.warp/mcp_servers.json |
| VS Code / Cline / Copilot | .vscode/mcp.json (workspace) |
install-mcp writes the snippet below into each IDE config. The env: block forwards whichever API keys you have set in your shell; it's optional (the IDE usually inherits env, but explicit is safer for sandboxed hosts).
Claude Code — ~/.claude/mcp.json
Cursor / Windsurf / Gemini CLI / Codex CLI / Amp — same format as above, different path.
VS Code / Cline / Roo Code / GitHub Copilot — .vscode/mcp.json
Continue — ~/.continue/config.json
Aider — ~/.aider.conf.yml
Zed — ~/.config/zed/settings.json
Goose — ~/.config/goose/config.yaml
GitHub Actions — reusable workflow
Tries providers in priority order, uses the first available one.
| Priority | Provider | Env var | Notes |
|---|---|---|---|
| 1 | MCP Sampler | (auto) | Uses the host tool's model |
| 2 | Gemini 2.5 Flash | GEMINI_API_KEY | Recommended — fast + generous free tier |
| 3 | Anthropic Claude | ANTHROPIC_API_KEY | Best for complex reasoning |
| 4 | OpenAI GPT-4o | OPENAI_API_KEY | |
| 5 | Groq Llama 3.3 70B | GROQ_API_KEY | Fastest API inference |
| 6 | Ollama | (auto-detected) | Fully offline, no API key |
| 7 | TIMPS-Coder 0.5B | (built-in) | Always available |
The MCP server exposes 161 specialist agents across 9 categories. Every one is also registered as a native Claude Code / Cursor / Codex sub-agent.
| Category | Count | Examples |
|---|---|---|
| Priority | 68 | research_agent, ab_testing_agent, abdm_agent, agent_composer, browser_automation, churn_predictor, demand_forecaster, dependency_agent, digilocker_agent, dpdp_act_auditor, federated_learning, finetuning_agent, fssai_compliance_agent, gst_compliance, indiehacker_agent, model_evaluator, model_perf_monitor, podcast_show_notes_writer, prompt_injection_scanner, quantum_ready, rag_designer, rag_evaluator, red_team_agent, release_manager, sbom_generator, security_remediation, service_mesh_configurator, sprint_planning_agent, storybook_story_generator, threat_intel_analyst, upi_agent, vector_db_agent, voice_agent_designer, wearable_health_coach, web3_agent, win_loss_analyst, … |
| Expert Diagnostics | 51 | dependency_rebel, kubernetes_navigator, docker_compose_architect, pipeline_healer, compliance_auditor, incident_response_coordinator, accessibility_tester, mcp_server_generator, observability_cost_optimizer, license_compliance_scanner, container_image_scanner, adr_writer, contract_reviewer, court_case_summarizer, data_pipeline, db_migration_pilot, disaster_recovery, game_day_facilitator, git_workflow_automator, graphql_agent, iac_drift_detector, load_testing, local_rag_builder, log_pattern_analyzer, phishing_simulator, postmortem_agent, test_intelligence, visual_regression_detective, web_scraping, web_search, … |
| Computer Health | 12 | system_optimizer, file_organizer, environment_doctor, security_guard, network_medic, battery_analyst, update_manager, log_interpreter, privacy_cleaner, media_librarian, backup_sentinel, context_switcher |
| Developer Workflow | 12 | issue_triager, boilerplate_architect, pr_reviewer, dependency_sentinel, unit_test_writer, docstring_generator, log_detective, sql_optimizer, sprint_reporter, flaky_test_hunter, api_contract_auditor, content_multiplier |
| Knowledge Worker | 7 | inbox_gatekeeper, meeting_condenser, research_scout, trend_monitor, data_wrangler, competitor_tracker, agri_commodity_forecaster |
| Meta | 6 | list_agents, dispatch, full_checkup, list_providers, connect_tools, tool_status |
| Context / Kernel | 3 | context_briefing, delegate, kernel_status |
| SDLC Pipeline | 1 | run_task (the 10-node LangGraph orchestrator: PM → Architect → Code → Review → QA → Security → Perf → Docs → DevOps) |
The Self-Critic Agent is the most valuable one — it scores any output 1–10 and re-runs the originating agent until the threshold is met, closing the quality loop across the entire swarm.
The 161 includes Phase 3 (12 priority), Phase 5 (7 more), Phase 6 nextgen (21 — security/DevOps/MLOps/emerging), Phase 7 (32 — India verticals, compliance, content, sales/voice, research), and
timps_batchfor parallel delegation. Thesrc/tool_connectorsmodule has a separateTOOLSdict (24 IDE config shortcuts —claude_code,cursor, etc.) used at runtime bytimps_connect_toolsandtimps_tool_status; those are not part of the 161.
If timps-swarm mcp is invoked but no Python repo is on disk, it transparently falls back to the bundled cli/lib/mcp-proxy.js — a Node.js JSON-RPC 2.0 stdio proxy that forwards every tool call to ${TIMPS_API_URL}/mcp/tools/call. So npm install -g timps-swarm is enough to get a working MCP server, as long as a FastAPI server is reachable.
Three transport paths converge on the same dispatch table:
mcp_server/server.py) — full MCP sampling, in-process, 161 tools. Used when the Python repo is on disk.cli/lib/mcp-proxy.js) — pure stdio JSON-RPC 2.0 that proxies tools/list + tools/call to a running FastAPI server. Used when only the npm package is installed (no Python repo).src/main.py) — /swarm/run, /agents/*, /health, /ws, plus the bridge endpoints /mcp/tools (catalogue) and /mcp/tools/call (dispatch).Layer 1 — Computer Manager (src/layer1_computer_manager.py) — isolated working directories, CPU/memory/disk caps per agent.
Layer 2 — Swarm Bridge (src/layer2_swarm_bridge.py) — agent lifecycle: spawning, team formation, LangGraph DAG execution, result collection.
Layer 3 — CLI (src/layer3_swarm_cli.py) — give_work.py and the npm CLI.
Full interactive docs at http://localhost:8000/docs when the server is running.
The Code Generator uses TIMPS-Coder — a 0.5B model with 20 LoRA adapters, one per bug class. Add examples and push — GitHub Actions trains new adapters automatically.
Set HF_TOKEN and HF_REPO_ID in repo secrets. The pipeline merges your data, trains 20 adapters in parallel on Apple Silicon (MLX), benchmarks, and publishes to HuggingFace.
The 20 bug-class adapters: java_npe · java_ioob · java_concurrent · python_keyerror · python_typeerror · python_recursion · python_async · python_logic · javascript_null · javascript_scope · javascript_async · cpp_memory · cpp_bounds · go_routine · rust_borrow · sql_injection · xss_vuln · auth_bypass · performance_slow · api_design
| Setup | RAM | Notes |
|---|---|---|
| Minimum | 8 GB | One Ollama model at a time |
| Recommended | 16 GB | All models loaded simultaneously |
| Fine-tuning | 8 GB Apple Silicon | MLX on M1/M2/M3/M4 |
API key auth is off by default. Enable when sharing across a team:
Keys stored as SHA-256 hashes in ~/.timps/.secrets (chmod 600).
PRs welcome against main. Conventional commits, please.
make testis currently a no-op —tests/is empty. Existing runnable test scripts are top-level (python3 mcp_server/test_server.py,python3 test_computer_allocation.py). Add atests/directory and wire it intopyproject.tomlbefore relying on pytest.
Lint: ruff check . (configured in pyproject.toml, no make lint target). Typecheck: none configured. Python ≥ 3.10, CI pins 3.11.
Built on TIMPS-Coder — a 0.5B model fine-tuned with 20 LoRA adapters for specific bug patterns.