nablr

Security Scan Python 3.12+ PyPI

AI-powered SDLC governance via Model Context Protocol.

nablr (pronounced like "enabler") connects to your AI assistant (Cursor, Claude Desktop, Windsurf) and enforces quality gates across your entire software delivery lifecycle — 18 expert personas, 12 built-in scanners, full workflow orchestration.

Documentation: docs.nablr.dev

Why nablr

AI assistants accelerate typing, not engineering.

What they promised	What actually happens
Ship faster	More code, same bugs
Higher quality	AI-generated tech debt
Reduce costs	Increased rework cycles

nablr is the orchestration layer that fixes this: quality enforcement, workflow context, and persistent state injected directly into your AI assistant via MCP.

What a licence unlocks

nablr needs a licence key. There is no free tier. Buy a plan or the paid 10-day trial at nablr.dev. Your key arrives by email. Then call the set_license_key tool with it.

Capability	With a licence
12 built-in scanners	✅
Workflow orchestration	✅
Codebase mapping	✅
Persona prompts	18 (all)
Rule files + language/framework configs	Ships in every install, plus server-fetched freshness

Installation

Requires uv.

Add to your AI assistant config:

{
  "mcpServers": {
    "nablr": {
      "command": "uvx",
      "args": ["nablr"]
    }
  }
}

Config file locations:

Cursor: ~/.cursor/mcp.json
Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
Windsurf: ~/.codeium/windsurf/mcp_config.json

Restart your AI assistant after saving. Full setup guide at docs.nablr.dev/quickstart.

Quick start

# Entry point — loads nablr context into your AI assistant
activate nablr

# Activate the key from your purchase email
Call set_license_key with sk_nablr_<your-key>

# Invoke a persona
Set agent to developer

# Run a scanner
Scan this directory for technical debt

# Full SDLC workflow
Set agent to discovery  →  Set agent to architect  →  Set agent to developer

Personas

18 expert agents covering every SDLC phase: Discovery, Product Manager, QA Lead, Specifier, Architect, Developer, Tester, Test Designer, PR Reviewer, Scrum Master, Security Owner, Forensic Engineer, Strategist, Platform Engineer, Impact Architect, Migration Planner, Parity Tester, Cutover Engineer.

Every persona requires a licence.

Security

nablr makes exactly one category of outbound call: license validation to nablr-api.nablrco.workers.dev:443. Your code never leaves your machine.

Paid assets are pre-cached to ~/.nablr_cache/assets/ on activation — all subsequent prompt generation works fully offline.

# Verify no unexpected network calls
uv run python scripts/airgap_proof.py

Full security details at docs.nablr.dev/security.

License

Metadata

Release files for nablr 4.15.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 nablr 4.15.0
File	Size	Uploaded
nablr-4.15.0.tar.gz	729.7 kB	Oct 4, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for nablr 4.15.0
File	Interpreter	ABI	Platform	Reset
nablr-4.15.0-py3-none-any.whl 926.7 kB Oct 4, 2026	Python 3	none	any	Details

Total release size: 1.7 MB

Release files / nablr-4.15.0.tar.gz

Download URL	nablr-4.15.0.tar.gz
Size	729.7 kB
Tags	Source
SHA-256 checksum How to use checksums	`631fa318335c6c9e85b947a7149a5aaa00fcfa41a67eb93818574fba9bdc29df`
BLAKE2b-256 checksum How to use checksums	`99bafcbbf64e189b6e4fc65f13ec509accefe051fe576589893c900daa346126`
Upload date	Oct 4, 2026
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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/nablrco/nablr
Publishing commit: github.com/nablrco/nablr/tree/21d0b4787ddd0d94cfd07ccee48eadfee8b2b0ee

Workflow

Publishing configuration: github.com/nablrco/nablr/blob/21d0b4787ddd0d94cfd07ccee48eadfee8b2b0ee/.github/workflows/publish.yml
Publishing logs: github.com/nablrco/nablr/actions/runs/37185905249/attempts/1

Artifact

Subject: nablr-4.15.0.tar.gz
SHA-256 checksum: 631fa318335c6c9e85b947a7149a5aaa00fcfa41a67eb93818574fba9bdc29df Verifying attestations

Release files / nablr-4.15.0-py3-none-any.whl

Download URL	nablr-4.15.0-py3-none-any.whl
Size	926.7 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`a44534167753e8c9d0928d69eeec962ac7430e7091ac767f334372d4097f4e72`
BLAKE2b-256 checksum How to use checksums	`de338ef5e70b83caab1acb216621a033506cb4890fa3481060e6189cb277def6`
Upload date	Oct 4, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/nablrco/nablr
Publishing commit: github.com/nablrco/nablr/tree/21d0b4787ddd0d94cfd07ccee48eadfee8b2b0ee

Workflow

Publishing configuration: github.com/nablrco/nablr/blob/21d0b4787ddd0d94cfd07ccee48eadfee8b2b0ee/.github/workflows/publish.yml
Publishing logs: github.com/nablrco/nablr/actions/runs/37185905249/attempts/1

Artifact

Subject: nablr-4.15.0-py3-none-any.whl
SHA-256 checksum: a44534167753e8c9d0928d69eeec962ac7430e7091ac767f334372d4097f4e72 Verifying attestations