Sqlew

MCP开发工具

提供方 未标注

开发工具 未标注 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code

ADR (Architecture Decision Record) for AI Agents – An MCP server that enables AI agents to create, query, and maintain architecture decision records in a...

一句话选型结论

按资料字段整理

Sqlew 属于开发工具类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Development

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Sqlew当前 未标注 未标注 未标注 无 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

13.5 KB
来自项目仓库与上游目录的原文,未做删改

sqlew

> Design intent on tap — stop agents from re-auditing the whole repo every turn

What is sqlew?

The Problem

Strong coding agents no longer "forget" the stack between sessions the way older models did. They treat the codebase as ground truth — and that is good for correctness.

The new failure mode is cost and thrash:

  • Specs, plans, and ADRs already say why a choice was made
  • The agent still re-opens large swaths of source "just to be sure"
  • Rejected alternatives and non-local constraints are expensive (or impossible) to re-derive from code alone
  • Every turn pays the same investigation tax; multi-agent and multi-day work multiplies it

Code answers what is implemented. It is a poor, high-token index for why we chose it, what we forbade, and what we already rejected.

The Solution

sqlew is an MCP server that stores architectural decisions and constraints in a SQL database — with rationale, tags, layers, and rejected alternatives. Agents query intent first (suggest, session context, targeted decision / constraint lookups) instead of re-deriving design context from a full-tree read every turn.```
┌──────────────────────────────────────────────────────────────────────┐
│ Without sqlew │ With sqlew │
│────────────────────────────────────────│─────────────────────────────│
│ Plan/spec: "use Postgres, no Mongo" │ Research/write → ADR draft │
│ Next turn: re-read half the repo │ (or Plan approved → ADR) │
│ "just to confirm the architecture" │ Next turn: suggest/query │
│ Tokens burned; same audit next agent │ → intent in milliseconds │
└──────────────────────────────────────────────────────────────────────┘


sqlew does **not** replace reading code for implementation detail. It replaces **ritual whole-repo archaeology for design intent** with structured recall:

1. **Capture** — Plan Mode is **not required**. Research + Write hooks draft ADRs automatically; Plan Mode capture still works as before (sqlew-plugin)
2. **Recall** — Session start injects recent context (where the harness supports it); Post hooks on Grep / WebSearch / WebFetch inject related ADRs via `suggest`
3. **Enforce** — Constraints stay first-class rules; duplicate/similarity checks stop circular re-decisions

Built on the Model Context Protocol (MCP), so it works with any MCP-compatible AI coding tool.

> _This software does not send any data to external networks. We NEVER collect any data or usage statistics._

## Quick Start

### 1. Install

**Local / full (default)** — all RDB drivers (SQLite, PostgreSQL, MySQL). Unchanged:```bash
npm install -g sqlew
# same capability under the scoped name:
npm install -g @sqlew/full

Cursor Cloud / ephemeral VMs — prefer PostgreSQL-only (no native SQLite addon):```bash
npx @sqlew/pg

or: npm install -g @sqlew/pg


Wire a remote DB with `SQLEW_DATABASE_URL` / `DATABASE_URL` in Environment Secrets. Project name usually comes from the **git** remote basename; set `SQLEW_PROJECT_NAME` only when sharing one DB across repos. **Plan-less auto ADR needs sqlew-plugin Cursor hooks** — MCP (`npx @sqlew/pg`) alone is not enough. Details: Cursor Cloud Agents. Other slim installs: `@sqlew/mysql`, `@sqlew/sqlite`. Package matrix: SCOPED_PACKAGES.md.

**npm 12+** (bundled with Node 24.19+) blocks dependency install scripts by default. The full/`@sqlew/sqlite` installs need better-sqlite3 to download or compile its native addon, so allow that script:```bash
npm install -g --allow-scripts=better-sqlite3 sqlew

Without the flag, sqlew installs but exits on first run with Could not locate the bindings file. Re-run the command above to repair an existing install. @sqlew/pg and @sqlew/mysql do not need this flag.

npm 11 and earlier still run install scripts by default; npm install -g sqlew is enough there.

2. Setup

Choose the setup that matches your environment. Each client has its own install and uninstall steps.

Claude Code (Plugin)

Install:```bash
claude plugin marketplace add sqlew-io/sqlew-plugin
claude plugin install sqlew


Configures MCP server, Skills (Plan Mode guidance), and Hooks (research suggest inject, Write enqueue / Stop flush, Plan-to-ADR).

**Uninstall:**```bash
claude plugin remove sqlew

