Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@NGOPilotMCP Convert the scanned volunteer forms to an Excel workbook"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
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 for the product architecture and MCP-pre-build algorithm design plan.md for the MCP and algorithm boundaries.
Fill a bundled Hong Kong government welfare-form PDF from elder information, with mandatory human review before export. Call list_templates first or start with a template_id and exactly one source: non-empty text, one absolute .jpg/.jpeg/.png path (HEIC/HEIF only when discovery reports support), or an elder_profile object. This tool does not accept a blank government PDF, completed volunteer visit forms, audio, Word, or Excel files. Continue the same job with status, review using every preview field, then export.
Inputs: operation (required), input, job_id, request_id. Returns: object
Convert one local audio recording and one CareFlow report template into reviewed meeting or home-visit notes. Attach audio_path as an absolute .mp3, .wav, .m4a, .aac, .flac, or .ogg path and template_path as an absolute .docx path (or .doc only when the managed CareFlow worker reports legacy conversion support). Use the same tool with operation=start, status, review, export, or burn and the returned job_id. PDF templates, images, and spreadsheets do not belong to this tool.
Inputs: operation (required), input, job_id, request_id. Returns: object
Convert photos or scans of completed CareFlow volunteer visit forms into reviewed records and a CareFlow-generated Excel workbook. For start, provide one or more absolute .jpg, .jpeg, or .png paths in image_paths. Do not route Excel files, audio recordings, or blank government PDF forms to this tool. Continue the same job with status, review, and export; every review must submit all 13 fields.
Inputs: operation (required), input, job_id, request_id. Returns: object
Build and review one weekly RosterCopiilot roster from exactly two named local workbook roles: hc_workbook_path and escort_workbook_path. Both must be absolute .xlsx or .xlsm paths in the native HC timetable and escort-master formats; generic spreadsheets and CareFlow exports do not belong here. Continue the returned job_id with status, review, revalidate, export (review draft), publish (ready-only final), or get_published. Export never publishes or distributes the workbook.
Inputs: operation (required), input, job_id, request_id. Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Document conversion MCP server: PDF to Markdown, image OCR, spreadsheet parsing.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
