wren-connection-info

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.

Ir para a instalação

Repositório: Canner/wren-engine
Última atividade na origem: 7 de abril de 2026 às 06:01
Idioma detectado do SKILL.md: inglês
Estrelas: 666
Forks: 200

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/Canner/wren-engine --skill wren-connection-info

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

3 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

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](references/databases.md) | | `MYSQL` | MySQL / MariaDB | [databases.md](references/databases.md) | | `MSSQL` | SQL Server | [databases.md](references/databases.md) | | `CLICKHOUSE` | ClickHouse | [databases.md](references/databases.md) | | `ORACLE` | Oracle | [databases.md](references/databases.md) | | `DORIS` | Apache Doris | [databases.md](references/databases.md) | | `REDSHIFT` | Amazon Redshift | [databases.md](references/databases.md) | | `TRINO` | Trino | [databases.md](references/databases.md) | | `BIGQUERY` | Google BigQuery | [databases.md](references/databases.md) | | `SNOWFLAKE` | Snowflake | [databases.md](references/databases.md) | | `DUCKDB` | DuckDB | [databases.md](references/databases.md) | | `ATHENA` | AWS Athena | [databases.md](references/databases.md) | | `DATABRICKS` | Databricks | [databases.md](references/databases.md) | | `SPARK` | Apache Spark | [databases.md](references/databases.md) | | `S3_FILE` | Amazon S3 | [file-sources.md](references/file-sources.md) | | `GCS_FILE` | Google Cloud Storage | [file-sources.md](references/file-sources.md) | | `MINIO_FILE` | MinIO | [file-sources.md](references/file-sources.md) | | `LOCAL_FILE` | Local files | [file-sources.md](references/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](references/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](references/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) |

Ver no GitHub

Voltar à pesquisa Voltar à instalação

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

2026-04-30

wren-generate-mdl

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-10

wren-usage

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-10

Ver todas deste repositório

wren-connection-info

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório