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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mangome_statusC | Return bounded MangoMe status without admitting or mutating work. |
| mangome_observeC | Read/inspect derived or canonical context. OBSERVE never creates work identity or truth. |
| mangome_queryC | Resolve/read MangoMe identity, graph, truth and work state through an allow-listed query surface. |
| mangome_workC | Enter/progress governed work through deterministic allow-listed transitions. The semantic worker facade is intentionally more automatic than the precise advanced capability surface. RECONCILE_ASSIGNMENT remains read-only underneath, but when it deterministically proves that the current request is new operational work, the facade immediately performs ENTER_WORK. Ordinary agents must not stop to ask the user for internal WorkIdentity vocabulary. |
| mangome_effectC | Record/reconcile external effects. Unknown outcomes must not be blindly retried. |
| mangome_verifyC | Validate, audit and verify without allowing a worker DONE claim to become trusted completion. |
| mangome_controlD | Perform explicit controller/router/owner operations through the advanced capability layer. |
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 7 tools
Three read-oriented tools overlap heavily: mangome_observe, mangome_query and mangome_status all describe reading MangoMe state, differing only in vaguely stated scope ('context' vs 'identity/graph/truth/work state' vs 'bounded status'). mangome_work and mangome_control also blur, since both concern progressing/operating on governed work. An agent could easily misselect among these.
Every tool uses the same 'mangome_' prefix in snake_case, giving a predictable and readable set. The only minor deviation is that the suffixes mix verb forms (observe, verify, query) with noun forms (effect, work, control, status), which slightly reduces predictability.
Seven tools sits squarely in the well-scoped 3-15 range. Each represents a plausible distinct facet of the domain without obvious filler or a missing major operation.
The surface covers read/query/status, work progression, effect recording, control, and verification, which appears to span the governed-work lifecycle end to end. The heavily abstract descriptions leave some uncertainty about edge operations (e.g., identity creation or effect retraction), so a minor gap is possible.