Skip to content
Skills Library
Programming · Tool integration

wren-http-api

/wren-http-api

Interact with Wren Engine 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).

Repository
wren-engine ↗
Licence
Apache-2.0
Last repository change
06.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
1
HTML comments
0
URLs in SKILL.md
9
Deprecation

No signals detected. Repository changed on 06.05.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/session.sh

What it does and when to use it

Interact with Wren Engine 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).

Original author description

Interact with Wren Engine 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).

How it works

  1. Version check
  2. Overview
  3. Step 1 — Initialize a session
  4. Step 2 — Discover available tools
  5. Step 3 — Call tools
  6. Available Tools — Quick Reference
  7. Prerequisites
Original SKILL.md headings · 206 lines, 822 words
SKILL.md preview
---
name: wren-http-api
description: "Interact with Wren Engine 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)."
compatibility: "Requires a running Wren MCP server with streamable-http transport (default Docker setup). curl or any HTTP client."
license: Apache-2.0
metadata:
  author: wren-engine
  version: "1.0"
---

# Interact with Wren MCP via HTTP JSON-RPC

## Version check

Silently fetch `https://raw.githubusercontent.com/Canner/wren-engine/main/skills/versions.json`.
Compare the `wren-http-api` key with this skill's version (from the frontmatter above).
If the remote version is newer, notify the user before proceeding:

> A newer version of the **wren-http-api** skill is available.
> Update with:
> ```
> npx skills add Canner/wren-engine --skill wren-http-api --agent claude-code
> ```

Then continue with the workflow below regardless of update status.

---

## Overview

The Wren MCP server exposes a **streamable-http** endpoint that speaks **JSON-RPC 2.0** over plain HTTP POST. Any HTTP client (curl, httpx, fetch, requests) can call Wren tools without an MCP SDK.

**Base URL:** `http://localhost:9000/mcp` (default Docker setup from `wren-mcp-setup`)

All requests use:
- Method: `POST`
- Content-Type: `application/json`
- Accept: `application/json, text/event-stream`

---

## Step 1 — Initialize a session

Before calling any tool, initialize a JSON-RPC session. The server returns a `Mcp-Session-Id` header that must be included in all subsequent requests.

```bash
curl -s -D - http://localhost:9000/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-03-26",
      "capabilities": {},
      "clientInfo": { "name": "my-client", "version": "1.0" }
    }
  }'
```

**Save the `Mcp-Session-Id` header** from the response. Then complete the handshake:

```bash
curl -s http://localhost:9000/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Mcp-Session-Id: <SESSION_ID>" \
  -d '{"jsonrpc": "2.0", "method": "notifications/initialized"}'
```

> The `initialized` notification has no `id` field — it is a JSON-RPC notification, not a request.

Or run the helper script: `bash scripts/session.sh http://localhost:9000/mcp`

---

## Step 2 — Discover available tools

```bash
curl -s http://localhost:9000/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Mcp-Session-Id: <SESSION_ID>" \
  -d '{"jsonrpc": "2.0", "id": 2, "method": "tools/list"}'
```

Returns `result.tools` — an array of tool definitions with name, description, and input schema.

---

## Step 3 — Call tools

All tool calls use the `tools/call` method with this structure:

```json
{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "<tool_name>",
    "arguments": { ... }
  }
}
```

Responses arrive as **Server-Sent Events** (SSE). Parse the `data:` line:

```
event: message
data: {"jsonrpc":"2.0","id":3,"result":{"content":[{"type":"text","text":"..."}]}}
```

Extract the tool output from `result.content[0].text`. Shell shortcut:

```bash
curl -s ... | grep '^data: ' | sed 's/^data: //' | jq '.result.content[0].text'
```

See [references/response-format.md](references/response-format.md) for full response parsing and error handling details.

---

## Available Tools — Quick Reference

All arguments are passed inside `params.arguments`. See [references/tools.md](references/tools.md) for full details, argument tables, and example payloads for every tool.

