Skip to main content
ClaudeWave
stcmain avatar
stcmain

whats-running-mcp

Ver en GitHub

MCP server exposing live machine ground-truth (processes, listening ports, daemons, load) to agent fleets — stop guessing what's actually running.

MCP ServersRegistry oficial0 estrellas0 forksJavaScriptMITActualizado today
Install in Claude Code / Claude Desktop
Method: NPX · whats-running-mcp
Claude Code CLI
claude mcp add whats-running-mcp -- npx -y whats-running-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "whats-running-mcp": {
      "command": "npx",
      "args": ["-y", "whats-running-mcp"]
    }
  }
}
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.
Casos de uso

Resumen de MCP Servers

# whats-running-mcp

[![npm](https://img.shields.io/npm/v/whats-running-mcp)](https://www.npmjs.com/package/whats-running-mcp)
[![license](https://img.shields.io/badge/license-MIT-blue)](./LICENSE)
[![Glama](https://glama.ai/mcp/servers/stcmain/whats-running-mcp/badge)](https://glama.ai/mcp/servers/stcmain/whats-running-mcp)

**Ground truth for agent fleets.** An MCP server that tells your AI agent what is *actually* running on the machine — live agent sessions, listening TCP ports, loaded daemons, system load — read straight from the OS (`ps` / `lsof` / `launchctl` / `df`), never from docs, transcripts, or memory files.

## Why

If you run more than one coding-agent session (Claude Code, Codex, Aider…), you've seen this failure mode: an agent "health-checks" a server that died weeks ago, or confidently reports a daemon as live because an old transcript said so. Model memory is a cache with no invalidation. The OS is the source of truth.

This server started as a shell script (`whats-running`) I wrote after my own fleet of Claude Code sessions kept reporting stale state as live. Wrapping it in MCP means every session grounds itself the same way, automatically.

## Tools

| Tool | What it answers |
|---|---|
| `whats_running` | Full snapshot in one call — use at session start |
| `agent_sessions` | Which agent processes are live? Terminal-attached vs detached/orphan, with pid, uptime, and working directory |
| `listening_ports` | Is service X actually up? Every TCP LISTEN socket with owning process |
| `daemons` | What persistent services are loaded? `launchctl` (macOS, non-Apple) or systemd user services (Linux), with optional label filter |
| `system_stats` | Load average, uptime, root-disk free space |

## Install

Register with Claude Code (available in every session):

```bash
claude mcp add --scope user whats-running -- npx -y whats-running-mcp
```

Or in any MCP client config:

```json
{
  "mcpServers": {
    "whats-running": {
      "command": "npx",
      "args": ["-y", "whats-running-mcp"]
    }
  }
}
```

<details>
<summary>From source</summary>

```bash
git clone https://github.com/stcmain/whats-running-mcp.git
cd whats-running-mcp
npm install && npm run build
# then point your client at node /path/to/whats-running-mcp/dist/index.js
```

</details>

Published as [`whats-running-mcp`](https://www.npmjs.com/package/whats-running-mcp) on npm and as
`io.github.stcmain/whats-running-mcp` in the [MCP Registry](https://registry.modelcontextprotocol.io/).

## Configuration

| Env var | Default | Purpose |
|---|---|---|
| `WR_AGENT_PATTERNS` | `claude,codex,aider,cursor-agent,copilot,goose` | Comma-separated substrings that mark a process as an "agent" in `agent_sessions` |

## Design notes

- **Read-only by construction.** Every command is a fixed binary with fixed flags via `execFile` — no shell, and nothing derived from model input is ever executed. The only model-controlled inputs are a boolean and a substring filter applied in-process.
- **Local information disclosure is the point.** The model sees process names, pids, working directories, and ports of *your own machine*. Don't attach this server to an untrusted client.
- **Best-effort, never blocking.** Commands time out at 10s and degrade to empty results rather than erroring the whole snapshot.

Platform: macOS first (my daily driver), Linux best-effort (`systemd --user` in place of `launchctl`).

## Related free tools

Same idea — read-only, MIT, no telemetry — pointed at different blind spots:

- **[whats-loaded-mcp](https://github.com/stcmain/whats-loaded-mcp)** — what is consuming your agent's context *before* a session starts: skill descriptions ranked by token cost, skills installed more than once, `CLAUDE.md`/`AGENTS.md` sizes including what their imports pull in. `npx -y whats-loaded-mcp`
- **[whats-inherited-mcp](https://github.com/stcmain/whats-inherited-mcp)** — what a checkout tells your agent to do *before* you run it: instruction files, commands wired to auto-run, declared MCP servers, shipped skills. Repo strings come back labelled as data, not instructions. `npx -y whats-inherited-mcp`
- **[whats-allowed-mcp](https://github.com/stcmain/whats-allowed-mcp)** — what your agent can do *without asking you*: every settings file that contributes permission rules, which one wins, what runs unattended, and the rules your client accepts and then ignores. `npx -y whats-allowed-mcp`

## Who makes this

Built by [Shift The Culture](https://shifttheculture.media/agent-tools?utm_source=github&utm_medium=readme&utm_campaign=whats-running-mcp) — we run a one-person company on AI agents and ship the tooling we needed ourselves. This server is free and MIT-licensed, no strings.

This server is the free, standalone piece of a larger multi-agent setup. The rest of that tooling is paid:

- **[Agent Fleet Ops Kit](https://stcai.gumroad.com/l/agent-fleet-ops-kit?wanted=true&utm_source=github&utm_medium=readme&utm_campaign=whats-running-mcp)** ($29) — the other failure modes of running three or four agents on one box: two sessions editing the same checkout, a dev server nobody owns (so the agent tests a different app than it edits), and MCP servers leaked from crashed sessions that hold ports and RAM for weeks.
- **[Agent Reliability Kit](https://stcai.gumroad.com/l/agent-reliability-kit?wanted=true&utm_source=github&utm_medium=readme&utm_campaign=whats-running-mcp)** ($29) — a Stop hook and two CLIs that block a turn when an agent claims "done" against a repo, URL, or build that was never actually checked.

The server above stays free and MIT either way — it has no upsell in it, no telemetry, and no dependency on the paid kits.

## Sponsors

This server is MIT and stays MIT. There is no pro edition, no telemetry, and
nothing held back from the free build. Sponsorship is how the maintenance gets
paid for without any of that changing.

**No sponsors yet — the first slot is open.** Company sponsors get their name or
logo in this section, in the two sibling servers, and on the sponsor page.
Tiers, exactly what the placement is, and what it explicitly does not buy:
**https://shifttheculture.media/sponsor**

Individuals: https://paypal.me/ShiftTheCultureLLC — any amount, no perks, no tier.

## License

MIT © Zachary Pampu
ai-agentsclaudeclaude-codedevtoolsmcpmcp-servermodel-context-protocolobservabilitytypescript

Lo que la gente pregunta sobre whats-running-mcp

¿Qué es stcmain/whats-running-mcp?

+

stcmain/whats-running-mcp es mcp servers para el ecosistema de Claude AI. MCP server exposing live machine ground-truth (processes, listening ports, daemons, load) to agent fleets — stop guessing what's actually running. Tiene 0 estrellas en GitHub y se actualizó por última vez today.

¿Cómo se instala whats-running-mcp?

+

Puedes instalar whats-running-mcp clonando el repositorio (https://github.com/stcmain/whats-running-mcp) 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 stcmain/whats-running-mcp?

+

stcmain/whats-running-mcp aún no ha sido auditado por nuestro agente de seguridad. Revisa el repositorio original en GitHub antes de usarlo en producción.

¿Quién mantiene stcmain/whats-running-mcp?

+

stcmain/whats-running-mcp es mantenido por stcmain. La última actividad registrada en GitHub es de today, con 0 issues abiertos.

¿Hay alternativas a whats-running-mcp?

+

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

Despliega whats-running-mcp 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: stcmain/whats-running-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/stcmain-whats-running-mcp)](https://claudewave.com/repo/stcmain-whats-running-mcp)
<a href="https://claudewave.com/repo/stcmain-whats-running-mcp"><img src="https://claudewave.com/api/badge/stcmain-whats-running-mcp" alt="Featured on ClaudeWave: stcmain/whats-running-mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a whats-running-mcp