Align CLI MCP Server

MCPAI代理

提供方 aligndottech

AI代理 stdio · 本地进程 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorVS Code

Your AI agents know the code. They don't know the company. A local decision graph from your git history, checked by your coding agent before it edits.

一句话选型结论

按资料字段整理

Align CLI MCP Server 属于AI代理类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

mcpclaude codecursor

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 node,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

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

值得选的地方

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

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Align CLI MCP Server当前 未标注 stdio · 本地进程 本地部署 无 2026-11-20
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方aligndottech上游标注的维护方 aligndottech
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · node本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

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

Align CLI

Your AI agents know the code. They don't know the company.

Align reads the decisions your team already made, from commits, pull requests, docs, tickets and
chat. Then it checks your coding agent's changes against them. Nobody writes the decisions in by
hand: Align reads them from where they were made, and reads again when you run it.

See it catch a decision in a few seconds, with nothing installed and no account or AI key:```bash
npx @aligndottech/cli demo


It runs in a temp folder and leaves your repo and `~/.align` alone. The first run downloads a
small on-device model (about 50 MB) once.

*The same prompt, two real runs on Align's own repo (14 Oct 2026). The text is
copied from those runs and shortened. The GIF replays it, so it isn't a live session (how).
Without Align the agent plans to skip signature checks; with it, the agent stops and cites the
decision that ruled that out.*

## Use it on your own repo```bash
npm install -g @aligndottech/cli
align

No Node? curl -fsSL https://align.tech/install.sh | sh installs a standalone binary instead.
Windows and the details are in Installing.

Run align in a git repo. It reads your commits, ADRs and RFCs, decision logs, CLAUDE.md,
AGENTS.md and recent merged pull requests, and stores what was decided, why and where in a local
file, ~/.align/local.db. This README calls that the graph. Then it asks how you want to use it.
Before it writes anything it lists every file and asks.

MIT, no account needed. Beta, pre-1.0.

Three ways to use it

Use one, or all three.

1. A decisions file you commit

Nothing is wired into your agent. One command writes the file, and your agent reads it like any
other file in the repo. It needs no setup first.```bash
align up --out DECISIONS.md --limit 30


This reads the repo's commits, pull requests and docs, writes `DECISIONS.md`, and adds
`@DECISIONS.md` to your `CLAUDE.md`. With no `CLAUDE.md`, it prints that line for you to add.
Commit both. Run it again whenever you want a new version.
The file lists the rules written in your docs first, then the commits that state a decision, with
the reason where one was given. Fixes and chores are left out.

Two protections. It never replaces a file it did not write, and it will not write into
`CLAUDE.md` or `AGENTS.md`. And `--out` only writes when every decision comes from this repo's
own commits, pull requests and committed docs, on your local graph. If any decision comes from a
chat, a ticket, another repo or a doc you have not committed, `--out` refuses. Plain `align up`
then writes a private `.align/decisions.md` that stays out of git.

### 2. A check inside your agent

`align` wires two things into your agent. An edit hook checks each edit against the graph. An MCP
server (the standard way an agent calls an outside tool) lets the agent ask the graph a question.
The hook runs outside the model, so the agent doesn't have to remember to ask. It shows the
decision behind the code and where it came from.

- **Claude Code:** the check runs before the edit is written. That is recorded in headless runs
  only; interactive sessions are not tested.
- **Cursor, Copilot CLI and Gemini CLI:** their hooks hand the result to the model after the edit
  lands. None of the three has been tested against a live session.
- It warns by default, and blocking is opt-in. If Align is slow or errors, the edit goes ahead.

Hook coverage lists what has and has not been tested, host by host.
Agent hooks has what each agent can and can't do, what setup writes, and
how the pieces fit.
To undo everything Align wrote, run `align use --undo`.

Claude Code users can install it as a plugin instead:```
/plugin marketplace add aligndottech/align-cli
/plugin install align-cli@aligndottech

Then run npx @aligndottech/cli once in the repo to build the graph. Codex has a plugin too. Its
hook does nothing until you approve it once inside Codex. After that we have seen it run in
codex exec (Codex CLI 0.153.0), though no recorded payload backs that yet. Both are in
Installing.

3. A check in CI

