Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Deterministic, offline, read-only ADR decision memory for coding agents. No model or network calls.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ADRKIT_MCP_CWD, ADRKIT_MCP_DIRYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"adrkit": {
"command": "npx",
"args": [
"-y",
"@adrkit/mcp"
],
"env": {
"ADRKIT_MCP_CWD": "your-value",
"ADRKIT_MCP_DIR": "your-value"
}
}
}
}Run this in your terminal
claude mcp add adrkit --env ADRKIT_MCP_CWD=your-value --env ADRKIT_MCP_DIR=your-value -- npx -y @adrkit/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"adrkit": {
"command": "npx",
"args": [
"-y",
"@adrkit/mcp"
],
"env": {
"ADRKIT_MCP_CWD": "your-value",
"ADRKIT_MCP_DIR": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"adrkit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@adrkit/mcp"
],
"env": {
"ADRKIT_MCP_CWD": "your-value",
"ADRKIT_MCP_DIR": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
ADRKIT_MCP_CWD envADRKIT_MCP_DIR envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain adrkit.dev (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.20.0) reached the registry 26 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
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.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
@adrkit/mcpDeterministic, offline, read-only decision memory for coding agents — including the decisions you already rejected.
A local Model Context Protocol server that lets an agent harness query one Git-backed ADR (Architecture Decision Record) corpus over stdio: *"has this been decided?"*, *"what governs these files?"*, and *"what replaced this?"* It surfaces superseded and rejected decisions specifically so agents stop re-proposing paths the team already ruled out.
No model calls. No network calls. No writes. The server reads Markdown files
from your repo and returns structured JSON. It never calls an LLM, never opens a
socket, and never mutates your corpus. Every tool is annotated
readOnlyHint: true,openWorldHint: false.
Part of adrkit. The corpus lives in git as one Markdown file per decision with typed YAML frontmatter (@adrkit/core); this server only reads it. Listed in the official MCP registry as `dev.adrkit/mcp` (this is the Node/npm @adrkit/mcp package — unrelated to the adr-kit Python package on PyPI).
Published on npm for Node 22+ with a deliberately small, read-only stdio surface: four tools and no write path.
adrkit is still pre-1.0. If you need repeatable client installs, pin an explicit @adrkit/mcp version in your MCP config instead of floating latest.
The published binary is `adrkit-mcp`. Run it with npx (no install):
npx -y @adrkit/mcp --cwd /path/to/your/repo --dir docs/adr
It speaks JSON-RPC over stdio, so you normally point an MCP client at it rather than running it by hand. Copy-pasteable client configs follow.
Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json). Claude launches servers from an arbitrary working directory, so set ADRKIT_MCP_CWD to your repo's absolute path:
{
"mcpServers": { "adrkit": { "command": "npx", "args": ["-y", "@adrkit/mcp"], "env": { "ADRKIT_MCP_CWD": "/absolute/path/to/your/repo", "ADRKIT_MCP_DIR": "docs/adr" } } } }
Create .vscode/mcp.json in your workspace (VS Code uses the servers key and substitutes ${workspaceFolder}):
{
"servers": { "adrkit": { "type": "stdio", "command": "npx", "args": ["-y", "@adrkit/mcp", "--cwd", "${workspaceFolder}", "--dir", "docs/adr"] } } }
Create .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": { "adrkit": { "command": "npx", "args": ["-y", "@adrkit/mcp"], "env": { "ADRKIT_MCP_CWD": "/absolute/path/to/your/repo", "ADRKIT_MCP_DIR": "docs/adr" } } } }
Add to ~/.copilot/mcp-config.json (user-level) or ./.copilot/mcp-config.json (per-repo). Copilot CLI runs servers from the trusted repo directory, so the default cwd usually resolves correctly:
{
"mcpServers": { "adrkit": { "type": "local", "command": "npx", "args": ["-y", "@adrkit/mcp", "--dir", "docs/adr"], "tools": ["*"] } } }
You can also add it interactively with /mcp add inside a copilot session.
| Option | Env | Default | Meaning |
|---|---|---|---|
--cwd | ADRKIT_MCP_CWD | process.cwd() | Repository root; must canonicalize to a directory containing a readable .git entry (a normal clone or a linked-worktree .git file). |
--dir | ADRKIT_MCP_DIR | docs/adr | ADR directory, resolved against --cwd and required to stay contained within it (realpath-checked, so a symlink escape is rejected). |
Flags win over environment variables, which win over the defaults. An unusable configuration exits non-zero with a diagnostic on stderr (2 for an unparseable flag, 1 for an invalid root/directory) and never starts a transport. stdout is reserved for JSON-RPC protocol frames only.
The server speaks both MCP protocol eras on the same stdio connection, and the client picks. The opening exchange selects the era and pins it for the connection's lifetime:
| Client opens with | Server serves |
|---|---|
server/discover, or any request carrying a 2026 _meta envelope | `2026-07-28` — stateless, no handshake |
initialize / notifications/initialized | the 2025-era revision it negotiates |
On 2026-07-28 there is no initialize handshake and no session id: every request carries its own protocol version and client capabilities in _meta, and every result is self-describing (resultType, plus server identity in _meta). tools/list and server/discover are cacheable (SEP-2549) and are served with ttlMs: 300000, cacheScope: "public" because the 4-tool surface is fixed for the life of the process and carries no corpus content. Corpus reads are never cacheable: every tools/call loads a fresh projection.
Nothing else about the tools changes between eras — same names, same schemas, same annotations, same structured results. The server uses none of the features the 2026-07-28 revision deprecated (roots, sampling, logging) or removed (sessions, ping, resources/subscribe).
Exactly four tools, all read-only. Each shares fixed annotations (readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false), returns a deterministic human-readable summary line in content[0].text, and carries a findings page with the corpus's own parse/validation findings. Every substantive response also includes a corpusHealth sibling: { fingerprint, recordCount, excludedCount }.
Shapes below are the real input/output contracts (see packages/mcp/src/tools). Each tool's structured output is { corpusHealth?, result }; the objects shown under "output" are the members of that discriminated result union (keyed on outcome). findings and every growing array are cursor-paginated (see Pagination); findings and repeated pagination fields are elided here for brevity.
search_decisionsNormalized literal substring search over id, title, tags, and body (the graveyard of superseded/rejected records is included by default). Filters are ANDed: status/scope match any-of; tags matches all-of.
// input
{ "query": "postgres", // required, 1–256 code units, non-empty after trim "status": ["accepted"], // optional, ≤6, any-of "tags": ["database"], // optional, ≤32 tags × ≤64 chars, all-of "scope": ["backend"] // optional, ≤3, any-of } // output → single "results" branch (empty results use the same branch) { "outcome": "results", "items": [ { "id": "0007", "title": "Adopt Postgres", "status": "accepted", "sourcePath": "docs/adr/0007-adopt-postgres.md", "matchedFields": ["title", "body"] // subset of id | title | tag | body } ], "cursor": null }
get_decisionThe complete typed frontmatter + body for one ref.
// input
{ "ref": "0007" } // AdrRef, 1–128 chars (local id, or a "log:id" federated ref) // output → discriminated on "outcome" // found (the full record is nested under "decision"): { "outcome": "found", "decision": { "requestedRef": "0007", "id": "0007", "title": "Adopt Postgres", "status": "accepted", "sourcePath": "docs/adr/0007-adopt-postgres.md", "frontmatter": { /* typed YAML: status, tags, affects, relations, ... */ }, "body": "## Context\n..." } } // other outcomes: // { "outcome": "not-found", "requestedRef": "9999" } // { "outcome": "ambiguous-local-id", "requestedRef": "0007", "candidates": [ /* DecisionSummary[] */ ] } // { "outcome": "federated-log-unavailable", "requestedRef": "core:12", "log": "core", "id": "12" }
A log:id federated ref is recognized but never resolved or substituted — this server reads exactly one local corpus.
get_decision_contextGoverning / active-proposal / historical decisions for repo-relative files[], via each record's own affects matchers. Paths are compared against patterns only — never opened.
// input
{ "files": ["src/db/pool.ts", "src/db/schema.sql"] // 1–256 entries; each POSIX, 1–1024 chars; no leading "/", no "..", no drive, no "\" } // output → single "matches" branch (all three arrays; empty is the same branch) { "outcome": "matches", "governing": [ { "id": "0007", "title": "Adopt Postgres", "status": "accepted", "sourcePath": "docs/adr/0007-adopt-postgres.md", "firedMatchers": [ { "type": "path", "pattern": "src/db/**" } ], "relations": { "supersedes": [], "supersededBy": null, "relatesTo": [], "conflictsWith": [] } } ], "activeProposals": [], "history": [] }
list_supersededEvery superseded record with its direct local replacement state — the tool that keeps agents from re-proposing rejected paths.
// input (pagination only)
{} // output → single "entries" branch { "outcome": "entries", "items": [ { "id": "0003", "title": "Use MySQL", "status": "superseded", "sourcePath": "docs/adr/0003-use-mysql.md", "supersededBy": { // one of four states: "resolved": true, "target": { "id": "0007", "title": "Adopt Postgres", "status": "accepted", "sourcePath": "docs/adr/0007-adopt-postgres.md" } } // unresolved states: // { "resolved": false, "targetRef": "0099", "reason": "dangling" } // { "resolved": false, "targetRef": "0007", "reason": "ambiguous", "candidateCount": 2 } // { "resolved": false, "targetRef": "core:1", "reason": "federated-unavailable", "log": "core", "id": "1" } } ], "cursor": null }
Relation refs (supersedes, supersededBy, relatesTo, conflictsWith) are surfaced verbatim and never expanded — follow them with a second get_decision call. Supersession is reported one hop deep; there is no transitive traversal.
The package root exports only a sealed lifecycle factory. There is no way to reach the underlying SDK server, its registrations, or its transport:
import { createAdrkitMcpServer } from '@adrkit/mcp';
const server = createAdrkitMcpServer({ cwd: process.cwd(), dir: 'docs/adr' }); await server.start(); // validates the root, then serves one stdio connection // ... later: await server.close();
createAdrkitMcpServer(options?) performs no filesystem access at construction and returns a frozen, null-prototype handle with exactly start() and close().
Transport failures — a transport that fails to start, or a background stream error such as the EPIPE from a client that has gone away — are reported through the optional onError option, which defaults to a stderr diagnostic. The adrkit-mcp binary additionally exits non-zero. Nothing is written to stdout: that is reserved for protocol frames.
Closing stdin is the shutdown signal, as the MCP stdio binding specifies: the adrkit-mcp binary exits 0 with nothing on stderr. Requests still in flight when stdin closes are aborted and not answered, so a client (or a script piping requests in) must keep stdin open until it has read every response it wants.
query 1–256 code units (non-empty after trimming); ref 1–128; files[] 1–256 entries of 1–1024 POSIX-only chars (no leading /, no .., no drive letter, no backslash); status ≤6, scope ≤3, tags ≤32 × ≤64 chars; result and findings pages default 20, max 100; a per-record ADR sourc
Only the beginning is shown; read the rest in the repo