wren mcp setup

DevOps Community

Skill notes

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:

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:

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: If the image already exists locally, compare the local digest with the remote one to detect updates: Note: If a wren-mcp container is already running and a new image was pulled, stop and remove the old container before proceeding:

Step 3 — Configure connection info via Web UI

Open the Web UI at http://localhost:9001. The Web UI provides: Read-only Mode — toggle to prevent the AI agent from calling deploy, deploy_manifest, list_remote_tables, or list_remote_constraints. Useful for read-only query access. MDL Status — shows the currently deployed MDL (models, columns, data source). Connection Info — select the data source type and fill in credentials. Click Save Connection to test and persist.

Docker host hint

Critical: The container cannot reach the host's localhost directly. If your database runs on the host machine, use host.docker.internal instead of localhost or 127.0.0.1 as the hostname. The Web UI shows a hint for this when it detects you may be connecting to a local database: Original · Inside Docker localhost · host.docker.internal 127.0.0.1 · host.docker.internal

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
macOS · Linux · Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
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`:

02
Step 2 — Prepare workspace and start the container

Step 2 — Prepare workspace and start the container

03
Step 3 — Configure connection info via Web UI

Open the Web UI at http://localhost:9001. The Web UI provides: Read-only Mode — toggle to prevent the AI agent from calling `deploy`, `deploy_manifest`, `list_remote_tables`, or `list_remote_constraints`. Useful for read-only query access. MDL Status — shows the currently deployed MDL (models, columns, data source). Connection Info — select the data source type and fill in credentials. Click Save Connection to test and persist.

04
Step 4 — Configure Claude Code MCP

Claude Code uses streamable-http transport to connect to the containerized MCP server. Via Claude Code CLI (recommended): Or add manually to `~/.claude/settings.json` under `mcpServers`: After adding, restart Claude Code for the new MCP server to be loaded into the session. Confirm with: Note: The config file is `~/.claude/settings.json`, not `~/.claude.json`. Adding the MCP server while a session is already running has no effect until the session is restarted.

05
Step 5 — Configure other MCP clients

Step 5 — Configure other MCP clients

06
Step 6 — Verify the connection

Ask the AI agent to run a health check: Expected response: `SELECT 1` returns a successful result. If health check fails, see Troubleshooting below.

07
Step 7 — Load an MDL and start querying

Option A — Auto-load at startup (recommended): Place your compiled `mdl.json` in `<WORKSPACE_PATH>/target/mdl.json` before starting the container. The container reads `MDL_PATH` at startup and logs: Option B — Deploy via Web UI: Open `http://localhost:9001`, paste or edit your MDL JSON in the MDL Editor, and click Save & Deploy. Option C — Deploy via MCP tool (after container is running):

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.