Fail a pull request that goes against a decision in your committed file:```bash
align check --ci --base origin/main --decisions-file DECISIONS.md


It needs only your own provider key, for example `OPENAI_API_KEY` from a repository secret. No
account, no graph, no MCP. It exits `1` on a conflict and `2` when it could not check, so a
check that did not run never passes. A diff too big for the model to read whole is a `2` as
well. The workflow file is in Alignment check.

### ADRs in your repo

`align adr` lists the decisions that never got an ADR. `align adr write` goes through them and
drafts one for each you accept, in your existing ADR folder, numbered after the last one. The
text comes from the commit or pull request itself, with a link back to it. No model writes it,
and no file is ever replaced.

## What it reads

Git history, the repo's ADRs and RFCs, decision logs, `CLAUDE.md`, `AGENTS.md`, tenets and
architecture docs. With `align connect`: GitHub, GitLab, Jira, Confluence, Linear, Notion, Slack,
Teams and Zoom. Also nightshift's parking lot and
plan record (`align connect nightshift`), and MIRSAD exports. All read-only.
Importing has every source and its flags.

Connected sources refresh in the background when you start `align`, at most every 15 minutes per
source. There is no timer, so nothing refreshes while you only have your agent open.

## Privacy and telemetry

Align is open source (MIT). In local mode the graph is a SQLite file on your machine,
`~/.align/local.db`. Tokens you paste for a connector go in your OS credential store (Keychain,
Secret Service or DPAPI), or in `config.json` if there is none. In local-only mode the only thing
sent to Align is anonymous usage counts, never code or decision text, unless you run `align share`.
It tells you once before the first one and sends nothing from CI. Turn them off with
`align telemetry off` or `DO_NOT_TRACK=1`.

Two things do leave your machine. The first run in a github.com repo reads that repo's recent
merged pull requests from api.github.com without asking. And `align ask` and `align check` send
your question or your diff, with the matching decisions, to the AI provider whose key you set, or
to your local model. They do not go to Align. npm releases are published with provenance.

What touches the network and every field we send.

## Everyday commands```bash
align                                # set up, or see your graph and what to do next
align ask "how does our auth work"   # an answer, with sources
align ask src/auth/session.ts        # decisions about a file
align connect                        # pick a source to import: git, docs, jira, github, ...
align connect jira --token ...       # import one source directly
align check                          # check your staged diff against the graph
align mcp --setup                    # wire your agent to the graph

align --help lists the main ones, and the rest are in docs/commands.md. Something not working? align doctor
checks the install, the graph and one real question, and names the next step for each failure.

align ask and align check need an AI key or a local Ollama to write an answer or a verdict.
So does telling a replaced decision from a conflicting one on a local graph. Inside your agent,
search needs no key, because the agent does the reading.
Setting one up.

Teams

Team graphs are by invitation: your admin sends a link, and you run align join. Already have a
team graph? Run align login, then align. Starting a new one is by call for now. A personal
email doesn't get a cloud graph, so solo use is the local graph.
Joining your team.

Does it work

One published study gave a coding agent the product decisions on record and saw decision
compliance go from 46% to 95%
(Dillon & Varanasi, arXiv:2605.08112). It's a small vendor
study, 8 tasks and 41 decision points, and it isn't our data.

Our own benchmark is on our own repos: 29 decisions, every answer labelled by a person. With
Align the agent followed the current decision in 139 of 145 runs, with read-only repo search 96
of 145, and with no tools 34 of 145. Where the decision was never written in the code, it was 29
of 30 against 5 of 30. It's dogfood, not customer data, and the product was tuned on these
tasks. Method and raw results.

From people using it:

> Align caught a gap in my own pull request to Align. It flagged that my change went against a
> decision the team had already recorded, and it was right. With pi, the finding reaches the
> model before the edit lands, which is exactly where you want it.
>
> Ryan Joshua Gapac (#569)

With pi, a finding that blocks stops the edit before it runs. One that doesn't is added to
the edit's result, so the model reads it straight after.

> The pipe-guard question found the right commit and its reason: that guard would have refused
> about 1 in 24 of the Bash calls I'd recorded. Handy to get that back.
>
> Collin Nerdahl, maker of Andon

Want a hand setting it up? I do free 30-minute calls: https://calendly.com/tom-align/setup

Docs

Installing · npm, the binary, Windows, the Claude Code and Codex plugins
Your first session · Three prompts, which agent runs, and how to tell the check is running
Importing · Every source, tokens, flags
Alignment check · Modes, exit codes, CI, the GitHub Action
Agent hooks · How it works, what setup writes, and what each host can and can't do
Hook coverage · What has been tested, host by host
Cloud or local-only · What runs where, what touches the network
Telemetry · Every event and field, and how to turn it off
MCP server · Editor config, the tools your agent gets
Configuration · AI providers, env vars, auth, self-hosting
Join your team's graph · align join, hosted and self-hosted
Choosing an access path · API, CLI JSON or MCP, and why
All commands · Full reference

License

MIT, see LICENSE. The CLI, the MCP server and the
connector SDK are open source. The hosted
team product is a separate commercial service.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Align CLI MCP Server 怎么安装?

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

Align CLI MCP Server 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Align CLI MCP Server 收费吗?

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

Align CLI MCP Server 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Align CLI MCP Server 支持哪些客户端?

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

Align CLI MCP Server 能提供哪些能力?

资料显示能力标签包括 mcp、claude code、cursor、codex、ai agents、adr。具体工具清单以官方文档为准。

Align CLI MCP Server 需要什么运行环境?

运行时为 node;属于本地进程,需要在本机装好运行环境。

Align CLI MCP Server 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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