E
eyvant/spm
A simple, cross-platform manager for native system services.
updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · eyvant/spm · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
eyvant/spm;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# SPM
Excerpted from the repository README (abridged)
A simple, cross-platform manager for native system services.
SPM provides a unified command-line interface for managing native system services across Windows, Linux, and macOS.
It works with each operating system's native service manager:
Linux: systemd
macOS: launchd
Windows: Windows Services
SPM aims to make service management consistent, simple, and intuitive across platforms.
### Built for coding agents
Coding agents such as Claude Code, Codex, and Cursor often start dev servers and
workers with & or nohup. Those processes die or become orphans when the
session ends, and their output is lost. With spm, an agent starts them as real
native services instead: they keep running, restart on crash and at login, and
their logs stay readable through spm logs or the built-in MCP server.
bash
claude plugin marketplace add eyvant/spm && claude plugin install spm@eyvant-spm
codex mcp add spm -- spm mcp
Install spm itself first (see Install). See
Agent and MCP integration for every client.
Under the hood, Linux uses systemd and journald, macOS uses launchd LaunchAgents or LaunchDaemons, and Windows uses per-user supervisors with Startup integration or native SCM services for system scope.
> User services do not require elevation. Use --system explicitly when a service must run at the machine level.
## Install
Install the latest release on Linux or macOS:
bash
curl -fsSL https://raw.githubusercontent.com/eyvant/spm/main/install.sh | sh
The installer verifies the release checksum, installs spm to ~/.local/bin, and installs completion for the shell named by $SHELL when it is Bash, Zsh, or Fish. Make sure ~/.local/bin is in PATH.
Choose a completion shell explicitly, or skip completion installation:
bash
curl -fsSL https://raw.githubusercontent.com/eyvant/spm/main/install.sh | sh -s -- --completion bash
curl -fsSL https://raw.githubusercontent.com/eyvant/spm/main/install.sh | sh -s -- --no-completion
The SPM_COMPLETION environment variable also accepts auto, bash, zsh, fish, or none.
On Windows, run PowerShell:
powershell
irm https://github.com/eyvant/spm/releases/latest/download/install.ps1 | iex
The Windows installer verifies the release checksum, installs spm.exe under
%LOCALAPPDATA%\Programs\spm, adds it to the user PATH, and installs dynamic
PowerShell completion. Use install.ps1 -NoCompletion or -NoPath when needed.
Uninstall SPM on Linux or macOS:
bash
curl -fsSL https://raw.githubusercontent.com/eyvant/spm/main/install.sh | sh -s -- --uninstall
Uninstall SPM on Windows:
powershell
& ([scriptblock]::Create((irm https://github.com/eyvant/spm/releases/latest/download/install.ps1))) -Uninstall
The uninstallers remove the executable, installed shell completion, and—on
Windows—the PowerShell profile entry and user PATH entry. They do not delete
managed services or their data. If services still exist, uninstall stops and
asks you to delete them first (spm delete all --yes, and sudo spm --system
delete all --yes when applicable); use --force or -Force only when you
intentionally want to leave those services behind.
Install a specific version:
bash
curl -fsSL https://raw.githubusercontent.com/eyvant/spm/main/install.sh | \
sh -s -- --version v0.1.0
SPM provides a unified command-line interface for managing native system services across Windows, Linux, and macOS.
It works with each operating system's native service manager:
Linux: systemd
macOS: launchd
Windows: Windows Services
SPM aims to make service management consistent, simple, and intuitive across platforms.
### Built for coding agents
Coding agents such as Claude Code, Codex, and Cursor often start dev servers and
workers with & or nohup. Those processes die or become orphans when the
session ends, and their output is lost. With spm, an agent starts them as real
native services instead: they keep running, restart on crash and at login, and
their logs stay readable through spm logs or the built-in MCP server.
bash
claude plugin marketplace add eyvant/spm && claude plugin install spm@eyvant-spm
codex mcp add spm -- spm mcp
Install spm itself first (see Install). See
Agent and MCP integration for every client.
Under the hood, Linux uses systemd and journald, macOS uses launchd LaunchAgents or LaunchDaemons, and Windows uses per-user supervisors with Startup integration or native SCM services for system scope.
> User services do not require elevation. Use --system explicitly when a service must run at the machine level.
## Install
Install the latest release on Linux or macOS:
bash
curl -fsSL https://raw.githubusercontent.com/eyvant/spm/main/install.sh | sh
The installer verifies the release checksum, installs spm to ~/.local/bin, and installs completion for the shell named by $SHELL when it is Bash, Zsh, or Fish. Make sure ~/.local/bin is in PATH.
Choose a completion shell explicitly, or skip completion installation:
bash
curl -fsSL https://raw.githubusercontent.com/eyvant/spm/main/install.sh | sh -s -- --completion bash
curl -fsSL https://raw.githubusercontent.com/eyvant/spm/main/install.sh | sh -s -- --no-completion
The SPM_COMPLETION environment variable also accepts auto, bash, zsh, fish, or none.
On Windows, run PowerShell:
powershell
irm https://github.com/eyvant/spm/releases/latest/download/install.ps1 | iex
The Windows installer verifies the release checksum, installs spm.exe under
%LOCALAPPDATA%\Programs\spm, adds it to the user PATH, and installs dynamic
PowerShell completion. Use install.ps1 -NoCompletion or -NoPath when needed.
Uninstall SPM on Linux or macOS:
bash
curl -fsSL https://raw.githubusercontent.com/eyvant/spm/main/install.sh | sh -s -- --uninstall
Uninstall SPM on Windows:
powershell
& ([scriptblock]::Create((irm https://github.com/eyvant/spm/releases/latest/download/install.ps1))) -Uninstall
The uninstallers remove the executable, installed shell completion, and—on
Windows—the PowerShell profile entry and user PATH entry. They do not delete
managed services or their data. If services still exist, uninstall stops and
asks you to delete them first (spm delete all --yes, and sudo spm --system
delete all --yes when applicable); use --force or -Force only when you
intentionally want to leave those services behind.
Install a specific version:
bash
curl -fsSL https://raw.githubusercontent.com/eyvant/spm/main/install.sh | \
sh -s -- --version v0.1.0
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/eyvant-spm/)
- Source
- awesome · https://github.com/eyvant/spm
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.