Codex CLI (Plugin)

Install:```bash
codex plugin marketplace add sqlew-io/sqlew-plugin
codex plugin install sqlew --source sqlew-plugin


After install, open `/hooks` in Codex and trust the bundled sqlew hooks. Enable Plan Mode with `collaboration_modes = true` under `[features]` in your Codex config.

> Do not duplicate skills in `~/.codex/skills/` or add `[mcp_servers.sqlew]` to `config.toml` when using the plugin. See Hooks Guide.

**Uninstall:**```bash
codex plugin remove sqlew

Grok Build (Plugin)

Install:```bash
grok plugin install sqlew-io/sqlew-plugin --trust
grok plugin update


Configures MCP server, Skills (plan mode guidance), and Hooks (plan-less save enqueue, Plan-to-ADR on `exit_plan_mode`).

> Do not duplicate hooks in `~/.grok/hooks/` or add `[mcp_servers.sqlew]` to `~/.grok/config.toml`. See Hooks Guide.

**Uninstall:**```bash
grok plugin remove sqlew

Hermes (Plugin)

Requires sqlew >= 5.3.0. Hermes uses a separate plugin bundle (.hermes-plugin/), not the Claude/Codex plugin manifest.

Install:```bash
hermes plugins install sqlew-io/sqlew-plugin/.hermes-plugin
hermes plugins enable sqlew


Merges MCP + shell hooks into `~/.hermes/config.yaml` and copies planning skills to `~/.hermes/skills/`. See Hermes Hooks Guide for wire-protocol details and manual `config.yaml` setup.

**Uninstall:**```bash
hermes plugins remove sqlew

If you merged hooks manually before using the plugin, also remove mcp_servers.sqlew and sqlew hooks: entries from ~/.hermes/config.yaml. Skills under ~/.hermes/skills/sqlew-* are not removed automatically.

oh-my-pi / omp (Extension)

Requires sqlew with the sqlew/hooks export (see Harness Compatibility for the minimum version). omp uses an in-process Extension (.omp-plugin/), not Claude-style shell hooks.

Install:```bash
npm i -g --allow-scripts=better-sqlite3 sqlew # see Install above (npm 12+)
omp --extension /path/to/sqlew-plugin/.omp-plugin

or:

omp plugin install /path/to/sqlew-plugin/.omp-plugin


Session context via `before_agent_start`; Plan-to-ADR when you approve via `xd://propose` / `/xdev/propose`. Plans live as session-local `local://*-plan.md` (no project `.sqlew/plans/` copy by default). See Hooks Guide.

MCP still comes from the project `.mcp.json` (Extension does not re-register MCP when already present).

#### Other harness (MCP only)

MCP server only — no sqlew-plugin hooks or skills (Cursor, Claude Desktop, custom clients, …). See Harness Compatibility.

Add to `.mcp.json` in your project root:```json
{
    "mcpServers": {
        "sqlew": {
            "command": "sqlew"
        }
    }
}

The database (~/.config/sqlew/sqlew-shared.db) and config are auto-created on first run. See Shared Database for details.

3. Capture decisions (Plan Mode optional)

Plan Mode is no longer required for ADR / suggest. With sqlew-plugin hooks:

  1. Research — Post hooks on Grep / WebSearch / WebFetch (and equivalents) inject related context via suggest
  2. Write — first implementation Write enqueues a draft ADR to .sqlew/queue/pending.json (no DB write yet)
  3. Stop / flush — on-stop or QueueWatcher upserts the queue into the database

Plan Mode still works as before — create a plan, get approval, and Plan-to-ADR records 📌 / 🚫 blocks automatically.

> Hermes exception: Hermes cannot drive this automatic research→ADR trigger via Hooks. Create a Skill with /learn, for example: 「調査開始時にsqlewを使ってサジェストを取得し、実装前にADRをsqlewで記録することを義務付けて」

See Harness Compatibility and Hooks Guide.

Features

  • Structured Records — Decisions stored as relational data with metadata, tags, layers, and version history
  • Fast Queries — 2-50ms SQL recall for design intent; avoid multi-file repo archaeology every turn
  • Duplicate Detection — Three-tier similarity scoring (0-100) prevents redundant decisions
  • Constraint Tracking — Architectural rules and principles as first-class entities
  • Auto-Capture (plan-less) — Research Post hooks inject related ADRs; Write enqueues drafts; Stop / flush upserts to DB
  • Auto-Capture (Plan Mode) — Hooks/Extension still record decisions from Plan Mode (Claude Code, Codex, Grok Build, Hermes, and oh-my-pi via sqlew-plugin)
  • Session Context Injection — Recent decisions and active constraints injected at session start (Claude Code, Hermes, omp, Codex partial; not Grok Build — see matrix)
  • Multi-Database — SQLite (default), PostgreSQL, MySQL/MariaDB, or Cloud
  • Git Worktree Ready — Each worktree shares the same context database

Harness compatibility

Not every feature works the same on every client. Grok Build uses passive hooks (no stdout injection), so session context and plan-mode hook enforcement are skill-based only (◎). oh-my-pi (omp) uses an in-process Extension (sqlew/hooks) rather than shell hooks — the summary rows below are full (✓). Hermes lacks Post-hook context inject for research→ADR — use a Skill (/learn); Plan-to-ADR via plan files still works.

Feature Claude Codex Grok Hermes omp
MCP tools ✓ ✓ ✓ ✓ ✓
Session context injection ✓ △ — ✓ ✓
Research → ADR (plan-less) ✓ △ △ ◎ ✓
Plan-to-ADR (auto) ✓ △ △ ✓ ✓
Plan mode hook enforcement ✓ △ ◎ ✓ ✓

✓ full · △ partial · ◎ skills only · ✎ manual MCP · — not available

Full matrix (hooks, Other harness column, fallbacks): Harness Compatibility

For Teams (sqlew.io)

Connect to sqlew.io for team-shared decisions:

Step 1: Get your API key

Visit sqlew.io and save your API key:```bash

