Quanti

io.quantiPublished by quanti.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Query BigQuery, Snowflake, Redshift & Azure Synapse with natural language

VerifiedStreamable HTTPWeb executableDatabasesData & Analytics

Overview

AI-generated overview

Remote MCP server that lets an assistant query BigQuery, Snowflake, Redshift and Azure Synapse data warehouses using natural language.

What you can do
  • Query data warehouses in natural language across BigQuery, Snowflake, Redshift and Azure Synapse.
  • No tool list is published, so the exact operations available are not documented; the stated purpose is natural-language querying of these warehouses.
When to use it
Useful when you want an assistant to answer questions from data held in BigQuery, Snowflake, Redshift or Azure Synapse without writing SQL by hand, and you are comfortable connecting a hosted service to those warehouses.
Requirements
A remote MCP endpoint at ai.quanti.io reached over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared. Network access to the endpoint is needed.
Before you install
The server is hosted by a third party and requires OAuth sign-in, so it will likely receive access to your warehouse data and query results. No tool list or documentation is provided, so what it can read or change cannot be verified before connecting. Review the OAuth scopes granted and avoid exposing sensitive datasets.

Installation

In SourceWeft

  1. Open Quanti 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/io.quanti%2Fmcp-server/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": {
    "quanti": {
      "type": "http",
      "url": "https://ai.quanti.io/mcp"
    }
  }
}

README

This repository has no README.

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. v1.0.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.