Run any Skill in Manus with one click

wren-connection-info

Stars664

Forks198

UpdatedApril 7, 2026 at 06:01

Reference guide for Wren Engine connection info — explains required fields for all 18 supported data sources (PostgreSQL, MySQL, BigQuery, Snowflake, ClickHouse, Trino, DuckDB, Databricks, Spark, Athena, Redshift, Oracle, SQL Server, Apache Doris, S3, GCS, MinIO, local files). Covers sensitive field handling, Docker host hints, and BigQuery credential encoding. Use when the user asks how to configure a data source connection or what fields to fill in.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Canner

Canner/wren-engine

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	wren-connection-info
description	Reference guide for Wren Engine connection info — explains required fields for all 18 supported data sources (PostgreSQL, MySQL, BigQuery, Snowflake, ClickHouse, Trino, DuckDB, Databricks, Spark, Athena, Redshift, Oracle, SQL Server, Apache Doris, S3, GCS, MinIO, local files). Covers sensitive field handling, Docker host hints, and BigQuery credential encoding. Use when the user asks how to configure a data source connection or what fields to fill in.
license	Apache-2.0
metadata	{"author":"wren-engine","version":"1.5"}

Wren Connection Info Reference

Connection info can only be configured through the MCP server Web UI at http://localhost:9001. Do not attempt to set it programmatically. Always direct the user to the Web UI.

Supported data sources

Value	Database	Fields reference
`POSTGRES`	PostgreSQL	databases.md
`MYSQL`	MySQL / MariaDB	databases.md
`MSSQL`	SQL Server	databases.md
`CLICKHOUSE`	ClickHouse	databases.md
`ORACLE`	Oracle	databases.md
`DORIS`	Apache Doris	databases.md
`REDSHIFT`	Amazon Redshift	databases.md
`TRINO`	Trino	databases.md
`BIGQUERY`	Google BigQuery	databases.md
`SNOWFLAKE`	Snowflake	databases.md
`DUCKDB`	DuckDB	databases.md
`ATHENA`	AWS Athena	databases.md
`DATABRICKS`	Databricks	databases.md
`SPARK`	Apache Spark	databases.md
`S3_FILE`	Amazon S3	file-sources.md
`GCS_FILE`	Google Cloud Storage	file-sources.md
`MINIO_FILE`	MinIO	file-sources.md
`LOCAL_FILE`	Local files	file-sources.md

Read the linked reference file for the user's data source to get required fields, default ports, and setup notes.

Common patterns

Most database connectors need: host, port, user, password, database.

Exceptions:

BigQuery — uses project_id, dataset_id, credentials (base64-encoded). See databases.md for encoding instructions.
Snowflake — uses account instead of host, plus schema.
Trino — needs catalog and schema instead of database.
Databricks — uses serverHostname, httpPath, accessToken (or service principal with clientId, clientSecret).
Spark — only host and port (Spark Connect protocol, no auth fields).
File sources — use url, format, plus bucket/credentials. See file-sources.md.

Docker host hint

If the database runs on the host machine and Wren Engine runs inside Docker, localhost cannot reach the host. Use host.docker.internal instead:

Original	Inside Docker
`localhost`	`host.docker.internal`
`127.0.0.1`	`host.docker.internal`
Cloud/remote hostname	No change needed

Sensitive fields

Never log, display, or pass sensitive values through the AI agent unnecessarily.

Connector	Sensitive fields
Postgres / MySQL / MSSQL / ClickHouse / Oracle / Doris / Redshift	`password`
BigQuery	`credentials`
Snowflake	`password`
Athena	`aws_access_key_id`, `aws_secret_access_key`
Databricks (token)	`accessToken`
Databricks (service principal)	`clientId`, `clientSecret`
S3 / MinIO	`access_key`, `secret_key`
GCS	`key_id`, `secret_key`, `credentials`
Trino / Spark / Local files	(none)

More from this repository

same repository

wren-onboarding

Canner/wren-engine

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. Triggers: '/wren-onboarding', 'install wren', 'set up wren engine', 'wren onboarding', 'connect new database to wren'.

2026-04-30664

wren-generate-mdl

Canner/wren-engine

Generate a Wren MDL project by exploring a database with available tools (SQLAlchemy, database drivers, MCP connectors, or raw SQL). Guides agents through schema discovery, type normalization, and MDL YAML generation using the wren CLI. Use when: user wants to create or set up a new MDL, onboard a new data source, or scaffold a project from an existing database.

2026-04-10664

wren-usage

Canner/wren-engine

