
MCP server for Tently, the AI code reviewer for GitHub pull requests. Your coding agent checks team
MCP server for Tently, the AI code reviewer for GitHub pull requests. Your coding agent checks team decisions before it writes code.
·
Tently is an AI code reviewer for GitHub pull requests. It catches the two things diff-only reviewers miss: regressions in code that depends on the change, and changes that break design decisions your team made on purpose. It learns those decisions from your merged pull requests, review threads and docs, and checks every pull request against them.
This repo is Tently's MCP server: the same decisions, inside Claude Code, Cursor or Codex while the agent writes code, before a pull request exists.
Tently is one decision store with two gates:
| Gate | When | What it does |
|---|---|---|
| Pull request review (GitHub App) | Every PR | Posts a check run and inline comments for regressions and decision drift, with the evidence attached |
| This MCP server | While the agent writes | Lets the agent look up the decisions that apply and the blast radius of a change |
The MCP server needs a Tently workspace. Request early access at tently.dev.
Create an API key on the Connect page at app.tently.dev, then run this from your repo root:
npx @tently/mcp init --agent claude --api-key <your key>Or pass the key through the environment:
TENTLY_API_KEY=<your key> npx @tently/mcp initinit adds the tently server to .mcp.json (Claude Code) or .cursor/mcp.json (Cursor), and
installs a small skill that tells the agent when to use it. It backs up any file before editing
it, keeps your other MCP servers, and prints every change. Restart your agent afterwards.
--agent takes claude, cursor, both or auto (the default, which detects what's in the
repo).
{
"mcpServers": {
"tently": {
"command": "npx",
"args": ["-y", "@tently/mcp", "mcp"],
"env": { "TENTLY_API_KEY": "<your key>" }
}
}
}search_decisions: the decisions that apply to the code it's about to change, from your
Tently workspace. Each one says whether breaking it is blocking or advisory. The search is
scoped to the repo you're in (read from the checkout's git remotes), so decisions from your
workspace's other repos don't crowd out this one's.query_impact_zone: the blast radius of a symbol (who calls it, what it depends on),
computed locally on your checkout with CodeGraph.
Your source code never leaves your machine. The index lives in .codegraph/, which init
adds to .gitignore.Impact results are evidence, not proof: callers reached through interfaces, dynamic dispatch or re-exports can be missed, and the tool says so in its output.
| Variable | Meaning |
|---|---|
TENTLY_API_KEY | Workspace API key (required for search_decisions) |
TENTLY_API_URL | API origin, default https://api.tently.dev |
TENTLY_WORKING_DIR | Directory query_impact_zone indexes, default the current directory |
TENTLY_REPO | GitHub repo to scope search_decisions to, as owner/name or a GitHub URL. Default: the origin and upstream remotes of TENTLY_WORKING_DIR, whichever is connected to your workspace (origin first), which covers forks. A value that isn't a GitHub repo is ignored. When no repo is connected (or it was renamed since), the search covers the whole workspace |
search_decisions sends your query text, the file paths you pass and the owner/name of the checkout's origin and upstream remotes to
the Tently API. Nothing
else leaves your machine: query_impact_zone runs entirely locally. See
tently.dev for how Tently handles data.
npm install
npm test
npm run build
node dist/cli.js mcp # start the server on stdioRequires Node.js 20 or later.
Issues and pull requests are welcome. For anything beyond a small fix, please open an issue first so we can agree on the approach.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add tently -- npx -y @tently/mcp mcp{
"mcpServers": {
"tently": {
"env": {
"TENTLY_API_KEY": ""
},
"args": [
"-y",
"@tently/mcp",
"mcp"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"tently","env":{"TENTLY_API_KEY":""},"args":["-y","@tently/mcp","mcp"],"command":"npx"}'[mcp_servers.tently]
command = "npx"
args = ["-y", "@tently/mcp", "mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/tently-mcp to learn what the "Tently Mcp" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npx @tently/mcp init --agent claude --api-key <your key>| Name | What it does |
|---|---|
search_decisions | Search the Tently decision store — the same ratified decisions the PR review gate enforces (architecture boundaries, code-shape conventions, process rules). Each hit is marked BLOCKING (violating it b |
query_impact_zone | Compute the blast radius (callers/dependents) of a symbol using the local code graph, run on your working tree — source never leaves the machine. Call this BEFORE changing the signature or behavior of |
Read live from the server on October 27, 2026.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/tently-mcp)Nothing comparable is listed yet.
v0.1.4Release notesv0.1.3Release notesv0.1.2Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "tently-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.