Skip to main content
ClaudeWave

160 specialist AI agents for Claude Code, Cursor & Codex — one npm install puts them all into your IDE as MCP tools and parallel sub-agents. Local-first, BYOK, works offline with Ollama.

MCP ServersRegistry oficial1 estrellas1 forksPythonMITActualizado 1mo ago
ClaudeWave Trust Score
90/100
Verified
Passed
  • Open-source license (MIT)
  • Recently active
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 8/21/2026
Install in Claude Code / Claude Desktop
Method: NPX · timps-swarm
Claude Code CLI
claude mcp add timps-swarm -- npx -y timps-swarm
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "timps-swarm": {
      "command": "npx",
      "args": ["-y", "timps-swarm"],
      "env": {
        "GEMINI_API_KEY": "<gemini_api_key>",
        "ANTHROPIC_API_KEY": "<anthropic_api_key>"
      }
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Detected environment variables
GEMINI_API_KEYANTHROPIC_API_KEY
Casos de uso

Resumen de MCP Servers

<div align="center">

<img src="https://img.shields.io/badge/TIMPS%20SWARM-v2.2-FF6B35?style=for-the-badge&labelColor=1a1a1a" alt="TIMPS Swarm" />

**One `npm install` puts 160 AI specialists into every coding tool you use — as parallel sub-agents, not just MCP tools.**

[![npm](https://img.shields.io/badge/npm-timps--swarm-CB3837?style=flat-square&logo=npm&logoColor=white)](https://www.npmjs.com/package/timps-swarm)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=flat-square)](LICENSE)
[![Python 3.11+](https://img.shields.io/badge/Python-3.11+-3776AB?style=flat-square&logo=python&logoColor=white)](https://python.org)
[![MCP Protocol](https://img.shields.io/badge/Protocol-MCP-7C3AED?style=flat-square)](https://modelcontextprotocol.io)
[![Discord](https://img.shields.io/badge/Discord-Join%20Community-5865F2?style=flat-square&logo=discord&logoColor=white)](https://discord.gg/MmsTNm8WF6)

[Quick Start](#quick-start) · [Sub-agents](#what-install-actually-does) · [160 Agents](#the-160-agents) · [MCP Setup](#mcp-integrations) · [CLI](#cli) · [Architecture](#architecture)

</div>

---

![TIMPS Swarm Parallel Agent Demo](demo/swarm-demo.gif)
*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.
- **160 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
```

Postinstall 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 — 160 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 tools
npx timps-swarm install-mcp --no-sub-agents  # MCP config only, skip the .md files
npx timps-swarm install-mcp --tool cursor    # configure one tool
npx timps-swarm install-mcp --dry-run        # preview without writing
npx 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`).
- **160 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 key
npx timps-swarm audit ./

# Full 10-agent SDLC pipeline on any codebase
npx timps-swarm fix ./src --language python

# Generate a complete OpenAPI spec from plain English
npx timps-swarm api-design "billing API with metered usage and Stripe webhooks"

# Design a DB schema with DDL, ER diagram, and migrations
npx 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 tools
npx timps-swarm install-mcp --tool cursor    # single tool only
npx timps-swarm install-mcp --dry-run        # preview without writing files
```

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

<details>
<summary>Manual config snippets (all tools)</summary>

`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 }}
```

</details>

---

## LLM providers

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 |

```bash
export GEMINI_API_KEY=...      # free tier, fastest start
export ANTHROPIC_API_KEY=...   # optional
```

---

<details>
<summary><strong>The 160 agents — full list</strong></summary>

The MCP server exposes **160 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_m
ai-agentsclaude-codecursorllmmcpmcp-servermodel-context-protocolmulti-agentsswarm-intelligence

Lo que la gente pregunta sobre timps-swarm

¿Qué es Sandeeprdy1729/timps-swarm?

+

Sandeeprdy1729/timps-swarm es mcp servers para el ecosistema de Claude AI. 160 specialist AI agents for Claude Code, Cursor & Codex — one npm install puts them all into your IDE as MCP tools and parallel sub-agents. Local-first, BYOK, works offline with Ollama. Tiene 1 estrellas en GitHub y su última actualización registrada es del 2026-06-23.

¿Cómo se instala timps-swarm?

+

Puedes instalar timps-swarm clonando el repositorio (https://github.com/Sandeeprdy1729/timps-swarm) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar Sandeeprdy1729/timps-swarm?

+

Nuestro agente de seguridad ha analizado Sandeeprdy1729/timps-swarm y le ha asignado un Trust Score de 90/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene Sandeeprdy1729/timps-swarm?

+

Sandeeprdy1729/timps-swarm es mantenido por Sandeeprdy1729. La última actividad registrada en GitHub es del 2026-06-23, con 0 issues abiertos.

¿Hay alternativas a timps-swarm?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega timps-swarm en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: Sandeeprdy1729/timps-swarm
[![Featured on ClaudeWave](https://claudewave.com/api/badge/sandeeprdy1729-timps-swarm)](https://claudewave.com/repo/sandeeprdy1729-timps-swarm)
<a href="https://claudewave.com/repo/sandeeprdy1729-timps-swarm"><img src="https://claudewave.com/api/badge/sandeeprdy1729-timps-swarm" alt="Featured on ClaudeWave: Sandeeprdy1729/timps-swarm" width="320" height="64" /></a>

Más MCP Servers

Alternativas a timps-swarm