Wren Engine CLI workflow guide for AI agents. Answer data questions end-to-end using the wren CLI: gather schema context, recall past queries, write SQL through the MDL semantic layer, execute, and learn from confirmed results. Use when: user asks a data question, requests a report or analysis, asks about metrics, revenue, customers, orders, trends, or any business data; user says 'how many', 'show me', 'what is the', 'top N', 'compare', 'trend', 'growth', 'breakdown'; user wants to explore, analyze, filter, aggregate, or summarize data from a database; agent needs to query data, connect a data source, handle errors, or manage MDL changes via the wren CLI.

2026-04-10664

wren-dlt-connector

Canner/wren-engine

Connect SaaS data (HubSpot, Stripe, Salesforce, GitHub, Slack, etc.) to Wren Engine for SQL analysis. Guides the user through the full flow: install dlt, pick a SaaS source, set up credentials, run the data pipeline into DuckDB, then auto-generate a Wren semantic project from the loaded data. Use this skill whenever the user mentions: connecting SaaS data, importing data from an API, dlt pipelines, loading HubSpot/Stripe/Salesforce/GitHub/Slack data, querying SaaS data with SQL, or setting up a new data source from a REST API. Also trigger when the user already has a dlt-produced DuckDB file and wants to create a Wren project from it.

2026-04-09664

wren-generate-mdl

Canner/wren-engine

Generate a Wren MDL manifest from a database using ibis-server metadata endpoints. Use when a user wants to create or set up a new Wren MDL, scaffold a manifest from an existing database, or onboard a new data source without installing any database drivers locally.

2026-04-07664

wren-http-api

Canner/wren-engine

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).

2026-04-07664

name	wren-connection-info
description	Reference guide for Wren Engine connection info — explains required fields for all 18 supported data sources (PostgreSQL, MySQL, BigQuery, Snowflake, ClickHouse, Trino, DuckDB, Databricks, Spark, Athena, Redshift, Oracle, SQL Server, Apache Doris, S3, GCS, MinIO, local files). Covers sensitive field handling, Docker host hints, and BigQuery credential encoding. Use when the user asks how to configure a data source connection or what fields to fill in.
license	Apache-2.0
metadata	{"author":"wren-engine","version":"1.5"}

Wren Connection Info Reference

Connection info can only be configured through the MCP server Web UI at http://localhost:9001. Do not attempt to set it programmatically. Always direct the user to the Web UI.

Supported data sources

Value	Database	Fields reference
`POSTGRES`	PostgreSQL	databases.md
`MYSQL`	MySQL / MariaDB	databases.md
`MSSQL`	SQL Server	databases.md
`CLICKHOUSE`	ClickHouse	databases.md
`ORACLE`	Oracle	databases.md
`DORIS`	Apache Doris	databases.md
`REDSHIFT`	Amazon Redshift	databases.md
`TRINO`	Trino	databases.md
`BIGQUERY`	Google BigQuery	databases.md
`SNOWFLAKE`	Snowflake	databases.md
`DUCKDB`	DuckDB	databases.md
`ATHENA`	AWS Athena	databases.md
`DATABRICKS`	Databricks	databases.md
`SPARK`	Apache Spark	databases.md
`S3_FILE`	Amazon S3	file-sources.md
`GCS_FILE`	Google Cloud Storage	file-sources.md
`MINIO_FILE`	MinIO	file-sources.md
`LOCAL_FILE`	Local files	file-sources.md

Read the linked reference file for the user's data source to get required fields, default ports, and setup notes.

Common patterns

Most database connectors need: host, port, user, password, database.

Exceptions:

BigQuery — uses project_id, dataset_id, credentials (base64-encoded). See databases.md for encoding instructions.
Snowflake — uses account instead of host, plus schema.
Trino — needs catalog and schema instead of database.
Databricks — uses serverHostname, httpPath, accessToken (or service principal with clientId, clientSecret).
Spark — only host and port (Spark Connect protocol, no auth fields).
File sources — use url, format, plus bucket/credentials. See file-sources.md.

Docker host hint

If the database runs on the host machine and Wren Engine runs inside Docker, localhost cannot reach the host. Use host.docker.internal instead:

Original	Inside Docker
`localhost`	`host.docker.internal`
`127.0.0.1`	`host.docker.internal`
Cloud/remote hostname	No change needed

Sensitive fields

Never log, display, or pass sensitive values through the AI agent unnecessarily.

Connector	Sensitive fields
Postgres / MySQL / MSSQL / ClickHouse / Oracle / Doris / Redshift	`password`
BigQuery	`credentials`
Snowflake	`password`
Athena	`aws_access_key_id`, `aws_secret_access_key`
Databricks (token)	`accessToken`
Databricks (service principal)	`clientId`, `clientSecret`
S3 / MinIO	`access_key`, `secret_key`
GCS	`key_id`, `secret_key`, `credentials`
Trino / Spark / Local files	(none)