SIXTA Connect MCP MCP server

SIXTA Connect provides a remote MCP server that integrates DBA-grade SQL analysis directly into AI coding assistants. It reviews SQL queries, execution plans, and database migrations for safety and performance, offering deterministic feedback on potential issues like table locks or slow queries. The server supports integration with editors like VS Code, Cursor, and Claude, as well as CI/CD pipelines, ensuring that risky database changes are caught before they reach production.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by SIXTA

MCP endpoint (Streamable HTTP)

https://connect.sixta.ai/mcp

Vendor documentation

What you can do with it

Review SQL queries for safety and performance issues
Analyze database migrations for lock levels and safe rollout paths
Identify slow queries and suggest optimized rewrites
Check schema DDL for redundant indexes or security risks

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http sixta-connect-mcp https://connect.sixta.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add sixta-connect-mcp --url https://connect.sixta.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable sixta-connect-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "sixta-connect-mcp": {
      "url": "https://connect.sixta.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "sixta-connect-mcp": {
      "type": "streamableHttp",
      "url": "https://connect.sixta.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start sixta-connect-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "sixta-connect-mcp": {
      "type": "http",
      "url": "https://connect.sixta.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http sixta-connect-mcp https://connect.sixta.ai/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "sixta-connect-mcp": {
      "url": "https://connect.sixta.ai/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "sixta-connect-mcp": {
      "serverUrl": "https://connect.sixta.ai/mcp"
    }
  }
}

See all 957

Do you run SIXTA Connect MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing