pepe MCP Server

What the code does

We read the source, 2 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    process = subprocess.Popen([exe] + args)

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.

        path = os.path.join(OUT, name)

  while ((m = re.exec(command || ''))) out.push(m[1] ?? m[2] ?? m[3]);

        if host == "hooks.slack.com" {

      p.innerHTML = paths[(i * 2 + k) % paths.length] + "<i>" + (bad ? "503" : "200") + " " + ms + "ms</i>";

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 pepe -- uvx pepe-http

{
  "mcpServers": {
    "pepe": {
      "command": "uvx",
      "args": [
        "pepe-http"
      ]
    }
  }
}

[mcp_servers.pepe]
command = "uvx"
args = ["pepe-http"]

{
  "mcpServers": {
    "pepe": {
      "command": "uvx",
      "args": [
        "pepe-http"
      ]
    }
  }
}

{
  "servers": {
    "pepe": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "pepe-http"
      ]
    }
  }
}