Tently MCP
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Tently MCPbefore I refactor src/auth/session.ts, check team decisions and who calls refreshToken"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Tently MCP
Tently in your coding agent. An MCP server for Claude Code and Cursor that checks your team's decisions (the rules Tently learned from your pull requests, reviews and docs) before the agent writes code.
Coding agents write code fast, but they don't know why your team built things the way it did. Tently remembers, and this server gives your agent that memory while it works, before a pull request exists.
Set up
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).
Manual config
{
"mcpServers": {
"tently": {
"command": "npx",
"args": ["-y", "@tently/mcp", "mcp"],
"env": { "TENTLY_API_KEY": "<your key>" }
}
}
}Related MCP server: coderadius
What the agent gets
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.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/, whichinitadds 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.
Configuration
Variable | Meaning |
| Workspace API key (required for |
| API origin, default |
| Directory |
Privacy
search_decisions sends your query text and the file paths you pass to the Tently API. Nothing
else leaves your machine: query_impact_zone runs entirely locally. See
tently.dev for how Tently handles data.
Development
npm install
npm test
npm run build
node dist/cli.js mcp # start the server on stdioRequires Node.js 20 or later.
Contributing
Issues and pull requests are welcome. For anything beyond a small fix, please open an issue first so we can agree on the approach.
License
Related MCP Connectors
Codebase intelligence for AI agents — dead code, blast radius, ownership.
Your team's shipping standards, org map and delivery metrics, inside your coding agent.
Deterministic context layer for your codebase: change impact, blast radius, answers with receipts.
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
Related MCP Servers
- AlicenseAqualityAmaintenanceEnforces team knowledge and workflow policies for AI coding agents by providing context, decisions, and gates before code changes are made.153Apache 2.0

coderadiusofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to query architecture context, data contracts, and blast radius to prevent cross-repo architectural breakage before merging.24Apache 2.0- AlicenseNot gradedqualityAmaintenanceProvides live, graph-verified code intelligence for AI agents, including call graphs, dependency awareness, and safety gates on edits to prevent breaking changes.17MIT
- AlicenseNot gradedqualityAmaintenanceProvides AI coding agents with an embedded knowledge graph and architecture governance tools, enabling blast radius analysis, compliance checks, and smart context extraction from codebases.Apache 2.0