原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Timps Swarm

作者:Sandeeprdy1729版本 2.2.3i★ –i在你的电脑上运行
注册名称io.github.Sandeeprdy1729/timps-swarm

安装

概览

作者提供的说明(英文原文)

161 AI agents for code gen, health, AI/ML, infra, India-stack. One command.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 诊所与健康
  • 你需要填写:GEMINI_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY, GROQ_API_KEY

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: GEMINI_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY, GROQ_API_KEY, OLLAMA_HOST, TIMPS_MODEL_PATH, TIMPS_MAX_AGENT_WORKERS, REDIS_URL, TIMPS_AUTH, LOG_LEVEL

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "timps-swarm": {
      "command": "npx",
      "args": [
        "-y",
        "timps-swarm"
      ],
      "env": {
        "GEMINI_API_KEY": "your-value",
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value",
        "GROQ_API_KEY": "your-value",
        "OLLAMA_HOST": "your-value",
        "TIMPS_MODEL_PATH": "your-value",
        "TIMPS_MAX_AGENT_WORKERS": "your-value",
        "REDIS_URL": "your-value",
        "TIMPS_AUTH": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add timps-swarm --env GEMINI_API_KEY=your-value --env ANTHROPIC_API_KEY=your-value --env OPENAI_API_KEY=your-value --env GROQ_API_KEY=your-value --env OLLAMA_HOST=your-value --env TIMPS_MODEL_PATH=your-value --env TIMPS_MAX_AGENT_WORKERS=your-value --env REDIS_URL=your-value --env TIMPS_AUTH=your-value --env LOG_LEVEL=your-value -- npx -y timps-swarm

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "timps-swarm": {
      "command": "npx",
      "args": [
        "-y",
        "timps-swarm"
      ],
      "env": {
        "GEMINI_API_KEY": "your-value",
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value",
        "GROQ_API_KEY": "your-value",
        "OLLAMA_HOST": "your-value",
        "TIMPS_MODEL_PATH": "your-value",
        "TIMPS_MAX_AGENT_WORKERS": "your-value",
        "REDIS_URL": "your-value",
        "TIMPS_AUTH": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "timps-swarm": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "timps-swarm"
      ],
      "env": {
        "GEMINI_API_KEY": "your-value",
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value",
        "GROQ_API_KEY": "your-value",
        "OLLAMA_HOST": "your-value",
        "TIMPS_MODEL_PATH": "your-value",
        "TIMPS_MAX_AGENT_WORKERS": "your-value",
        "REDIS_URL": "your-value",
        "TIMPS_AUTH": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • GEMINI_API_KEY 机密 env
    Gemini API key (recommended free tier)
  • ANTHROPIC_API_KEY 机密 env
    Anthropic API key
  • OPENAI_API_KEY 机密 env
    OpenAI API key
  • GROQ_API_KEY 机密 env
    Groq API key
  • OLLAMA_HOST env
    Ollama host URL
  • TIMPS_MODEL_PATH env
    TIMPS model path for Ollama
  • TIMPS_MAX_AGENT_WORKERS env
    Max concurrent agent workers
  • REDIS_URL env
    Redis URL for state persistence
  • TIMPS_AUTH env
    Enable API key authentication
  • LOG_LEVEL env
    Log level (DEBUG, INFO, WARNING, ERROR)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 Sandeeprdy1729 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“诊所与健康”中的其他服务器比较i

  • 星标数多于此分类中其他 1031 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1031 个服务器的 30% 更新
  • 基础检查结果等于或优于此分类中其他 1031 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Timps Swarm 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:GEMINI_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY, GROQ_API_KEY

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(2.2.3)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Mirobody, FHIR MCP Server, Google Health MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Mirobody

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

作者:thetahealth正在增长↓ 290/周★ 1408昨天更新

在你的电脑上运行✓ thetahealth.ai

FHIR MCP Server

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

作者:wso2正在增长↓ 823/周★ 13711天前更新

在你的电脑上运行

Google Health MCP

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

作者:davidmosiah正在增长↓ 1024/周★ 794个月前更新

在你的电脑上运行

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

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

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:

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

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

What install actually does

install-mcp is the only command you need:

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

# 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

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

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

{

"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

{

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

Continue — ~/.continue/config.json

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

Aider — ~/.aider.conf.yml

mcp-servers:

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

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

{

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

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

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

GitHub Actions — reusable workflow

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
export GEMINI_API_KEY=...      # free tier, fastest start

export 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)
# Trigger the full SDLC pipeline

python3 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 checkup

npx timps-swarm health python3 give_work.py "My laptop fan is always running"

Delegate a multi-step goal

npx timps-swarm delegate "fix the auth bug and ensure 80% test coverage"

Call any of the 161 directly from the CLI

npx 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_

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx