
Timps Swarm
io.github.Sandeeprdy1729由 GitHub 帳號 Sandeeprdy1729 發布v2.2.3更新於 Oct 24, 2026
161 AI agents for code gen, health, AI/ML, infra, India-stack. One command.
概覽
本機 MCP 伺服器,提供 161 個專業 AI 代理,涵蓋程式開發、安全稽核、DevOps、資料與電腦健康,可平行調度。
- 可以做什麼
- 調度專業代理進行程式碼產生、審查、重構、測試以及 API 與資料庫設計
- 執行安全稽核、相依性與合規檢查,以及基礎設施與流程診斷
- 執行多步驟軟體交付流程,並把多步目標委派給平行子代理
- 產生研究、文件、監控與雲端成本相關產出
- 查詢代理群自身狀態:列出代理、列出 LLM 供應商、查看工具與核心狀態
- 執行電腦健康檢查,涵蓋系統、網路、電池、備份與隱私
- 適用情境
- 當你希望程式助理把稽核、重構、Schema 或 API 設計、多代理流程等較大任務交給本機代理群處理,而不是全在同一個對話中完成時適用。若你想在多個 IDE 中把這些代理註冊為子代理,也很合適。
- 執行需求
- 透過 npm(npx timps-swarm mcp)在本機執行,需要 Node.js。完整功能需要可存取的 FastAPI 後端(本機或透過 TIMPS_API_URL);沒有後端時 npm 代理只能轉送呼叫。需要 LLM 供應商:GEMINI_API_KEY、ANTHROPIC_API_KEY、OPENAI_API_KEY 或 GROQ_API_KEY,或透過 OLLAMA_HOST 使用本機 Ollama。可選 REDIS_URL 保存狀態、TIMPS_AUTH 啟用 API 金鑰驗證。記憶體建議至少 8 GB。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Timps Swarm,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
One install-mcp command puts 161 AI specialists into every coding tool you use — as parallel sub-agents, not just MCP tools.
[npm] [License: MIT] [Python 3.11+] [MCP Protocol] [Discord]
Quick Start · Sub-agents · 161 Agents · MCP Setup · CLI · Architecture
[TIMPS Swarm Parallel Agent Demo] 4 agents dispatched in parallel vs sequential — 3× speedup (64s vs 192s)
What it does
- Security audit any repo in 30 seconds —
npx timps-swarm audit ./finds CVEs, hardcoded secrets, and OWASP issues. No backend, no config, no API key. - 161 specialist agents in every AI tool — one
install-mcpcommand 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 viaTask(subagent_type=...). - Local-first, BYOK — runs on Ollama with zero API cost; plug in Gemini/Anthropic/OpenAI/Groq when you want more power.
- Works without the Python backend —
npm install -g timps-swarmships a Node.js MCP stdio proxy (cli/lib/mcp-proxy.js) that talks to any running FastAPI server (local or remote viaTIMPS_API_URL). The Python repo is optional.
Quick Start
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:
- Writes the
timps-swarmMCP server entry into every detected IDE config (with an explicitenv:block forwardingANTHROPIC_API_KEY,OPENAI_API_KEY,GEMINI_API_KEY,GROQ_API_KEY,TIMPS_API_URL,OLLAMA_HOST,REDIS_URL). - Writes one sub-agent
.mdfile 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):
What install actually does
install-mcp is the only command you need:
By default this writes:
- MCP server entries into 9 IDE config files (one entry per IDE, all pointing at
npx timps-swarm mcp). - 161 sub-agent
.mdfiles into~/.claude/agents/,./.claude/agents/,~/.codex/agents/(one per MCP tool) so Claude Code'sTask(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).
The killer commands
MCP integrations
Manual config snippets (all tools)
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
LLM providers
Tries providers in priority order, uses the first available one.
The 161 agents — full list
The MCP server exposes 161 specialist agents across 9 categories. Every one is also registered as a native Claude Code / Cursor / Codex sub-agent.
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.
CLI
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.
Architecture
Three transport paths converge on the same dispatch table:
- Python MCP stdio (
mcp_server/server.py) — full MCP sampling, in-process, 161 tools. Used when the Python repo is on disk. - Node.js MCP stdio proxy (
cli/lib/mcp-proxy.js) — pure stdio JSON-RPC 2.0 that proxiestools/list+tools/callto a running FastAPI server. Used when only the npm package is installed (no Python repo). - FastAPI REST + WebSocket (
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.
REST API
Full interactive docs at http://localhost:8000/docs when the server is running.
Training custom adapters
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
Hardware
Security
API key auth is off by default. Enable when sharing across a team:
Keys stored as SHA-256 hashes in ~/.timps/.secrets (chmod 600).
Contributing
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.
來源:README.md,提交 c895066
工具
0版本歷史
1- v2.2.3最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分