A
licenseNot graded
qualityA
maintenanceEnables AI assistants to securely inspect, search, edit, build, and test explicitly authorized local development projects over MCP, with sandboxed filesystem access and sensitive-file protection.
2
AGPL 3.0
AGIW MCP
by louiscalata
Related Servers
Alternatives to AGIW MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables external agents to inspect and interact with a local single-project workbench via MCP, providing read-only tools for state, audit, resume, readiness, comparison, impact preview, and repair candidates, while proposals are saved for manual confirmation in the workbench.MIT
- AlicenseAqualityBmaintenanceEnables MCP-compatible AI clients to securely access explicitly authorized local project files and run approved development commands with bounded execution and audit logging.1MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to delegate routine coding tasks to a local model in isolated git worktrees, using test results as a gate and the client as the reviewer before changes are merged.5MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to securely operate on a local workstation through MCP by exposing file, shell, and workspace management tools.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables local static analysis of deployed AI model artifacts over MCP, exposing audit, diff, capabilities, and rule-explanation tools without uploading model bytes.199 npm2Apache 2.0
TDQS
A3.9/5.0
Scored across 6 tools
Disambiguation4/5
Each tool targets a distinct phase: readiness gate, informational status, consent management, isolated workflow execution, and pre/post Jev review. The main overlap is agiw_readiness vs agiw_status, both of which report on prerequisites, though descriptions differentiate them (ordered gate with a fix vs. a snapshot of versions/config).
Naming Consistency4/5
All names share a consistent agiw_ prefix, snake_case, and a domain_action shape (agiw_jev_pre, agiw_jev_post, agiw_nisi_run). Minor deviation: agiw_readiness, agiw_status, and agiw_consent are noun-only with no action verb, but they remain readable and predictable.
Tool Count5/5
Six tools is well-scoped for a gate-and-review server: two diagnostic tools, one execution tool, one consent tool, and a pre/post review pair. Every tool has a clear purpose with no filler.
Completeness4/5
The lifecycle (check readiness, run workflow, review before/after via Jev) is fully covered, and read-only-by-design behavior is explicit. The notable gap is that consent can only be granted out-of-band in a terminal, so an agent cannot complete that step itself; there is also no tool to list or inspect prior Jev/nisi results.
Maintenance
ActivityMaintained
ResponsivenessNo issues