Performance Co-Pilot MCP Server

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      - name: Update server.json version
        run: |
          VERSION=${{ needs.release.outputs.version }}

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add pcp -- uvx pcp-mcp

{
  "mcpServers": {
    "pcp": {
      "args": [
        "pcp-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.pcp]
command = "uvx"
args = ["pcp-mcp"]

{
  "mcpServers": {
    "pcp": {
      "args": [
        "pcp-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "pcp": {
      "args": [
        "pcp-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: PCP_HOST (pmproxy host), PCP_PORT (pmproxy port), PCP_TARGET_HOST (Target pmcd host to monitor). The author declared them in the registry entry; get the values from the project itself.