Skip to content
MCP server

pepe

Load-test a URL, ping it by phase and ramp load from an agent, within set guardrails

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, macOS, Linux
Runs
Locally
Version
0.57.0
Listing updated
2 days ago

About pepe

pepe is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

pepe is a Rust HTTP load generator with a live dashboard, and its MCP mode turns the same engine into tools an agent can call. Each call returns pepe's versioned JSON report, so an agent can run a test, ping a target phase by phase (DNS, connect, TLS, first byte, download), ramp load to find where a target stops keeping up, and compare runs.

The safety design is the point of the MCP page. Whoever starts the server sets allowed hosts, a request cap, a rate cap and a concurrency cap, checked before anything is sent; every redirect hop is checked and a tool call cannot loosen them. A dry run reports what would be sent with secrets masked. Exit codes distinguish a usage error or guardrail refusal from a crossed limit.

The README claims one thread sends 160k requests a second on an Apple M4 Pro, and states it is lighter on CPU and memory than wrk and oha.

Install

Run in a terminal

claude mcp add pepe -- uvx pepe-http

Add to claude_desktop_config.json

{
  "mcpServers": {
    "pepe": {
      "command": "uvx",
      "args": [
        "pepe-http"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "pepe": {
      "command": "uvx",
      "args": [
        "pepe-http"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

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

Add to ~/.codeium/windsurf/mcp_config.json

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

Add to your client's MCP settings (most use this shape)

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

Tools this server provides (8)

Taken from the project documentation; the running server may differ.

run
Runs a load test.
ping
Pings a target with phase timings.
ramp
Ramps load to find capacity.
api
Load-tests endpoints from an OpenAPI spec.
flow
Runs a flow of dependent requests.
replay
Replays an access log.
logs
Reads request logs.
compare
Compares runs.

What it does

Host allow-list
Targets and redirect hops must match an allowed host.
Request, rate and concurrency caps
Limits set at server start that tool calls cannot raise.
Dry run
Shows what would be sent with secrets masked, sending nothing.
Phase-split pings
Breaks each ping into DNS, connect, TLS, first byte and download.
Capacity ramp
Raises load to find where a target stops keeping up.
Versioned JSON reports
Published schema with stable field names.

Good for

  • Let an agent load-test a staging API within strict limits
  • Find the capacity of a service by ramping load
  • Compare two runs after a change
  • Diagnose where time goes in a slow request

Pricing

Open source

Prices change. Check pepe.mhaimdat.com before you buy.

pepe FAQ

Can an agent override the guardrails?

No. Flags given at server start hold for every call and a tool call cannot loosen them.

How do I install the MCP server?

Run uvx pepe-http mcp or the ghcr.io/omarmhaimdat/pepe Docker image with the mcp argument.

What do the exit codes mean?

0 as asked, 1 could not start or nothing answered, 2 usage error or guardrail refusal, 4 a limit crossed.

Is it safe to point at any site?

The docs say to load only what you are allowed to load; guardrails make that a setting.

Is pepe free?

Yes. pepe is open source, so you can use and self-host it for free.

How do I add pepe to Claude Code?

Run this command in your terminal: claude mcp add pepe -- uvx pepe-http

What are the best alternatives to pepe?

The closest alternatives to pepe are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to pepe

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ouroboros

    MCP server

    Spec-first layer that pins requirements and verifies results of AI coding agent work

    Runs locally
    • Open source
    • 6.4K GitHub stars
    • Developer tools