Tently

io.github.tently-teamv0.1.1Updated Oct 5, 2026

Checks your team's architecture decisions before your coding agent writes code.

VerifiedSTDIODesktop onlyDeveloper Tools Knowledge & Memory

Overview

AI-generated overview

Gives a coding agent your team's architecture decisions and a local impact analysis before it writes code.

What it does: Tently exposes two tools to a coding agent. search_decisions returns the team decisions that apply to the code about to change, each marked blocking or advisory. query_impact_zone computes the blast radius of a symbol, such as its callers and dependencies, locally on the checkout using CodeGraph. The README notes impact results are evidence, not proof, since callers reached through interfaces, dynamic dispatch or re-exports can be missed.
When to use it: Useful when a coding agent works in a repository where the team has accumulated architecture rules from pull requests, reviews and docs, and you want those rules checked before a pull request exists. Also helpful for quickly seeing what a symbol change could affect.
Requirements: Runs locally over stdio via the npm package @tently/mcp, requiring Node.js 20 or later. Needs a Tently workspace API key in TENTLY_API_KEY, created on the Connect page at app.tently.dev. Optional TENTLY_API_URL (default and TENTLY_WORKING_DIR. The init command edits .mcp.json or .cursor/mcp.json and adds a skill; restart the agent afterwards.

Before you install

search_decisions sends your query text and the file paths you pass to the Tently API; query_impact_zone runs entirely locally and source code does not leave the machine. The API key is a workspace credential stored in the agent config, so protect it. init edits agent config files, though it backs up files before editing and prints every change.

Installation

In SourceWeft

Open Tently in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Tently MCP

[npm] [CI] [License: MIT]

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:

Or pass the key through the environment:

init 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

json

{  "mcpServers": {    "tently": {      "command": "npx",      "args": ["-y", "@tently/mcp", "mcp"],      "env": { "TENTLY_API_KEY": "<your key>" }    }  }}

{  "mcpServers": {    "tently": {      "command": "npx",      "args": ["-y", "@tently/mcp", "mcp"],      "env": { "TENTLY_API_KEY": "<your key>" }    }  }}

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/, 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.

Configuration

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

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

Requires 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

MIT

Source: README.md at commit bdcbd90

Tools

Tool metadata has not been indexed yet.

Version history

v0.1.1LatestOct 5, 2026