io.github.thuupx/lunge

السجل الرسمي الذكاء الاصطناعي والوكلاء

Agent-native API client: execute/test REST/GraphQL/WS/SSE with assertions, extraction, collections

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

NPM package lunge-mcp
Claude Code
claude mcp add lunge -- npx -y lunge-mcp@1.3.1
إعداد JSON (Claude Desktop وCursor وVS Code)
{
    "mcpServers": {
        "lunge": {
            "command": "npx",
            "args": [
                "-y",
                "lunge-mcp@1.3.1"
            ]
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. lunge
  2. Why this exists
  3. Design pillars
  4. Documents
  5. Decisions locked in

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/Brunolunge approach
Require human clicking in a GUIAgent-native: everything is an MCP tool call
Postman is heavy, enterprise features are paywalledSmall, open, single local binary + thin MCP layer
Verbose responses blow up the LLM context windowRust core summarizes/compresses output before it reaches the agent
Collections are locked into proprietary formatsPlain YAML/JSON files, git-friendly
Separate tools per protocolOne server for REST/GraphQL/WS/SSE/gRPC

Design pillars

  1. Agent-native - designed for LLM tool calls, not human UIs.
  2. Token-efficient - every response is filtered, truncated, and summarized. Full payloads are spilled to disk and referenced by handle so the context stays small.
  3. Fast & portable - a Rust core (execution + protocols + summarization) exposed to a thin TypeScript MCP layer via napi-rs.
  4. Both ad-hoc and reusable - agents can fire one-off requests or create, save, and re-run declarative collections stored as files.

Documents

DocContents
architecture.mdSystem design, the Rust/TS split, module layout, streaming strategy, FFI boundary
features.mdFull feature list by protocol + cross-cutting features (auth, vars, assertions, token optimizer)
mcp-tools.mdThe MCP tool surface: names, inputs, outputs, examples
collection-format.mdThe declarative YAML/JSON test/collection format
roadmap.mdPhased 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.

الأسئلة الشائعة

ما هو io.github.thuupx/lunge؟

Agent-native API client: execute/test REST/GraphQL/WS/SSE with assertions, extraction, collections

كيف أثبّت io.github.thuupx/lunge؟

يعمل على جهازك. في Claude Code: claude mcp add lunge -- npx -y lunge-mcp@1.3.1. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج io.github.thuupx/lunge إلى مفتاح API؟

لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.

هل io.github.thuupx/lunge مفتوح المصدر؟

شيفرته علنية على GitHub، لكن المستودع لا يعلن ترخيصًا قياسيًا.

من يصون io.github.thuupx/lunge؟

ينشره thuupx. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.