~/.config/sqlew/.sqlew.env (shared across all projects)

SQLEW_API_KEY=your-api-key


**Step 2: Configure each project**```toml
# .sqlew/config.toml
[database]
type = "cloud"

[project]
name = "your-project-name"

Benefits:
- All team members share the same decision database
- Works seamlessly with Git worktree workflows
- No local database setup required

Performance

Metric Value
Query speed 2-50ms
Concurrent agents 5+ simultaneous
Storage efficiency ~140 bytes/decision
Token savings Fewer full-tree "confirm the architecture" passes; 60-75% vs dumping Markdown ADRs into context

Use Cases

  • Architecture Evolution — Document major decisions with full context and alternatives considered
  • Pattern Standardization — Establish coding patterns as constraints, enforce via AI code generation
  • Cross-Session Continuity — Agents reuse recorded intent across days without re-auditing the tree for why
  • Multi-Agent Coordination — Multiple AI agents share architectural understanding
  • Onboarding Acceleration — New sessions/agents load decisions and constraints first, then read only the code paths that matter

Documentation

Guide Description
ADR Concepts Architecture Decision Records explained
Configuration Config file setup, database options
Harness Compatibility Feature × harness matrix (MCP, hooks, session context, Plan-to-ADR)
Hooks Guide Claude Code, Codex, Grok Build, Hermes, and oh-my-pi (omp) integration
Hermes Hooks Guide Hermes-specific setup and wire-protocol notes
Cross Database Multi-database support
CLI Usage Database migration, export/import
Scoped packages @sqlew/* matrix, Cloud install, npm release via GitHub Actions

Upgrade Guides

  • Migrating to SaaS — Export local data to sqlew.io cloud

MCP Tools

8 action-based tools: decision, constraint, project, suggest, help, example, use_case, queue

All tools support action: "help" for documentation. The project tool targets a project per call for desktop AI agents (Claude Desktop, Hermes Desktop) — see Shared Database.

Support

Support development via GitHub Sponsors.

Version

Current version: 5.3.0

See CHANGELOG.md for release history.

What's New in v5.3.0:

  • Hermes support — Plan-to-ADR via sqlew-plugin .hermes-plugin bundle (hermes plugins install sqlew-io/sqlew-plugin/.hermes-plugin)
  • Hook normalization — Hermes pre_tool_call / pre_llm_call payloads mapped to canonical Claude-shaped events and tools
  • Every-turn plan guidance — on-prompt injects FULL/SHORT context via Hermes pre_llm_call ({"context":"..."})
  • .hermes/plans/ — Plan files written by the Hermes plan skill are tracked for decision extraction

License

Apache License 2.0 — Free for commercial and personal use. See LICENSE for details.

Links

  • npm package
  • GitHub
  • Issues
  • Model Context Protocol

Built with MCP SDK, better-sqlite3, and TypeScript.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Sqlew 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Sqlew 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Sqlew 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Sqlew 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Sqlew 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Sqlew 能提供哪些能力?

资料显示能力标签包括 Development。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。