
Timps Swarm
io.github.Sandeeprdy1729Published by GitHub account Sandeeprdy1729v2.2.3Updated Oct 24, 2026
161 AI agents for code gen, health, AI/ML, infra, India-stack. One command.
Overview
Local MCP server exposing a swarm of 161 specialist AI agents for coding, security audits, DevOps, data and health tasks, dispatched in parallel.
- What you can do
- Dispatch specialist agents for code generation, review, refactoring, testing and API or database design
- Run security audits, dependency and compliance checks, and infrastructure or pipeline diagnostics
- Run a multi-step software delivery pipeline and delegate multi-step goals to parallel sub-agents
- Generate research, documentation, monitoring and cloud cost outputs
- Inspect the swarm itself: list agents, list LLM providers, check tool and kernel status
- Run computer health checks covering system, network, battery, backups and privacy
- When to use it
- Useful when you want a coding assistant to hand off larger jobs — audits, refactors, schema or API design, multi-agent pipelines — to a local swarm instead of doing everything in one conversation. Also relevant if you want the same agents registered as sub-agents across several IDEs.
- Requirements
- Runs locally via npm (npx timps-swarm mcp) and needs Node.js. Full functionality needs a reachable FastAPI backend, either local or via TIMPS_API_URL; without it the npm proxy only forwards calls. An LLM provider is needed: GEMINI_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY or GROQ_API_KEY, or a local Ollama host via OLLAMA_HOST. Optional REDIS_URL for state and TIMPS_AUTH for API key auth. Around 8 GB RAM minimum.
Installation
In SourceWeft
- Open Timps Swarm in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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.
Source: README.md at commit c895066
Tools
0Version history
1- v2.2.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts