wren-mcp-setup

wren-mcp-setup is a skill for Claude Code from Canner/wren-engine. It costs 116 tokens per session (3,133 once invoked), scanned B, original, Apache-2.0.

A guide for running Wren Engine and its MCP server in Docker, a tool that packages software into repeatable containers. It also explains how to register the server with Claude Code or another MCP client.

In plain words
What is it for?
Use it to pull and run the Wren container, mount a workspace, configure database connections, and connect Wren to an AI agent over HTTP.
Why use it?
It turns the engine and connection setup into a repeatable local deployment and explains where the project files should be mounted.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions Claude Code; built for cline.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/me/wren-workspace.

Part of the wren plugin — 8 skills shipped together

Good fit Use it to pull and run the Wren container, mount a workspace, configure database connections, and connect Wren to an AI agent over HTTP.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Canner/wren-engine
Claude Code
/plugin install wren

Made for: Claude Code.

Or install wren, the plugin that ships this one along with the rest of its 8 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for wren-mcp-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/canner/wren-engine/wren-mcp-setup.svg)](https://agentmods.dev/skills/canner/wren-engine/wren-mcp-setup)
Your own site
<a href="https://agentmods.dev/skills/canner/wren-engine/wren-mcp-setup"><img src="https://agentmods.dev/badge/skills/canner/wren-engine/wren-mcp-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,133 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00116 $0.03133
Opus 5 $0.00058 $0.01566
Sonnet 5 $0.00023 $0.00627
Haiku 4.5 $0.00012 $0.00313

Measured 7d ago against content hash 2879ee374ba1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade B, and why

wren-mcp-setup scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Or add manually to `~/.claude/settings.json` under `mcpServers`:

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -v http://localhost:9000/mcp
skills-archive/wren-mcp-setup/SKILL.md · 372 lines

How it starts

The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set Up Wren MCP via Docker

Version check

Silently fetch https://raw.githubusercontent.com/Canner/wren-engine/main/skills/versions.json. Compare the wren-mcp-setup 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-mcp-setup skill is available. Update with:

npx skills add Canner/wren-engine --skill wren-mcp-setup --agent claude-code

Then continue with the workflow below regardless of update status.


Runs the Wren Engine ibis-server + MCP server together in a single Docker container and connects it to Claude Code (or another MCP client) over streamable-http.


Step 1 — Ask for workspace path

Ask the user:

What directory on your host machine should be mounted as the MCP workspace? This is where MDL files and YAML project directories will be read and written. (Example: ~/wren-workspace)

If the user has no preference, suggest creating a dedicated directory such as ~/wren-workspace:

mkdir -p ~/wren-workspace

Save the answer as <WORKSPACE_PATH> (use the absolute path, e.g. /Users/me/wren-workspace) for use in the next steps.


Step 2 — Prepare workspace and start the container

Check for a newer image

Before starting the container, verify whether a newer wren-engine-ibis image is available on the registry.

If the image has never been pulled (first-time setup), just pull it:

docker pull ghcr.io/canner/wren-engine-ibis:latest

If the image already exists locally, compare the local digest with the remote one to detect updates:

# Save current local digest (empty string if image not present)
LOCAL_DIGEST=$(docker inspect --format='{{index .RepoDigests 0}}' ghcr.io/canner/wren-engine-ibis:latest 2>/dev/null || echo "")

# Pull from registry (downloads only if remote digest differs)
docker pull ghcr.io/canner/wren-engine-ibis:latest

# Compare digests
NEW_DIGEST=$(docker inspect --format='{{index .RepoDigests 0}}' ghcr.io/canner/wren-engine-ibis:latest 2>/dev/null || echo "")

if [ "$LOCAL_DIGEST" != "$NEW_DIGEST" ]; then
  echo "✓ New image pulled — container will use the updated version."
else
  echo "✓ Already up to date. No update was needed."
fi

Read the full file on GitHub · 372 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 372 lines · 116 tokens per session scan B 2879ee374ba1

Subscribe to this mod's changes

wren-mcp-setup is a skill published in the GitHub repository Canner/wren-engine (663 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 116 tokens to every session and 3,133 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

data-analysis

Answer data questions from quick metric lookups to full investigations and stakeholder-ready reports.

datagallery-ai/dataagent · 19 tokens

malloy-dashboards

Build or modify a Malloy Publisher dashboard, a tagged .malloy file in a package's dashboards/ directory, with auto-rendered filter controls, a grid layout, and # drill click-through. Use when the user asks for a dashboard, a filterable operational view, or drill-through between views, and no code is wanted.

malloydata/publisher · 73 tokens

malloy-gotchas-modeling

Common Malloy modeling mistakes and how to avoid them. Read BEFORE writing source definitions, dimensions, measures, or joins. Covers reserved words, NULL checks, date functions, type casts, field management (extend except/accept/rename vs include public/internal/private), and query-based source gotchas.

malloydata/publisher · 67 tokens

malloy-model

Build Malloy semantic models with base source and joined source files. Use when creating or modifying .malloy files, user asks to "create a malloy model", "add dimensions", "add measures", "create a source", or any Malloy model authoring task.

malloydata/publisher · 59 tokens

malloy-charts

Chart selection guidance and renderer reference for Malloy views. Use when choosing visualization types, adding chart annotations, user asks "what chart should I use", "how should I visualize this", or when deciding between barchart, linechart, scatterchart, etc.

malloydata/publisher · 57 tokens

malloy-materialization

Add and debug Malloy Persistence materializations in a package - persist an expensive source so queries read a pre-built table. Read this whenever the user wants to materialize a source, add a persist annotation, speed up a slow source, or asks why a persist source isn't building.

malloydata/publisher · 61 tokens