← Projects

Case studyWork in progress

AGIW MCP

A tool that connects a coding assistant to checks on your computer. It can check whether required software is ready or propose and review changes to files you provide.

Availability Released: server v0.1.0

Result A readiness result, or a report and proposed file changes when available. You decide whether to apply the changes.

Read setup and install instructions

Requires Python 3.10 or later; the coding workflow also needs Node.js 22 or later and two different local models.

Your coding assistantUses AGIW MCP
AGIW MCPChecks on your computer
  • Check readinessStarts no task
  • Run a Nisi taskUses files you provide
  • Optional hosted adviceTask or report to TypeSafe; recorded consent + key
Connector illustration. Readiness, a supplied-file task and optional hosted advice are separate operations.

AGIW MCP, at a glance

What it is

Check readiness without starting a task, run a Nisi coding task on supplied file contents, or request optional hosted advice. You choose whether to apply proposed changes.

What you get

A readiness result, or a report and proposed file changes when available. You decide whether to apply the changes.

Where it stands

  • Released: Server v0.1.0
  • Unreleased source: Later fixes landed on main; no release newer than v0.1.0
  • Not verified: A live request to the hosted checking service in tests

How it works

Then, a Nisi task can follow this workflow

  1. Send the task and file contents
  2. Draft proposed files
  3. Check proposed files
  4. Review; recheck after any repairIf it passes
  5. Return results

Failed checks, tests or review → repair Then checks and review run again.

This Nisi example proposes changes to supplied files. A failed check or review can return for repair within limits. Nisi’s separate review-only mode skips drafting and repair; this connector’s example drafts changes.

Why it helps

Coding assistants need access to local checking tools.

Audience, outcomes, availability and workflow for AGIW MCP.

All projects are work in progress.

Task workflow

AGIW MCP workflow Your assistant sends a task and supplied file contents to the local AGIW MCP server. Readiness is a separate check returning ready or the first fix. Nisi uses local models to draft, check, review and make limited repairs, then returns a report and any available proposed files for you to decide what to apply. Jev is an optional hosted checking service requiring recorded consent and a TypeSafe API key. Checking readiness starts no task. AGIW Suite does not start this server. After repair: recheck, then review Your assistant Task + supplied file contents AGIW MCP Local MCP server Check readiness Ready or the first fix Nisi · local models Draft · check · review Repair returns to checks Jev · hosted checking Optional hosted service Recorded consent + key Report + available files You decide what to apply
AGIW MCP workflow Your assistant sends a task and supplied file contents to the local AGIW MCP server. Readiness is a separate check returning ready or the first fix. Nisi uses local models to draft, check, review and make limited repairs, then returns a report and any available proposed files for you to decide what to apply. Jev is an optional hosted checking service requiring recorded consent and a TypeSafe API key. Checking readiness starts no task. AGIW Suite does not start this server. After repair: recheck, then review Your assistant Task + supplied file contents AGIW MCP Local MCP server Nisi · local models Draft · check · review Repair returns to checks Report + available files You decide what to apply Check readiness Ready or the first fix Jev · hosted checking Optional hosted service Recorded consent + key
Nisi example: a local model drafts proposed files, then checks and separate review examine those proposals. Repairs are limited and must pass fresh checks and review.

Releases

Tagged release v0.1.0 · 2026-10-24