Skip to main content
ClaudeWave

SQAI (Structured Query AI) MCP server — the three governed, deterministic, read-only structured-data tools (listSources, queryData, explainQuery) for any MCP host. npm: @thyn-ai/sqai-mcp. A Thyn product, Apache-2.0.

MCP ServersOfficial Registry0 stars0 forksTypeScriptApache-2.0Updated today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (Apache-2.0)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 9/24/2026
Install in Claude Code / Claude Desktop
Method: NPX · @thyn-ai/sqai-mcp
Claude Code CLI
claude mcp add sqai-mcp -- npx -y @thyn-ai/sqai-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "sqai-mcp": {
      "command": "npx",
      "args": ["-y", "@thyn-ai/sqai-mcp"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Use cases

MCP Servers overview

# SQAI — Structured Query AI

> **SQAI is the deterministic, read-only structured-data tool for AI agents, with governed execution and replayable provenance.**

Apache-2.0 · TypeScript + Python · built on Algenta as the underlying substrate · a [Thyn](https://thyn.ai) product

The model proposes meaning. SQAI controls execution: typed intent in, policy-checked
deterministic execution, replayable results with full provenance out. No raw SQL,
no eval, no write path.

## Architecture

| Layer | Package | What it is |
| --- | --- | --- |
| AI SDK tools | `@thyn-ai/sqai-ai-sdk` (npm) | Three Vercel AI SDK 7 tools — `listSources`, `queryData`, `explainQuery` |
| Product SDK | `@thyn-ai/sqai` (npm) | SQAI query plane + full computation plane |
| Product SDK | `sqai` (PyPI) | Same SQAI surface, 1:1 vocabulary |
| CLI | `@thyn-ai/sqai-cli` (npm, bin `sqai`) | `sqai doctor --parity`, `sqai runtime install/verify/status/stop` |
| Capability contract | Embedded SQAI contract | The generated, hash-pinned inventory of every capability SQAI exposes |
| Execution substrate | Algenta (exact-pinned) | Underlying deterministic execution substrate and managed signed runtime bundle |

## Quickstart (AI SDK)

```ts
import { generateText } from "ai";
import { createSQAI } from "@thyn-ai/sqai-ai-sdk";

const sqai = createSQAI({ sources: [{ data: "./data/sales.csv", name: "sales" }] });

const { text } = await generateText({
  model: "openai/gpt-5-mini",
  tools: sqai.tools(),
  prompt: "Which region had the highest total revenue?",
});
```

No server. No daemon for the query plane. The computation plane provisions a
signed managed runtime transparently on first use.

<!-- mcp-name: io.github.thyn-ai/sqai -->

## MCP server

The same three governed tools are available to any MCP host (Claude Desktop,
Cursor, …) as a stdio server — descriptions, Zod schemas, and execute
functions are read straight off the AI-SDK tool objects, never forked:

```bash
npx @thyn-ai/sqai-mcp
```

```json
{
  "mcpServers": {
    "sqai": {
      "command": "npx",
      "args": ["-y", "@thyn-ai/sqai-mcp"],
      "env": {
        "SQAI_SOURCES": "[{\"data\": \"./data/sales.csv\", \"name\": \"sales\"}]"
      }
    }
  }
}
```

Introspection (`initialize` / `tools/list`) needs no credentials — zero
environment is a valid configuration. Executing any of the three tools requires
a free community login (`sqai login` once / device registration, or
`SQAI_API_KEY`) — fully offline thereafter; without it every tools/call returns
a structured `login_required` error. `SQAI_DEPLOYMENT_URL` keeps its usual
semantics from `@thyn-ai/sqai`.

| Tool | What it does |
| --- | --- |
| `listSources` | Discovery: sources with exact field names, types, and allowed operations; computation-catalog search; per-module signatures. |
| `queryData` | One deterministic, read-only query or computation; truncated results stay retrievable via `result_id`. |
| `explainQuery` | Dry-run: resolved plan, `plan_hash`, validation — or a computation-signature check with a preview `invocation_hash`. |

All three are annotated `readOnlyHint: true`, `destructiveHint: false`,
`idempotentHint: true`, `openWorldHint: false`. All three execute under the one
uniform license gate: free on 1 machine with a one-time device registration
(`sqai login`) — licensing moves a signed token, never your data; without it,
every tool call — local CSV reads included — returns a structured
`login_required` error by design.

## What works today

- Query plane (connect / resolve / query / verify / ask) — in-process, both languages
- Full SQAI computation plane behind capability-contract validation
- Policy allow-lists (sources, fields, functions) the model can never override
- Cross-language conformance: identical values, `plan_hash`, `intent_signature`
- Model-context truncation with opaque result handles

## Repository layout

```
contracts/        generated capability contract + tested version pair
packages/sdk/     @thyn-ai/sqai (TypeScript product SDK)
packages/ai-sdk/  @thyn-ai/sqai-ai-sdk (Vercel AI SDK tools)
packages/cli/     sqai CLI (doctor, runtime verbs)
packages/mcp/     @thyn-ai/sqai-mcp (MCP stdio server)
packages/python-sdk/  sqai (PyPI)
examples/         runnable examples (AI SDK registry example)
scripts/          contract sync + parity gate
docs/             GitBook (docs.sqai.com)
```

## Key documents

| Doc | Purpose |
| --- | --- |
| [docs/quickstart-ts.md](docs/quickstart-ts.md) | TypeScript quickstart |
| [docs/quickstart-python.md](docs/quickstart-python.md) | Python quickstart |
| [docs/ai-sdk-tools.md](docs/ai-sdk-tools.md) | Tool schemas and truncation contract |
| [docs/determinism.md](docs/determinism.md) | Hashes, envelopes, "deterministic within the declared execution scope" |
| [docs/licensing.md](docs/licensing.md) | Free developer tier, entitlements, runtime bundle trust |
| [SECURITY.md](SECURITY.md) | Security policy |
ai-agentshacktoberfestmcpmcp-servermodel-context-protocolstructured-datatypescript

What people ask about sqai-mcp

What is thyn-ai/sqai-mcp?

+

thyn-ai/sqai-mcp is mcp servers for the Claude AI ecosystem. SQAI (Structured Query AI) MCP server — the three governed, deterministic, read-only structured-data tools (listSources, queryData, explainQuery) for any MCP host. npm: @thyn-ai/sqai-mcp. A Thyn product, Apache-2.0. It has 0 GitHub stars and its last recorded update is dated 2026-09-24.

How do I install sqai-mcp?

+

You can install sqai-mcp by cloning the repository (https://github.com/thyn-ai/sqai-mcp) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is thyn-ai/sqai-mcp safe to use?

+

Our security agent has analyzed thyn-ai/sqai-mcp and assigned a Trust Score of 95/100 (tier: Verified). See the full breakdown of passed checks and flags on this page.

Who maintains thyn-ai/sqai-mcp?

+

thyn-ai/sqai-mcp is maintained by thyn-ai. The last recorded GitHub activity is dated 2026-09-24, with 0 open issues.

Are there alternatives to sqai-mcp?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy sqai-mcp to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: thyn-ai/sqai-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/thyn-ai-sqai-mcp)](https://claudewave.com/repo/thyn-ai-sqai-mcp)
<a href="https://claudewave.com/repo/thyn-ai-sqai-mcp"><img src="https://claudewave.com/api/badge/thyn-ai-sqai-mcp" alt="Featured on ClaudeWave: thyn-ai/sqai-mcp" width="320" height="64" /></a>

More MCP Servers

sqai-mcp alternatives