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.

概覽

AI 產生的概覽

本機 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。
安裝前請注意
安裝指令會寫入多個 IDE 設定檔,並在使用者目錄與專案目錄產生 161 個子代理檔案;建議先用 dry-run 預覽,並以 uninstall 還原。它會把 API 金鑰(ANTHROPIC_API_KEY、OPENAI_API_KEY、GEMINI_API_KEY、GROQ_API_KEY)轉送進這些設定檔,金鑰可能以明文保存。代理呼叫會把程式碼與提示傳送給所選的 LLM 供應商,包括遠端服務。API 金鑰驗證預設關閉;若把 TIMPS_API_URL 指向遠端伺服器,工具呼叫會離開本機。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Timps Swarm,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

[TIMPS Swarm]

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-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=...).
  • 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-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.

Quick Start

bash
npm i -g timps-swarm

Hand this repo to any coding agent and it will set itself up. SETUP.md is 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 the timps-swarm MCP server for whatever tool it's running in, and starts dispatching the 161 specialist agents in parallel.

Then wire it into your coding agents:

bash
npx timps-swarm install-mcp

install-mcp auto-detects every AI tool on your machine and:

  1. Writes the 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).
  2. Writes one sub-agent .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):

bash
npx timps-swarm audit ./          # security scan any repo — works immediately

What install actually does

install-mcp is the only command you need:

bash
npx timps-swarm install-mcp                  # default: configure all detected toolsnpx timps-swarm install-mcp --no-sub-agents  # MCP config only, skip the .md filesnpx timps-swarm install-mcp --tool cursor    # configure one toolnpx timps-swarm install-mcp --dry-run        # preview without writingnpx timps-swarm uninstall-mcp                # remove all of the above

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 .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).


The killer commands

bash
# Security audit — secrets + CVEs + SAST, no backend, no API keynpx timps-swarm audit ./
# Full 10-agent SDLC pipeline on any codebasenpx timps-swarm fix ./src --language python
# Generate a complete OpenAPI spec from plain Englishnpx timps-swarm api-design "billing API with metered usage and Stripe webhooks"
# Design a DB schema with DDL, ER diagram, and migrationsnpx timps-swarm db-design "multi-tenant SaaS with usage-based billing"
# Diagnose your machine (12 specialist agents)npx timps-swarm health

MCP integrations

bash
npx timps-swarm install-mcp            # auto-detect and configure all installed toolsnpx timps-swarm install-mcp --tool cursor    # single tool onlynpx timps-swarm install-mcp --dry-run        # preview without writing files
ToolConfig 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)
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

json
{  "mcpServers": {    "timps-swarm": {      "command": "npx",      "args": ["timps-swarm", "mcp"],      "env": {        "GEMINI_API_KEY": "...",        "ANTHROPIC_API_KEY": "..."      }    }  }}

Cursor / Windsurf / Gemini CLI / Codex CLI / Amp — same format as above, different path.

VS Code / Cline / Roo Code / GitHub Copilot — .vscode/mcp.json

json
{  "mcp": {    "servers": {      "timps-swarm": { "type": "stdio", "command": "npx", "args": ["timps-swarm", "mcp"] }    }  }}

Continue — ~/.continue/config.json

json
{ "mcpServers": [{ "name": "timps-swarm", "command": "npx", "args": ["timps-swarm", "mcp"] }] }

Aider — ~/.aider.conf.yml

yaml
mcp-servers:  timps-swarm:    command: npx    args: [timps-swarm, mcp]    type: stdio

Zed — ~/.config/zed/settings.json

json
{  "assistant": {    "mcp_servers": {      "timps-swarm": { "command": "npx", "args": ["timps-swarm", "mcp"] }    }  }}

Goose — ~/.config/goose/config.yaml

yaml
extensions:  - name: timps-swarm    type: stdio    cmd: npx timps-swarm mcp    enabled: true

GitHub Actions — reusable workflow

yaml
jobs:  generate:    uses: Sandeeprdy1729/timps-swarm/.github/workflows/timps-swarm.yml@main    with:      task: "Build a microservice for JWT authentication"      language: python    secrets:      GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}

LLM providers

Tries providers in priority order, uses the first available one.

