lunge
Allows sending GraphQL queries and mutations to any GraphQL API, with support for variables, headers, and token-efficient response summarization.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@lungeSend a GET request to https://jsonplaceholder.typicode.com/todos/1"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
Related MCP server: Relay
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 |
System design, the Rust/TS split, module layout, streaming strategy, FFI boundary | |
Full feature list by protocol + cross-cutting features (auth, vars, assertions, token optimizer) | |
The MCP tool surface: names, inputs, outputs, examples | |
The declarative YAML/JSON test/collection format | |
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.
This server cannot be deployed
Maintenance
Related MCP Connectors
Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface.
Discover and call AI agents via MCP. Supports A2A agents and platform agents with async tasks.
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceAPI client with an MCP server. Your agent builds collections from your codebase, runs requests, writes e2e flows, and exports them to GitHub Actions CI automatically. Category: Developer Tools04ISC
- AlicenseNot gradedqualityDmaintenanceA keyboard-first API client that stores requests and environments as plain files, and exposes its workspace over MCP so agents can browse, send, and create requests with vault access.159 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI clients to invoke CLI-driven agent tools over Streamable HTTP, including shell execution, file operations, patching, image viewing, web search, and nested agent tasks, with permission modes and real-time progress streaming.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.MIT