mcproc
A Model Context Protocol (MCP) server for comfortable background process management on AI agents.
Install / Use
claude mcp add neptaco -- npx -y github:neptaco/mcprocIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of mcproc
mcproc scores 80/100 on our quality scale, 3578th of 4,617 Development & Engineering skills we index.
Its MCP Server is 9.8 KB long, well organised into 46 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.
It has 10 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated 31 days ago, so mcproc is actively maintained.
- Our last check on 2026-10-22 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
mcproc compared with similar skills
All 4 of these similar skills score higher than mcproc; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| mcproc (this skill)by neptaco | 80 | 10 | 31d ago | MCP Server |
| taste-skillby Leonxlnx | 100 | 110.6k | today | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 109.2k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 78.9k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 69.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install mcproc?
- Run
claude mcp add neptaco -- npx -y github:neptaco/mcproc. The install tabs above show the steps for each supported agent. - Which AI agents does mcproc work with?
- It is written for Claude Code, Claude Desktop and Cursor, as a MCP Server file. Other agents that read the same format can often use it too.
- Is mcproc safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is mcproc still maintained?
- The repository was last updated 31 days ago, so mcproc is actively maintained.
Skill content
View source on GitHubmcproc
A Model Context Protocol (MCP) server for comfortable background process management on AI agents.
Overview
mcproc bridges the gap between AI agent development and traditional command-line workflows. It enables AI agents to manage long-running development processes (like dev servers, build watchers, etc.) while providing developers with full CLI access to monitor and control these same processes.
Why mcproc?
Simple AI agent-launched processes are stateless and can't manage long-running processes effectively. mcproc solves this by:
- Unified Control: No more confusion about which agent or terminal is running what - all processes are centrally managed
- Context Preservation: Logs are captured and stored, allowing AI agents to debug issues while reviewing logs from earlier
- Developer-Friendly: Full CLI access means you're never locked out of your own development environment
Key Features
- 🔄 Unified Process Management: Start and manage background processes from AI agents via MCP, then monitor them from your terminal
- 👁️ Cross-Environment Visibility: Processes started by AI agents are fully accessible via CLI and other agents, and vice versa
- 📝 Intelligent Log Management: Capture, persist, and search process logs with powerful regex patterns
- 📁 Project-Aware: Automatically groups processes by project context
- 📊 Real-time Monitoring: Follow logs in real-time from CLI while AI agents manage the processes
- 🛡️ XDG Compliant: Follows XDG Base Directory specification for proper file organization
- ⚡ Wait-for-Log: Start processes and wait for specific log patterns to ensure readiness
- 🔍 Advanced Search: Time-based filtering, context lines, and regex support for log analysis
- 🧰 Toolchain Support: Execute commands through version managers (mise, asdf, nvm, rbenv, etc.)
- 🧹 Clean Command: Stop all processes in a project with a single command
- 🌲 Process Groups: Automatic cleanup of child processes when stopping parent processes
Installation
Using Homebrew (macOS and Linux)
# Add the tap
brew tap neptaco/tap
# Install mcproc
brew install mcproc
Build from source
Prerequisites
- Rust toolchain (rustc, cargo)
- protobuf compiler:
- macOS:
brew install protobuf - Linux:
apt-get install protobuf-compiler
- macOS:
git clone https://github.com/neptaco/mcproc.git
cd mcproc
cargo build --release
# Install to PATH (optional)
cargo install --path mcproc
Usage
Setup as MCP Server
After installing mcproc, you need to register it as an MCP server with your AI assistant.
For Claude Code
# Register mcproc as an MCP server
claude mcp add mcproc mcproc mcp serve
For Other MCP Clients
Configure your MCP client by adding mcproc to your configuration:
{
"mcpServers": {
"mcproc": {
"command": "mcproc",
"args": ["mcp", "serve"]
}
}
}
Available MCP Tools
Once registered, AI agents can use these tools:
start_process: Start a development server or background processstop_process: Stop a running processrestart_process: Restart a processlist_processes: List all running processesget_process_logs: Retrieve process logssearch_process_logs: Search through process logs with pattern matchingget_process_status: Get detailed process information
For Developers (CLI)
While AI agents manage processes in the background, you can monitor and control them:
Recommended command: mcproc logs -f
CLI Commands
| Command | Description | Flags | Example |
|---------|-------------|-------|---------|
| 🗒️ ps | List all running processes | -s, --status <STATUS> Filter by status | mcproc ps --status running |
| 🚀 start **<NAME>** | Start a new process | -c, --cmd <CMD> Command to run<br>-d, --cwd <DIR> Working directory<br>-e, --env <KEY=VAL> Environment variables<br>-p, --project <NAME> Project name<br>--wait-for-log <PATTERN> Wait for log pattern<br>--wait-timeout <SECS> Wait timeout<br>--toolchain <TOOL> Version manager to use | mcproc start web -c "npm run dev" -d ./app |
| 🛑 stop **<NAME>** | Stop a running process | -p, --project <NAME> Project name<br>-f, --force Force kill (SIGKILL) | mcproc stop web -p myapp |
| 🔄 restart **<NAME>** | Restart a process | -p, --project <NAME> Project name | mcproc restart web |
| 📜 logs **<NAME>** | View process logs | -p, --project <NAME> Project name<br>-f, --follow Follow log output<br>-t, --tail <NUM> Number of lines to show | mcproc logs web -f -t 100 |
| 🔍 grep **<NAME>** **<PATTERN>** | Search logs with regex | -p, --project <NAME> Project name<br>-C, --context <NUM> Context lines<br>-B, --before <NUM> Lines before match<br>-A, --after <NUM> Lines after match<br>--since <TIME> Search since time<br>--until <TIME> Search until time<br>--last <DURATION> Search last duration | mcproc grep web "error" -C 3 |
| 🧹 clean | Stop all processes in project | -p, --project <NAME> Project name<br>-f, --force Force kill | mcproc clean -p myapp |
| 🎛️ daemon start | Start mcproc daemon | None | mcproc daemon start |
| 🎛️ daemon stop | Stop mcproc daemon | None | mcproc daemon stop |
| 🎛️ daemon status | Check daemon status | None | mcproc daemon status |
| 🔌 mcp serve | Run as MCP server | None | mcproc mcp serve |
| ℹ️ --version | Show version info | None | mcproc --version |
| ❓ --help | Show help message | None | mcproc --help |
Examples
# Start the daemon (if not already running)
mcproc daemon start
# View all processes (including those started by AI agents)
mcproc ps
# Follow logs in real-time
mcproc logs frontend -f
# Multi-process log streaming per project
mcproc logs -f
# Search through logs
mcproc grep backend "error" -C 5
# Stop a process
mcproc stop frontend
Example Workflow
-
AI agent starts your development server:
Agent: "I'll start the frontend dev server for you" → Uses MCP tool: start_process(name: "frontend", cmd: "npm run dev", wait_for_log: "Server running") -
You monitor it from terminal:
mcproc logs -f # See real-time logs as the server runs -
AI agent detects an error and searches logs:
Agent: "Let me check what's causing that error" → Uses MCP tool: search_process_logs(name: "frontend", pattern: "ERROR|WARN", last: "5m") -
You can see the same information:
mcproc grep frontend "ERROR|WARN" -C 3 --last 5m
Advanced Examples
# Start a process with environment variables
mcproc start api --cmd "python app.py" --env PORT=8000 --env DEBUG=true
# Wait for a specific log pattern before considering the process ready
mcproc start web --cmd "npm run dev" --wait-for-log "Server running on" --wait-timeout 60
# Search logs with time filters
mcproc grep api "database.*connection" --since "14:30" --until "15:00"
# View logs from multiple processes in the same project
mcproc ps
mcproc logs web --project myapp -t 100
# Use version managers for Node.js projects
mcproc start web --cmd "npm run dev" --toolchain nvm
mcproc start api --cmd "yarn start" --toolchain mise
# Clean up all processes in a project
mcproc clean --project myapp
# Force stop all processes in current project
mcproc clean --force
Architecture
mcproc consists of three main components:
- mcproc daemon: A lightweight daemon that manages processes and handles log persistence
- mcproc CLI: Command-line interface for developers to interact with the daemon
- MCP Server: Exposes process management capabilities to AI agents via the Model Context Protocol
File Locations (XDG Compliant)
- Config:
$XDG_CONFIG_HOME/mcproc/config.toml(defaults to~/.config/mcproc/) - Logs:
$XDG_STATE_HOME/mcproc/log/(defaults to~/.local/state/mcproc/log/) - Runtime:
$XDG_RUNTIME_DIR/mcproc/(defaults to/tmp/mcproc-$UID/)
Development
Building from Source
# Clone the repository
git clone https://github.com/neptaco/mcproc.git
cd mcproc
# Build all components
cargo build --release
# Run tests
cargo test
# Run with verbose logging
RUST_LOG=mcproc=debug cargo run -- daemon start
Project Structure
mcproc/
├── mcproc/ # CLI and daemon implementation
├── mcp-rs/ # Reusable MCP server library
├── proto/ # Protocol buffer definitions
└── docs/ # Architecture and design documentation
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
MIT License
Copyright (c) 2025 Atsuhito Machida (neptaco)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Related Skills
taste-skill
110.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
109.2kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
78.9kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
ai-job-search
69.8kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