| Category | Tool | Arguments | Description |
|----------|------|-----------|-------------|
| **Health** | `health_check` | — | Check engine health and configuration |
| | `is_deployed` | — | Check if MDL is deployed |
| | `get_version` | — | Get MCP server version |
| **Deploy** | `deploy` | `mdl_file_path` | Deploy MDL from a JSON file path |
| | `deploy_manifest` | `mdl` | Deploy MDL dict directly |
| | `mdl_validate_manifest` | `mdl` | Validate MDL without deploying |
| **Query** | `query` | `sql` | Execute SQL query |
| | `dry_run` | `sql` | Validate SQL without executing |
| **Metadata** | `get_manifest` | — | Get full deployed MDL |
| | `get_available_tables` | — | List model/table names |
| | `get_table_info` | `table_name` | Get table info + column names |
| | `get_column_info` | `table_name`, `column_name` | Get column detail |
| | `get_table_columns_info` | `table_columns`, `full_column_info?` | Batch column lookup |
| | `get_relationships` | — | Get all MDL relationships |
| | `get_current_data_source_type` | — | Get data source type |
| | `get_available_functions` | — | List SQL functions for data source |
| | `get_wren_guide` | — | Get usage tips |
| **Remote DB** | `list_remote_tables` | — | List tables in connected DB |
| | `list_remote_constraints` | — | List foreign key constraints |

### Example: query

```bash
curl -s http://localhost:9000/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Mcp-Session-Id: <SESSION_ID>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 10,
    "method": "tools/call",
    "params": {
      "name": "query",
      "arguments": { "sql": "SELECT * FROM orders LIMIT 5" }
    }
  }'
```

### Example: deploy_manifest

```bash
curl -s http://localhost:9000/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Mcp-Session-Id: <SESSION_ID>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 11,
    "method": "tools/call",
    "params": {
      "name": "deploy_manifest",
      "arguments": {
        "mdl": {
          "catalog": "wren",
          "schema": "public",
          "dataSource": "POSTGRES",
          "models": [],
          "relationships": [],
          "views": []
        }
      }
    }
  }'
```

---

## Prerequisites

This skill assumes the Wren MCP server is already running with **streamable-http** transport. If not set up yet, use the `wren-mcp-setup` skill or run:

```bash
docker run -d --name wren-mcp \
  -p 8000:8000 -p 9000:9000 -p 9001:9001 \
  -e ENABLE_MCP_SERVER=true \
  -e MCP_TRANSPORT=streamable-http \
  -e MCP_HOST=0.0.0.0 -e MCP_PORT=9000 \
  -e WREN_URL=localhost:8000 \
  -e MDL_PATH=/workspace/target/mdl.json \
  -v <WORKSPACE_PATH>:/workspace \
  ghcr.io/canner/wren-engine-ibis:latest
```

Configure connection info via the Web UI at `http://localhost:9001`.
Files in this package (4)
  • SKILL.md 7 KB
  • references/response-format.md 2 KB
  • references/tools.md 6 KB
  • scripts/session.sh 2 KB

Versions

The database has no other skills named wren-http-api.

Database snapshot: 13.11.2026 · package version 803bbd4fa80d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100wren-mcp-setup
    Set up Wren Engine MCP server via Docker and register it with an AI agent. Covers pulling the Docker image, running the container with docker run, mounting a workspace, configuring connection info via the Web UI (with Docker host hint), registering the MCP server in Claude Code…
  • 100wren-onboarding
    Onboard a user to Wren Engine end-to-end. Walks through environment checks, project scaffolding, connection configuration via .env, and first query. Use when: user wants to install Wren Engine, set up a new data source connection, or bootstrap a new project from scratch.…
  • 100onboarding
    Onboard a user to Wren Engine end-to-end. Walks through environment checks, project scaffolding, connection configuration via .env, and first query. Use when: user wants to install Wren Engine, set up a new data source connection, or bootstrap a new project from scratch.…
  • 100http-api-cloudbase
    CloudBase official HTTP API client guide. This skill should be used when backends, scripts, or non-SDK clients must call CloudBase platform APIs over raw HTTP instead of using a platform SDK or MCP management tool.
  • 100http-api-cloudbase
    CloudBase official HTTP API client guide. This skill should be used when backends, scripts, or non-SDK clients must call CloudBase platform APIs over raw HTTP instead of using a platform SDK or MCP management tool.
  • 100http-client-config
    Configure http client config operations. Auto-activating skill for API Integration. Triggers on: http client config, http client config Part of the API Integration skill category. Use when configuring systems or services. Trigger with phrases like "http client config", "http config", "http".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.