Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents.

Token-efficient SSH MCP server with hash-verified remote file operations. 6 tools.

Commits and pushes all changes (staged, unstaged, untracked) to remote. Use when you need a quick push of everything at once.

Analyzes current or recent session for errors, inefficiencies, and improvement opportunities across skills, tools, hooks, and communication. Use after completing a task or periodically.

Scans, installs, and configures dev environment: CLI agents, MCP servers, config sync, hooks. Use after setup or when agents/MCP need alignment.

Installs or updates Codex CLI and Gemini CLI to latest versions via npm. Use when CLI agents need installation or update.

Installs MCP server npm packages and registers them in Claude Code. Use when MCP servers need setup or reconfiguration.

Syncs skills and MCP settings from Claude Code to Gemini CLI and Codex CLI via symlinks and config conversion. Use when agent configs need alignment.

Audits CLAUDE.md, AGENTS.md, GEMINI.md for token budget, prompt cache safety, compact instructions, and cross-agent consistency. Use after editing instruction files or before release.

Creates missing instruction files (CLAUDE.md, AGENTS.md, GEMINI.md) and audits all for token budget, prompt cache safety, and cross-agent consistency. Use after setup or when instruction files need alignment.

Removes hex-line hooks, output style, and cached files from the system. Use when hex-line MCP needs to be fully uninstalled.

Builds and queries code knowledge graph for dependency analysis, impact checking, and architecture overview. Use when starting work on unfamiliar codebase or before refactoring.

Creates complete project documentation system (project docs, reference, tasks, tests, presentation). Use when bootstrapping docs from scratch or regenerating all.

Drives a Story through full pipeline (tasks, validation, execution, quality). Use when executing a Story end-to-end from kanban board.

Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.

Creates root documentation files (CLAUDE.md, docs/README.md, standards, principles, tools config). Use for initial project doc setup.

Creates core project docs (requirements, architecture, tech stack, patterns catalog). Use for any project regardless of type.

Creates backend docs (api_spec.md, database_schema.md). Use when project has backend API or database.

Creates design_guidelines.md with WCAG 2.1 compliance and design system docs. Use when project has a frontend.

Creates infrastructure.md and runbook.md (Docker-conditional). Use for DevOps documentation in any project.