wren-http-api

Initialize sessions, discover tools, and call Wren MCP tools via HTTP JSON-RPC 2.0.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kubeworkz/legible --skill wren-http-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wren-http-api
Source: https://github.com/kubeworkz/legible/tree/main/wren-engine/skills/wren-http-api
Command: npx skills add https://github.com/kubeworkz/legible --skill wren-http-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, python3, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Interact with Wren MCP server via plain HTTP JSON-RPC requests — no MCP client SDK required. Covers session initialization, tool discovery, and calling all 20+ Wren tools (query, deploy, metadata, health check) using standard HTTP POST with JSON-RPC 2.0 payloads. Use when the client cannot or prefers not to use the MCP protocol directly (e.g. OpenClaw, custom HTTP clients, shell scripts, or any environment without an MCP SDK).

Core Features & Use Cases

  • Initialize a JSON-RPC session and discover available tools on the Wren MCP server.
  • Call tools (query, deploy, metadata, health_check) via the tools/call method using JSON-RPC 2.0 over HTTP.
  • Seamlessly integrate Wren MCP in environments without an MCP SDK or with simple HTTP clients (curl, fetch, requests) for rapid prototyping or automation.

Quick Start

Use an HTTP client to initialize a session, list available tools, and call a tool via tools/call with the required arguments.

Frequently Asked Questions about wren-http-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I call Wren MCP tools using HTTP JSON-RPC without an MCP SDK?

You can call Wren MCP tools using HTTP JSON-RPC by sending standard HTTP POST requests with JSON-RPC 2.0 payloads to initialize sessions, discover tools, and invoke methods via tools/call.

What is the best way to integrate Wren MCP in shell scripts or custom HTTP clients?

The best way to integrate Wren MCP in shell scripts or custom HTTP clients is using standard HTTP POST with JSON-RPC 2.0 payloads, bypassing the need for a dedicated MCP client SDK.

Can I use curl to initialize a session and discover tools on the Wren MCP server?

Yes, you can use curl to initialize a JSON-RPC session and discover available tools on the Wren MCP server by sending HTTP POST requests with the appropriate JSON-RPC 2.0 parameters.

Do I need python3 and jq to interact with the Wren MCP server over HTTP?

You need python3 and jq to help construct and parse JSON-RPC 2.0 payloads when interacting with the Wren MCP server over HTTP, along with curl for sending the HTTP POST requests.

When should I use HTTP JSON-RPC instead of the native MCP protocol for Wren engine?

You should use HTTP JSON-RPC instead of the native MCP protocol when working in environments without an MCP SDK, such as when using OpenClaw, custom HTTP clients, or shell scripts for automation.