Sixta Connect

ai.sixtaPublished by sixta.aiOfficial publisherv0.1.0Updated Oct 27, 2026

DBRE-grade SQL analysis inside any MCP client. No connection. No install. Paste a query.

VerifiedStreamable HTTPWeb executableDatabases

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant DBRE-grade SQL analysis from a pasted query, with no database connection or install.

What you can do
  • Analyze a pasted SQL query with DBRE-grade review inside the MCP client.
  • Work without connecting to a database or installing anything locally.
  • The manifest lists no individual tools, so the exact operations are not documented.
When to use it
Useful when you want an assistant to review or analyze SQL text you paste in, without wiring up a live database connection or local tooling.
Requirements
A remote streamable HTTP endpoint at connect.sixta.ai; OAuth authentication is required. No environment variables, headers or packages are declared.
Before you install
OAuth sign-in is required, so the service receives your account authorization. Queries you paste are sent to a third-party service; avoid pasting sensitive schema, credentials or production data unless you accept that.

Installation

In SourceWeft

  1. Open Sixta Connect in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.sixta%2Fsixta-connect/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.