EnginiQ MCP

EnginiQ MCP exposes the safe Postgres runtime in EnginiQ over the Model Context Protocol.

It is designed for IDE agents and MCP-compatible hosts such as Cursor or Claude Desktop integrations.

Install

npm install enginiq-mcp

Use this package when you want IDE agents to call guardrailed Postgres tools instead of generating raw SQL on their own.

Configuration

The MCP server resolves the database URL in this order:

1. ENGINIQ_DATABASE_URL
2. DATABASE_URL
3. .enginiqrc.json in the current working directory
4. .enginiqrc.json one directory up

Run locally

export ENGINIQ_DATABASE_URL="postgresql://postgres:postgres@localhost:5432/postgres"
node dist/index.js

The server uses stdio, so it is typically launched by an MCP host rather than directly by a user.

Exposed tools

• list_tables
• describe_table
• get_schema
• create_table
• add_column
• run_migration
• query

Tool shape

The MCP server exposes JSON-schema input definitions for each tool and forwards calls into enginiq-core.

For example, add_column accepts:

{
  "table_name": "posts",
  "column_name": "title",
  "column_type": "text"
}

Internally, that is mapped to the core tool contract before execution.

Guardrails

EnginiQ MCP inherits the same SQL guardrails as enginiq-core, including protections against dangerous DDL and protected table prefixes.