PriorityProviderEnv varNotes
1MCP Sampler(auto)Uses the host tool's model
2Gemini 2.5 FlashGEMINI_API_KEYRecommended — fast + generous free tier
3Anthropic ClaudeANTHROPIC_API_KEYBest for complex reasoning
4OpenAI GPT-4oOPENAI_API_KEY
5Groq Llama 3.3 70BGROQ_API_KEYFastest API inference
6Ollama(auto-detected)Fully offline, no API key
7TIMPS-Coder 0.5B(built-in)Always available
bash
export GEMINI_API_KEY=...      # free tier, fastest startexport ANTHROPIC_API_KEY=...   # optional

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.

CategoryCountExamples
Priority68research_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 Diagnostics51dependency_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 Health12system_optimizer, file_organizer, environment_doctor, security_guard, network_medic, battery_analyst, update_manager, log_interpreter, privacy_cleaner, media_librarian, backup_sentinel, context_switcher
Developer Workflow12issue_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 Worker7inbox_gatekeeper, meeting_condenser, research_scout, trend_monitor, data_wrangler, competitor_tracker, agri_commodity_forecaster
Meta6list_agents, dispatch, full_checkup, list_providers, connect_tools, tool_status
Context / Kernel3context_briefing, delegate, kernel_status
SDLC Pipeline1run_task (the 10-node LangGraph orchestrator: PM → Architect → Code → Review → QA → Security → Perf → Docs → DevOps)
bash
# Trigger the full SDLC pipelinepython3 give_work.py "Build a rate-limited REST API for user authentication"# PM → Architect → Code → Review → QA → Security → Perf → Docs → DevOps
# Run a computer health checkupnpx timps-swarm healthpython3 give_work.py "My laptop fan is always running"
# Delegate a multi-step goalnpx timps-swarm delegate "fix the auth bug and ensure 80% test coverage"
# Call any of the 161 directly from the CLInpx timps-swarm mcp   # then use any MCP client

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_batch for parallel delegation. The src/tool_connectors module has a separate TOOLS dict (24 IDE config shortcuts — claude_code, cursor, etc.) used at runtime by timps_connect_tools and timps_tool_status; those are not part of the 161.


CLI

