io.github.thuupx/lunge
Agent-native API client: execute/test REST/GraphQL/WS/SSE with assertions, extraction, collections
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
lunge-mcpclaude mcp add lunge -- npx -y lunge-mcp@1.3.1{
"mcpServers": {
"lunge": {
"command": "npx",
"args": [
"-y",
"lunge-mcp@1.3.1"
]
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
lunge
An agent-native advanced API client - execute and test REST, GraphQL, WebSocket, SSE, and (later) gRPC requests from any MCP-capable AI agent. No GUI, no manual clicking, no heavyweight desktop app. Think advanced curl, native for agents.
It is a lightweight, token-efficient alternative to Postman/Bruno for the era of AI coding agents. The agent calls tools directly; there are no humans in the loop and no bloated feature surface to pay for.
Why this exists
| Pain with Postman/Bruno | lunge approach |
|---|---|
| Require human clicking in a GUI | Agent-native: everything is an MCP tool call |
| Postman is heavy, enterprise features are paywalled | Small, open, single local binary + thin MCP layer |
| Verbose responses blow up the LLM context window | Rust core summarizes/compresses output before it reaches the agent |
| Collections are locked into proprietary formats | Plain YAML/JSON files, git-friendly |
| Separate tools per protocol | One server for REST/GraphQL/WS/SSE/gRPC |
Design pillars
- Agent-native - designed for LLM tool calls, not human UIs.
- Token-efficient - every response is filtered, truncated, and summarized. Full payloads are spilled to disk and referenced by handle so the context stays small.
- Fast & portable - a Rust core (execution + protocols + summarization) exposed to a thin TypeScript MCP layer via napi-rs.
- Both ad-hoc and reusable - agents can fire one-off requests or create, save, and re-run declarative collections stored as files.
Documents
| Doc | Contents |
|---|---|
| architecture.md | System design, the Rust/TS split, module layout, streaming strategy, FFI boundary |
| features.md | Full feature list by protocol + cross-cutting features (auth, vars, assertions, token optimizer) |
| mcp-tools.md | The MCP tool surface: names, inputs, outputs, examples |
| collection-format.md | The declarative YAML/JSON test/collection format |
| roadmap.md | Phased delivery plan from scaffolding to gRPC and CI |
Decisions locked in
- Stack: Rust core via napi-rs + TypeScript MCP layer (
@modelcontextprotocol/sdk). - Distribution: local dev tool over stdio transport (used by Cursor/Windsurf/Claude Desktop).
- Test definition: both ad-hoc agent calls and persisted declarative collections.
- MVP protocols: REST, GraphQL, WebSocket, SSE. gRPC is a later phase.
Frequently asked questions
What is io.github.thuupx/lunge?
Agent-native API client: execute/test REST/GraphQL/WS/SSE with assertions, extraction, collections
How do I install io.github.thuupx/lunge?
It runs on your machine. In Claude Code: claude mcp add lunge -- npx -y lunge-mcp@1.3.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.thuupx/lunge need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.thuupx/lunge open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.thuupx/lunge?
It is published by thuupx. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.