T
thyn-ai/sqai-mcp
Apache-2.0 · TypeScript + Python · built on Algenta as the underlying substrate · a Thyn product
updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · thyn-ai/sqai-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
thyn-ai/sqai-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# SQAI — Structured Query AI
Excerpted from the repository README (abridged)
> 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 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 server
The same four 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 four 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
Apache-2.0 · TypeScript + Python · built on Algenta as the underlying substrate · a Thyn 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 server
The same four 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 four 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
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/thyn-ai-sqai-mcp/)
- Source
- awesome · https://github.com/thyn-ai/sqai-mcp
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.