NGOPilotMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NGOPILOT_MCP_STATE_DIR | No | Absolute path to the state root directory. Defaults to ~/.ngopilot-mcp. | |
| NGOPILOT_MCP_ALLOWED_INPUT_ROOTS | No | Colon-separated list of absolute paths allowed as input roots. If omitted, any readable absolute path outside the private job tree is accepted. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| careflow_paper_forms_to_excelA | 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. |
| careflow_meeting_notesA | 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. |
| careflow_government_formsA | 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. |
| roster_copilotA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.