Skip to main content

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 eight 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

promote is absent by construction, and so are migrate, view and report. A baseline is an approved reference, and promote writes into .digline/<tenant>/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.

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"]
    }
  }
}

--tenant and --env are accepted and verify; they never override. The suite decides, as it does everywhere else in digline.

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(artifacts=True).

Release files for digline-mcp 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for digline-mcp 0.4.0
File Size Uploaded
digline_mcp-0.4.0.tar.gz 37.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for digline-mcp 0.4.0
File Interpreter ABI Platform
digline_mcp-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 53.9 kB

Release files / digline_mcp-0.4.0.tar.gz

Download URL digline_mcp-0.4.0.tar.gz
Size 37.6 kB
Tags Source
SHA-256 checksum
How to use checksums
ba647218323d104aa18e804f9b78e73bf4a1d2aabfa41b3f79590473fd8c36bb
BLAKE2b-256 checksum
How to use checksums
d3476ae00693ed4a3a150cc13c36df66ad6d964c96533b07542a7ccb31ecd271
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.

Transparency log

Release files / digline_mcp-0.4.0-py3-none-any.whl

Download URL digline_mcp-0.4.0-py3-none-any.whl
Size 16.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2a4b0fdc2996131ae223ec56870d964e3f5841b62c86498ed440b24389d62c7b
BLAKE2b-256 checksum
How to use checksums
61c5460c96d63c35cba25030e802b2a869bca8f0f801d2a570f8b70f924651f4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.4.0 This release

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page