bash
npm install -g timps-swarm   # or: npx timps-swarm <command>
COMMANDS  audit <path>           Security audit — secrets + CVEs + SAST (works offline)  fix <path>             Run the full 10-agent SDLC pipeline  research <topic>       Research a topic before writing code  api-design <desc>      Generate an OpenAPI 3.1 spec from plain English  db-design <desc>       Design a database schema with DDL + ER diagram  n8n <desc>             Generate a complete n8n workflow JSON  refactor [path]        Detect code smells + produce refactored version  test-data <schema>     Generate realistic seed / fixture data  monitor <service>      Prometheus + Grafana + alerting config  ui <desc>              UI component spec + code + accessibility audit  cost <arch>            Cloud cost estimate + savings recommendations  critique <content>     Score output 1-10, auto-improve until threshold  health                 Computer health checkup (12 agents)  providers              Show configured LLM providers  install-mcp            Auto-configure TIMPS in 9 AI tools + 161 sub-agents  uninstall-mcp          Remove the MCP config and 161 sub-agent .md files  start [--repo <path>]  Start the TIMPS Swarm API server (port 8000)  mcp   [--repo <path>]  Start the MCP stdio server (Python or Node.js fallback)
FLAGS (install-mcp)  --tool <id>            Only configure one IDE (claude-code, cursor, codex-cli, …)  --no-sub-agents        Skip writing 161 sub-agent .md files (MCP config only)  --dry-run              Preview without writing anything  --silent               Suppress output (postinstall)
ENV VARS  TIMPS_API_URL          API server URL (default http://localhost:8000)                         Set to a remote URL to point every tool call at it.  TIMPS_REPO             Explicit path to the Python repo for backend commands  GEMINI_API_KEY         Free tier — fastest start  ANTHROPIC_API_KEY      Optional  OPENAI_API_KEY         Optional  GROQ_API_KEY           Optional  OLLAMA_HOST            Default http://localhost:11434  REDIS_URL              Default redis://localhost:6379/0

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

                          User / AI coding tool                          (Claude Code, Cursor, Codex, …)                                       │              ┌────────────────────────┼────────────────────────┐              │ stdio JSON-RPC 2.0     │                        │              ▼                        ▼                        ▼  ┌──────────────────────┐   ┌──────────────────────┐   ┌────────────────────┐  │ mcp_server/server.py │   │ cli/lib/mcp-proxy.js │   │     src/main.py    │  │  Python — 161 tools, │   │  Node.js fallback    │   │  FastAPI + WS      │  │  full MCP sampling   │   │  (npm-only path)     │   │  /swarm/run,       │  │                      │   │                       │   │  /agents/*,        │  │                      │   │                       │   │  /mcp/tools,       │  │                      │   │                       │   │  /mcp/tools/call,  │  │                      │   │                       │   │  /health, /ws      │  └──────────┬───────────┘   └──────────┬───────────┘   └──────────┬─────────┘             │                          │                          │             │      TOOLS / dispatch   │   POST /mcp/tools/call    │             │ ◀───────────────────────┴──────────────────────────▶│             │                                                     │             │      mcp_server/server._TOOL_HANDLERS              │             │              (161 tools, in-process)                │             └─────────────────────────┬───────────────────────────┘                                       │                              Swarm Bridge                                       │       ┌───────────────────┬──────────┴──────────┬───────────────────┐       ▼                   ▼                     ▼                   ▼  SDLC DAG          Health Graph          Specialist Agents      Context / Kernel  (10 nodes)        (12 nodes)            (120 direct calls)     (3 nodes)       │                   │                     │                   │       └───────────────────┴─────────────────────┴───────────────────┘                                       │                                  LLM Router       ┌─────────────┬─────────────────┼─────────────┬───────────────┐       ▼             ▼                 ▼             ▼               ▼   Gemini        Anthropic         OpenAI         Groq          Ollama   2.5 Flash      Claude           GPT-4o       Llama 3.3       (local)                                                            + TIMPS-Coder 0.5B

Three transport paths converge on the same dispatch table:

  1. Python MCP stdio (mcp_server/server.py) — full MCP sampling, in-process, 161 tools. Used when the Python repo is on disk.
  2. Node.js MCP stdio proxy (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).
  3. 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

bash
curl http://localhost:8000/healthcurl http://localhost:8000/health/full   # deep check with provider status
curl -X POST http://localhost:8000/swarm/run \  -H "Content-Type: application/json" \  -d '{"request": "Fix SQL injection in my FastAPI endpoint", "language": "python"}'
curl -X POST http://localhost:8000/agents/refactor \  -d '{"code": "...", "language": "python", "goals": ["reduce_complexity"]}'
curl http://localhost:8000/providers
# MCP bridge (used by cli/lib/mcp-proxy.js)curl http://localhost:8000/mcp/tools                                       # full 161-tool cataloguecurl -X POST http://localhost:8000/mcp/tools/call \  -H "Content-Type: application/json" \  -d '{"name": "timps_list_agents", "arguments": {}}'                      # call any tool over HTTP
wscat -c ws://localhost:8000/ws   # real-time stream

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.

bash
cp my_bugs.jsonl datasets/custom/git add datasets/custom/my_bugs.jsonlgit commit -m "feat: 40 new Python async bug examples"git push origin main

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

SetupRAMNotes
Minimum8 GBOne Ollama model at a time
Recommended16 GBAll models loaded simultaneously
Fine-tuning8 GB Apple SiliconMLX on M1/M2/M3/M4

Security

API key auth is off by default. Enable when sharing across a team:

bash
TIMPS_AUTH=1 make up-localpython3 give_work.py --keygen "sandeep-laptop"   # generate key (shown once)python3 give_work.py --revoke timps-sk-xxxx       # revoke a key

Keys stored as SHA-256 hashes in ~/.timps/.secrets (chmod 600).


Contributing

PRs welcome against main. Conventional commits, please.

bash
git clone https://github.com/Sandeeprdy1729/timps-swarmcd timps-swarm && pip install -e ".[dev]"make up-local    # starts the FastAPI server on :8000

make test is 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 a tests/ directory and wire it into pyproject.toml before 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.

MIT License · Discord · npm

來源:README.md,提交 c895066

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v2.2.3最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分