MangoMe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MANGOME_BACKEND | No | Backend to use: 'memory' for local development without MongoDB, 'mongo' for production with MongoDB. | |
| MANGOME_DATABASE | No | MongoDB database name when using MongoDB backend. | mangome |
| MANGOME_MCP_HOST | No | Host for streamable HTTP transport. | 127.0.0.1 |
| MANGOME_MCP_PORT | No | Port for streamable HTTP transport. | 8000 |
| MANGOME_MONGODB_URI | No | MongoDB connection URI when using MongoDB backend. | mongodb://127.0.0.1:27017 |
| MANGOME_MCP_TRANSPORT | No | MCP transport to use: 'stdio' (default) or 'streamable-http'. | stdio |
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 |
|---|---|
| intake_requestC | Persist and categorize a new assignment before execution. IntakeGov should pass its classification when available. |
| create_specC | Append an immutable specification version for a family. |
| resolveC | Resolve a family, declared contract id, or slice id without semantic guessing. |
| create_projectC | Create or return a project container. |
| create_familyC | Create or return a durable contract/work family. |
| register_contractC | Append a contract contribution. Declared-id collisions are preserved and warned, never overwritten. |
| import_contract_bundleC | Onboard an existing contract plus its existing slices in one explicit operation. |
| submit_planB | Record the mandatory pre-execution plan and return advisory collision warnings. |
| start_sliceC | Start a slice. A matching recorded plan is mandatory; collisions only warn. |
| update_slice_progressA | Persist current slice state. Does not verify or complete work. |
| claim_doneA | Record DONE_CLAIMED. The slice remains open/unverified until its gates are verified. |
| submit_evidenceC | Attach durable evidence to a family, contract, slice, or artifact. |
| set_gateC | Update an acceptance gate with evidence references. Verification still requires all gates PASS/WAIVED. |
| verify_sliceB | Verify a DONE_CLAIMED slice only when every acceptance gate is PASS or WAIVED. |
| statusB | Return deterministic materialized project-management state for one family. |
| read_contextB | Read all current family context. Reading is unrestricted for every agent. |
| compile_execution_contextC | Produce a compact deterministic execution package for IntakeGov/CogC or a worker. |
| graphB | Return confirmed/suggested incoming and outgoing graph edges for an entity. |
| register_modelC | Register a model/access-path identity for empirical execution comparisons. |
| record_execution_receiptC | Record model/agent cost and outcome for a slice; durable cost includes verification, repair and human cost. |
| model_statsC | Return empirical cost/verified-outcome statistics from MangoMe execution receipts. |
| bigbang_scanB | Non-destructively inventory configured filesystem roots; never auto-canonicalizes ambiguous contracts. |
| refresh_viewsB | Run deterministic maintenance and refresh all family status projections without LLM use. |
| attach_artifactC | Register a physical artifact/reference without changing its external storage. |
| link_entitiesB | Create a typed MangoMe graph relation such as ADDS_TO, AMENDS, EXTENDS or REPAIRS. |
| close_planA | Close a plan when that actor no longer intends to execute it; prevents stale collision traffic. |
| request_overrideC | Create an explicit approval request. Common actions are WAIVE_GATE and ACCEPT_SLICE. |
| approve_overrideC | Record an explicit approval decision. Authentication remains the MCP host's responsibility. |
| reject_overrideC | Record an explicit rejection decision. |
| list_approvalsA | List approval requests, optionally filtered by status and subject. |
| set_gate_controlledA | Set a gate with v0.1.1 integrity rules: PASS needs evidence; WAIVED needs approved override. |
| accept_sliceA | Move a VERIFIED slice to ACCEPTED using an approved ACCEPT_SLICE decision. |
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 32 tools
Several tools have unclear boundaries: set_gate and set_gate_controlled are two versions of the same action, and status vs read_context both surface family state, while attach_artifact vs submit_evidence can apply to the same artifact target. Tools like create_family, create_spec, and register_contract are separable only by dense descriptions, so an agent is likely to misselect.
Most tools follow a snake_case verb-first pattern like create_project, submit_plan, and approve_override, which keeps the set readable. However, exceptions such as status, graph, resolve, model_stats, and bigbang_scan break the pattern, and set_gate vs set_gate_controlled adds inconsistency to the same operation.
32 tools is a heavy surface even for a complex lifecycle-management domain. The set includes duplicated gate-setting functionality and peripheral utilities like bigbang_scan and model_stats that make the count feel inflated rather than tightly scoped.
The tool set covers a rich execution lifecycle including intake, planning, slices, gates, evidence, approvals, and model receipts. However, there is no general listing/discovery surface for projects, families, contracts, or slices, and contracts/plans are append-only with no update path, leaving notable operational gaps.