Performance Co Pilot
Expose Performance Co-Pilot host metrics to your agent for CPU, memory, disk, network, and process troubleshooting.
Overview
Performance Co-Pilot MCP is a MCP server for the Operate phase that queries system performance metrics—CPU, memory, disk I/O, network, and processes—through PCP via stdio.
What is this MCP server?
- Query CPU, memory, disk I/O, network, and process metrics via MCP
- PyPI package pcp-mcp version 1.5.1 with stdio transport
- Configurable PCP_HOST and PCP_PORT for pmproxy
- PCP_TARGET_HOST aims collection at a specific pmcd host
- Backed by Performance Co-Pilot ecosystem (pcp-mcp on GitHub)
- Server version 1.5.1
- 3 optional PCP environment variables documented in server schema
- GitHub source: major/pcp-mcp
What problem does it solve?
When production feels slow, agents guess without live host metrics unless you manually copy dashboard or CLI output into the chat.
Who is it for?
Solo devs ops-owning Linux hosts with pmproxy/pmcd who want agent-native metric queries.
Skip if: Cloud-only teams with no PCP stack, or users who need full APM traces and SLI dashboards out of the box.
What do I get? / Deliverables
After install, your agent can pull PCP-backed performance data to narrow bottlenecks during operate and incident workflows.
- Agent-queryable CPU, memory, disk I/O, network, and process metrics from PCP
- Configurable monitoring bridge for operate-phase diagnosis
Recommended MCP Servers
Journey fit
How it compares
Host metrics MCP via Performance Co-Pilot, not application-level error tracking or synthetic uptime monitoring.
Common Questions / FAQ
Who is io.github.major/pcp for?
Builders operating their own servers who use PCP and want Claude Code or Cursor to query CPU, memory, disk, network, and process stats.
When should I use io.github.major/pcp?
Use it in Operate monitoring when diagnosing performance regressions, capacity limits, or noisy neighbor processes on monitored hosts.
How do I add io.github.major/pcp to my agent?
Install pcp-mcp from PyPI, add the stdio MCP entry, and set PCP_HOST, PCP_PORT, and PCP_TARGET_HOST to match your pmproxy and pmcd layout.