SIXTA Connect
ai.sixta/sixta-connect
Documentation
Installation
Add https://connect.sixta.ai/mcp as a remote MCP server.
Claude Code:
claude mcp add --transport http sixta https://connect.sixta.ai/mcp
API-key auth is supported with an Authorization: Bearer <your-key> header. Claude web/Desktop can also use the keyed URL form shown in the docs.
Configuration
- Remote endpoint:
https://connect.sixta.ai/mcp - Optional API key auth:
Authorization: Bearer <your-key> - CI secret:
SIXTA_API_KEY - GitLab MR comments:
SIXTA_BOT_TOKEN - Codex CLI example env var:
SIXTA_KEY
Capabilities
- Deterministic SQL analysis in MCP clients
- Migration review for Django, Alembic, Flyway, Liquibase, Prisma, dbmate, and golang-migrate workflows
- Pull request / merge request comments, inline findings, and severity gating in CI
- Benchmarked with an internal 129-case suite across MySQL and PostgreSQL
- Self-hosted bridge support for Connect Pro when the database is not directly reachable
Limitations
- Free Connect works from pasted SQL and does not require database credentials
- The
/mcpsurface has no cache; CI caching applies only to the batch/v1/analyzepath - Benchmark figures are from SIXTA's internal suite and are not universal guarantees
- Bridge mode requires outbound HTTPS, a read-only database account, and Node.js 20 or newer
