database-connections

A way for a Mendix application to connect directly to an external database using JDBC, a standard method for database connections. It supports databases such as Oracle, PostgreSQL, MySQL, and SQL Server.

In plain words
What is it for?
Use it to configure database connections, define parameterized SQL queries, inspect tables, and map query results to temporary Mendix entities.
Why use it?
It removes the need to build a separate service just to run database queries from Mendix microflows and map the results into the app.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/mendixlabs/mxcli/database-connections
Any agent
npx skills add mendixlabs/mxcli --skill database-connections
Clone the repo
git clone --depth 1 https://github.com/mendixlabs/mxcli

Made for: Claude Code, Codex.

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,918 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00055 $0.03918
Opus 5 $0.00028 $0.01959
Sonnet 5 $0.00011 $0.00784
Haiku 4.5 $0.00006 $0.00392

Measured 2d ago against content hash 4d413184aef2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

database-connections scanned grade A with 0 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 2d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/mendix/database-connections/SKILL.md · 516 lines

How it starts

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

Skill: Create External Database Connections

Purpose

Create and manage external database connections in Mendix using the External Database Connector. This skill helps you set up JDBC connections to external databases (Oracle, PostgreSQL, MySQL, SQL Server, etc.) and define SQL queries that map results to non-persistent entities.

When to Use This Skill

  • User asks to connect to an external database from a Mendix app (via JDBC)
  • User needs to query data from Oracle, PostgreSQL, MySQL, SQL Server, or other JDBC databases
  • User wants to create database connection configurations
  • User needs to define SQL queries with parameter binding
  • User wants to map query results to Mendix entities

Tip: Use generate connector to auto-create all constants, entities, and queries from a database schema:

SQL CONNECT postgres 'postgres://user:pass@host/db' AS source;
SQL source GENERATE CONNECTOR INTO MyModule;
-- Or generate for specific tables and execute immediately:
SQL source GENERATE CONNECTOR INTO MyModule TABLES (employees, departments) EXEC;

For manual exploration, use sql source show tables; and sql source describe tablename;.

Prerequisites

1. Required Mendix Version

  • Mendix 9.22+ (Database Connector introduced)
  • Mendix 10.10+ (stable version recommended)

2. Required Non-Persistent Entities

Database query results must be mapped to NON-PERSISTENT entities. Create these first:

-- Entity to hold query results
create non-persistent entity MyModule.EmployeeRecord (
  EmployeeId: integer,
  EmployeeName: string(100),
  Department: string(50),
  Salary: decimal
);

3. Required Constants

Connection credentials should be stored in constants:

-- Connection string (JDBC URL)
create constant MyModule.DbConnectionString type string
  default 'jdbc:oracle:thin:@//hostname:1521/SERVICENAME'
  comment 'JDBC connection string for external database';

-- Username
create constant MyModule.DbUsername type string
  default 'app_user'
  comment 'Database username';

-- Password (use PRIVATE for local development)
create constant MyModule.DbPassword type string
  default ''
  comment 'Database password - inject via environment variable in production'
  PRIVATE;

Read the full file on GitHub · 516 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. 2d ago First seen · 516 lines · 55 tokens per session scan A 4d413184aef2

Subscribe to this mod's changes

database-connections is a skill published in the GitHub repository mendixlabs/mxcli (115 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 3,918 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.