List Processes
list_processesChecks whether specific services are currently running on the local machine — by process name or port. Returns running status, PID, and port for Docker, Redis, Postgres, Node, and any named service. Use when: you need to verify a dev server, database, or container runtime is up before running commands or tests. Scope: local machine only. Reads /proc or uses pgrep/lsof — no network calls. Not for: reading log output (use tail_system_logs), starting or stopping services, or checking remote hosts.
How to use list_processes
Provide only the required inputs below. Start with the smallest scope that answers the task, then review the risk properties before an agent executes the call.
Risk and execution properties
Read only: yes
Destructive: no
Idempotent: yes
Open world: no — operates locally or through configured services
Inputs
servicesarrayServices to check. Well-known names: docker, dockerd, redis, postgres, mysql, mongodb, nginx, node, python, uvicorn, celery, flower, rabbitmq, git, ssh-agent, gpg-agent, nodemon, watchman, vite, webpack, esbuild, pytest, jest, vitest, eslint, prettier, prometheus, grafana, jaeger, zipkin, opentelemetry-collector, ngrok, cloudflared, cron, vault. Also accepts custom process names or 'port:3000' to check by port. Default: all well-known services.
Default: []
include_portsbooleanIf true, also report which ports each detected process is listening on. Default: true.
Default: true
Example input
{
"services": [],
"include_ports": true
}Browse or search the full 74-tool reference to choose the smallest suitable capability.
Browse all tools →