NGOPilotMCP
# NGOPilot
NGOPilot is a local AI agent tailored for NGO operations. It combines the
rebranded agent harness with NGOPilot MCP tools for CareFlow and roster
workflows.
## Repository Layout
- `harness bone/`: NGOPilot agent runtime, CLI, and desktop application
- `MCPcode/`: NGOPilot MCP server and four stateful NGO workflow tools
- `algo-dependencies/CareFlow/`: CareFlow algorithm dependency source
- `algo-dependencies/RosterCopiilot/`: roster algorithm dependency source
The product exposes one user-facing agent: NGOPilot. The MCP server runs as a
first-party stdio extension and retains ownership of workflow validation,
durable jobs, review state, and delivered artifacts.
See [Agent-MCP Architecture Design Plan.md](Agent-MCP%20Architecture%20Design%20Plan.md)
for the product architecture and
[MCP-pre-build algorithm design plan.md](MCP-pre-build%20algorithm%20design%20plan.md)
for the MCP and algorithm boundaries.
TDQS
Scored across 4 tools
Each tool targets a distinct input type and workflow: photos of forms to Excel, audio to meeting notes, government PDFs, and rosters from workbooks. There is no overlap in purpose or input, so an agent can easily select the correct tool.
Three tools share the 'careflow_' prefix, but the fourth uses 'roster_', and none follow a verb_noun pattern. The names are descriptive and readable, but slightly inconsistent in structure and prefix.
Four tools is an ideal size for a domain-specific server, covering several distinct workflows without overwhelming the agent. Each tool has a clear role and earns its place.
Each tool provides a full workflow from input to review to export/publish, covering key NGO operation needs. Minor broader-domain gaps exist (e.g., client management, activity tracking), but the core workflows are well represented.