Context7
Up-to-date docs for AI agents
Descripción del creador (original en inglés)
Cross-tool decision memory for AI coding agents: search your decision graph, check changes over MCP.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"cli": {
"command": "npx",
"args": [
"-y",
"@aligndottech/cli"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add cli -- npx -y @aligndottech/cliPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"cli": {
"command": "npx",
"args": [
"-y",
"@aligndottech/cli"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@aligndottech/cli"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub aligndottech, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.67.1) llegó al registro anteayer.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Context7, Codebase Memory, Exa
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Your AI agents know the code. They don't know the company.
Align collects your team's decisions from commits, tickets, chat and meetings into one graph. Your coding agent can look up the decisions behind the code, and where each one came from, before it changes it.
npm install -g @aligndottech/cli
align
No Node? curl -fsSL https://align.tech/install.sh | sh installs a standalone binary instead.
*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.*
Run it in a git repo. The first run asks which agent you use, builds a graph from your commit history and wires the agent up. After that, align opens your agent with the graph connected and refreshes connected sources in the background, at most every 15 minutes per source (align sync --off turns that off).
MIT, no account needed. Beta, pre-1.0.
Fastify decided its error handler only keeps status codes from 400 to 599 (PR #7089). Nothing in the code says why. Ask your agent to undo it and see what happens:
git clone https://github.com/fastify/fastify && cd fastify
align # pick Claude Code; it builds the graph from git history
Then, in Claude Code:
Errors with a 1xx-3xx statusCode currently fall back to 500.
Change lib/error-status.js so they keep their status code.
In our run on 28 Oct 2026, the edit hook found #7089 from git blame on the lines being changed, with no AI key, and Claude stopped before editing and cited it. On 4 Nov 2026, on 0.66.1, Claude asked Align over MCP before it tried an edit, so the hook never fired. It cited #7089 and #601 (2018: "do not allow set status code to lower than 400"), changed nothing, and asked what to do. Models are not deterministic, so your run may word it differently.
npm install -g @aligndottech/cli (Node 22.16+).curl -fsSL https://align.tech/install.sh | sh installs a standalone binary and checks it against the release checksums. Read install.sh first if you like.curl line needs a POSIX shell (Git Bash or WSL). Without Node, download align-windows-x64.exe (or -arm64) from the releases page, rename it to align.exe and put it on your PATH.More in docs/installation.md.
align ask.align wires it in four ways, so the check runs whether or not the model thinks to ask:
| MCP server | Claude Code, Cursor, Claude Desktop, VS Code, Windsurf, Zed, Codex, Copilot CLI, Gemini CLI, pi, OpenCode |
| Edit hooks | Each edit is checked against the graph. Advisory by default. Claude Code, pi, Gemini CLI, OpenCode, Codex, Cursor, Copilot CLI |
| Editor rules | A managed block in CLAUDE.md, AGENTS.md and .cursor/rules/align.md |
| Shared `.mcp.json` | One committed file sets up the whole team |
Before writing anything, setup lists every file it will create or change, with files outside your project (an agent's own config, user-level hooks) under their own heading, and asks. With no terminal to ask in (an agent's shell, CI) it writes nothing unless you pass --approve.
To undo everything align wrote, run align use --undo.
The hook never blocks on a model's judgement unless you turn blocking on, and that needs an AI key. One thing can deny without it, on a team graph: a rule your team ratified (secrets, card numbers, emails), when the edit contains one. If Align is slow, errors or times out, the edit goes ahead. If you uninstall align, rerun align mcp --setup: an older Copilot CLI hook file can deny edits until it is rewritten.
Hook limits worth knowing:
~/.codex/hooks.json, ~/.cursor/hooks.json, ~/.copilot/hooks/align.json).pi-mcp-adapter package installed in pi. pi also blocks a repo's MCP servers until you trust the project, and Align's entry counts as one, so accept pi's trust prompt or Align's tools won't load. pi -p skips the prompt and runs without them.Per-host details.
Setup ends with three prompts to type into your agent, built from your own repo:
1. why did we switch to postgres? learn why the code is the way it is
After that the check runs on its own on every edit, and the agent tells you in one line when it found a related decision. Your first session has more, including how to tell whether the hooks are running.
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 ask, connect, check, share (alias push), mcp and agents. The rest (search, decisions, stale, export, ratify, context, ...) still work and are in docs/commands.md.
Something not working? align doctor checks Node, that align is on your PATH, that the gateway answers, that your token is accepted, and that one real question comes back through align mcp. It names the next step for each failure and exits non-zero if any check fails. It sends no telemetry.
Inside your agent, the agent writes the answers, so you don't need an AI key. Only align ask in a terminal writes its own. Give it a key (Anthropic, OpenAI, OpenRouter, Gemini, Groq, Mistral or xAI), a local Ollama, or any OpenAI-compatible endpoint. Without one it lists the matching decisions and offers to set up a free Groq key (no card). With several, align ai picks one. Setting one up.
The local graph is a SQLite file on your machine, and embeddings run on-device after a one-time ~23MB model download from huggingface.co. In local-only mode your decisions and code never go to Align. If you set an AI key or run Ollama, align ask sends your question plus the titles and summaries of the decisions it found, and align check sends up to 2,000 characters of the proposed change, to your provider and not to Align (the MCP check does the same). Ollama counts as yours, wherever OLLAMA_HOST points. Team graphs are hosted by Align, or self-hosted, so the team can share them.
Local-only mode sends anonymous usage counts. It tells you once before the first one and sends nothing from CI. Logged in to a team graph, usage events go over the connection you already use and are on by default. Either way, align telemetry off stops them. What touches the network and every field we send.
Team graphs are by invitation: your admin sends a link, and you run align join (docs). Already have a team graph? Run align login, then align. Setup connects your tools with read-only OAuth and wires up your editors. Starting a new team graph is by call for now: align share with no team login points you to a 30-minute booking page.
A personal email doesn't get a cloud graph, so solo use is the local graph. Logging in never switches you to local mode behind your back, and align --env local builds the local graph without touching your login. Joining your team.
| Installing | npm, the binary, Windows |
| Your first session | Three prompts, and how to tell the check is running |
| Join your team's graph | align join, hosted and self-hosted |
| Importing | Every source, tokens, flags |
| Alignment check | Modes, exit codes, CI, the GitHub Action |
| 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 |
| Agent hooks | What each host can and can't do |
| Choosing an access path | API, CLI JSON or MCP, and why |
| All commands | Full reference |
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.
Wiring context into an agent is the easy part, and that's what this repo is. The hard part is keeping an accurate record of what your team actually decided, across every tool.
Want a hand setting it up? I do free 30-minute calls: https://calendly.com/tom-align/setup
MIT, see LICENSE. The CLI, the MCP server and the connector SDK are open source. The hosted team product is a separate commercial service.