Install

Lunge ships as an npm package. Add it to any MCP-capable client and every agent you run gets an advanced API client - execute requests, run assertions, extract variables, replay collections - no GUI, no copy-paste, no context bloat.

Option 1: npx (recommended)

The simplest setup. Your MCP client runs npx -y lunge-mcp which downloads the latest version on first use and caches it. No global install needed.

{
  "mcpServers": {
    "lunge": {
      "command": "npx",
      "args": ["-y", "lunge-mcp"]
    }
  }
}

Option 2: global install

Install once, reference the binary directly:

npm install -g lunge-mcp

Then in your MCP client config:

{
  "mcpServers": {
    "lunge": {
      "command": "lunge"
    }
  }
}

Client config file locations

Cursor - ~/.cursor/mcp.json or project .cursor/mcp.json
Windsurf - ~/.codeium/windsurf/mcp_config.json
Claude Desktop - ~/Library/Application Support/Claude/claude_desktop_config.json
Devin CLI - ~/.config/devin/config.json
VS Code - ~/.vscode/mcp.json or project .vscode/mcp.json

Verify the connection

Restart your client and ask the agent to list available tools. You should seehttp_request, graphql_request, ws_session,sse_session, inspect_response, and the rest of the surface described in MCP tools.

From source (development)

If you want to hack on Lunge itself or run a local build:

git clone https://github.com/thuupx/lunge.git
cd lunge
pnpm install
pnpm build

Then point your MCP client at the local build:

{
  "mcpServers": {
    "lunge": {
      "command": "node",
      "args": ["/absolute/path/to/lunge/packages/mcp-server/dist/index.js"]
    }
  }
}

End-to-end verification

To confirm the full pipeline locally without an MCP client, run the bundled e2e script:

pnpm build
pnpm e2e

The script runs all checks covering every shipped tool. If it passes, your build is ready to register with any MCP client.