digline
What it does
Read, measure and explain LLM eval runs of a digline suite. Cannot promote a baseline.
- Connects Runs on your computer
- Account or key No key needed
- Category Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Let AI install it
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server digline for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "digline": { "command": "uvx", "args": [ "digline-mcp", "--root", "your-value", "--names", "your-value" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the digline tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "digline": { "command": "uvx", "args": [ "digline-mcp", "--root", "your-value", "--names", "your-value" ] } } }Quit Claude and open it again
Try it
Use digline and tell me what you can do for me, then show me one thing✓ If Claude says it is using digline or shows a digline tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect digline yet
digline runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect digline
- Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- Install Python (uv) on your computer first (one time)
- Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
- Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server digline for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user digline -- uvx digline-mcp --root your-value --names your-value 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the digline tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user digline -- uvx digline-mcp --root your-value --names your-valueType /mcp in Claude Code
You should see digline listed as connected
Try it
Use digline and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using digline or shows a digline tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Let AI install it
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server digline for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "digline": { "command": "uvx", "args": [ "digline-mcp", "--root", "your-value", "--names", "your-value" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the digline tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open Cursor’s MCP settings file
~/.cursor/mcp.json
Paste these settings, fill in the empty values and save
{ "mcpServers": { "digline": { "command": "uvx", "args": [ "digline-mcp", "--root", "your-value", "--names", "your-value" ] } } }Open the AI chat in Cursor in Agent mode
Try it
Use digline and tell me what you can do for me, then show me one thing✓ If Cursor says it is using digline or shows a digline tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Let AI install it
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server digline for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "digline": { "type": "stdio", "command": "uvx", "args": [ "digline-mcp", "--root", "your-value", "--names", "your-value" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the digline tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open VS Code’s MCP settings file
MCP: Open User Configuration
Paste these settings, fill in the empty values and save
{ "servers": { "digline": { "type": "stdio", "command": "uvx", "args": [ "digline-mcp", "--root", "your-value", "--names", "your-value" ] } } }Open the AI chat in VS Code in Agent mode
Try it
Use digline and tell me what you can do for me, then show me one thing✓ If VS Code says it is using digline or shows a digline tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user digline -- uvx digline-mcp --root your-value --names your-valueClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"digline": {
"command": "uvx",
"args": [
"digline-mcp",
"--root",
"your-value",
"--names",
"your-value"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"digline": {
"command": "uvx",
"args": [
"digline-mcp",
"--root",
"your-value",
"--names",
"your-value"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"digline": {
"type": "stdio",
"command": "uvx",
"args": [
"digline-mcp",
"--root",
"your-value",
"--names",
"your-value"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- GitHub starsi
- 10 (Stars for the whole repo)
This repo holds several MCP listings; its stars count once in rankings - Downloads per weeki
- 282/wk
- Verified domain
- ✓ digline.dev
- Connection
- Runs on your computer
- Latest versioni
- 0.9.1
- Categoryi
- Search & AI memory
- Published to registryi
- Nov 10, 2026
- Code last changedi
- Nov 14, 2026
- Maker
- digline
- Packages
pypi: digline-mcp- Website
- digline.dev
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 16, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain digline.dev (the registry checks domain ownership)
- ✓ Pass
Still maintained
Code last changed 2 days ago
- ✓ Pass
Has a licence
Uses Apache-2.0
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
No entries on OSV.dev for digline-mcp@0.9.1
Checks only this package version, not every dependency · checked Nov 15, 2026
Makers: ask for a re-check or report wrong info
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Search & AI memoryi
- More stars than 82% of the other 6183 servers in this category
- Published to the registry more recently than 88% of the other 6183 servers in this category
- Basic checks equal to or better than 100% of the other 6183 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is digline safe?
It passed 3 of 3 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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed 2 days ago, and the latest version (0.9.1) reached the registry 6 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: OpenSEO, Exa, Mockserver, Microsoft Learn MCP, Docs
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Mockserver
Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
Microsoft Learn MCP
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
Docs
Search and read Empryo's documentation. Read-only, no auth, no local access.
- OpenSEO — Runs in the cloud, nothing to install · No key needed
- Exa — Runs in the cloud, nothing to install · No key needed · In Claude’s directory
- Mockserver — Installs on your computer · No key needed
- Microsoft Learn MCP — Runs in the cloud, nothing to install · No key needed · In Claude’s directory
- Docs — Runs in the cloud, nothing to install · No key needed
README from the maker
Open the README
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.
digline-mcp
The MCP server for digline: it lets a coding agent read a digline result and measure a new one, and it does not let the agent promote a baseline.
Not because promotion is refused. Because there is no such tool.
The thirteen tools
| tool | what it does |
|---|---|
list_runs | every stored run of a suite, newest first, with the baseline marked |
get_run | one stored run — the verdicts, never the payload |
get_baseline | the approved reference, same shape |
log | which model answered, read down the stored runs; never a gate |
compare | a run against the baseline: did it get worse? |
diff | two runs, neither of them a reference: should I switch? |
explain | one run read back as typed facts, with the exit code |
run | execute the suite, with the call count acknowledged first |
where | where the project is, and the command for the next step |
record_status | whether each tenant records, and how much |
record_listing | a suite's recorded answers, counted by the shape of the output; never a yes or a no |
record_compare | a suite's recorded answers by case and by setup, each by its number in the answer |
suggest | a first suite, proposed as facts, with the command that writes it; writes nothing, asks no model |
promote is absent by construction, and so are migrate, view, report, a record import that writes a yes or a no, and record on and off. A baseline is an *approved reference*, and promote writes into .digline/ /baselines/, which is committed — anything landing there arrives in somebody's diff and must arrive because they put it there. A refusal would be a conversation an agent could argue with; an absence is not.
Every tool, the reading ones included, loads the suite it is named. For a suite.py that executes the project's code, in the server's environment.
The reasoning is ADR 0011, and the judgement layer it turns into surface is AGENTS.md.
Install and configure
uv pip install digline-mcp
One server serves one repository: the perimeter is the repo, and multi-project is N named servers rather than a registry.
{
"mcpServers": { "digline-northwind": { "command": "digline-mcp", "args": ["--root", "/Users/you/src/northwind", "--names", "clear"] } } }
--tenant and --env are accepted and verify; they never override. The suite decides, as it does everywhere else in digline.
--names is required, with no default: clear lets the store's names leave as they are, and project projects every answer, so the names leave as tokens from the name table that --name-table module:attribute names; a refusal is not projected yet, and is a sentence (ADR 0054 §8). A configuration with --root alone no longer starts; --names clear keeps what it did. ADR 0054 has the reasons.
What run costs, before it costs it
run takes a mandatory acknowledge_calls that must equal the suite's planned calls to the target. Called without it, the tool refuses and hands back the number:
run(suite="suite.py")
→ refused: this suite plans 100 calls to the target. 20 cases × 5 samples = 100 calls to the target; each answer is judged 3 times by llm_rubric. Call again with acknowledge_calls=100.
run(suite="suite.py", acknowledge_calls=100) → executes
The first call is the probe. An agent cannot spend a hundred model calls without having stated the number — AGENTS.md §7 as a contract rather than as advice.
What never crosses
An MCP response goes into a model's context, and from there into transcripts and caches nobody controls. So the run tools return a verdict-only projection: the name, the identity, the status, the score, the threshold, the tolerance, the measured interval, and the metadata a suite disclosed.
Never the judge's reason — the judge quotes the output, so the reason *is* the output. Never the sentence explaining a suspension, never undisclosed metadata, never a case's inputs, and never a prompt or its digest unless the suite declares Disclosure(artifact_body=True). A declared file outside the perimeter is refused when the run is made; one under .digline or .git is refused by the command that would let it cross. Neither is dropped in silence.