Project management methodology graph: route planning, stage-gate decisions and plan checks.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Evaluates gate g.g0 … g.g10 against your evidence. Outcome precedence: Stop > Recycle > Hold > Conditional go > Go, with the rule that fired (outcome_reason). Critical evidence missing or stale → Hold; required non-critical missing, or a waiver without a reason or an approver who decides at this gate → Conditional go; a waiver with both → Go with the Waiver modifier (under regulation a waived critical artifact stays Conditional go until the deviation is recorded with the quality approval); optional gaps are notes. Modifiers: Work started without the gate, Overdue, Stale, Waiver. gate.deciders decide, gate.advisors take part. A disproved key product hypothesis is a Recycle, not a Stop: pass earlier_stage_invalid:true with invalid_stage:'st.discovery'. At G8 (go / no-go), work_started_beyond:true means production was changed before the decision: Hold (R3), not a Go with a modifier. Call without evidence to list what the gate needs. Returns a receipt hash of the inputs.
Gate id, e.g. g.g5
Answer language, default en
Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.
Map artifact id → state or {state, reason, ref, by, date}. A waiver is {state:'waived', reason, by}: by is the role id of a decider of this gate (see gate.deciders, e.g. r.client_owner) or 'name, role'. Unknown ids are reported as warnings with a suggestion.
Overrides both limits. Default: 80% of planned_stage_days, else by approach (predictive/hybrid 10, agile/flow 5); required evidence then waits twice as long
With earlier_stage_invalid: the stage to return to, if known
With earlier_stage_invalid: the artifact that is no longer true, to find where to return
Planned length of the stage in days. With it, missing critical evidence is overdue after 80% of it and missing required evidence after all of it
false → Stop
True if work of later stages already started (adds the 'work started without the gate' modifier; at G8 it is a Hold)
true → Recycle; the answer names the stage to return to
Evaluates gate g.g0 … g.g10 against your evidence. Outcome precedence: Stop > Recycle > Hold > Conditional go > Go, with the rule that fired (outcome_reason). Critical evidence missing or stale → Hold; required non-critical missing, or a waiver without a reason or an approver who decides at this gate → Conditional go; a waiver with both → Go with the Waiver modifier (under regulation a waived critical artifact stays Conditional go until the deviation is recorded with the quality approval); optional gaps are notes. Modifiers: Work started without the gate, Overdue, Stale, Waiver. gate.deciders decide, gate.advisors take part. A disproved key product hypothesis is a Recycle, not a Stop: pass earlier_stage_invalid:true with invalid_stage:'st.discovery'. At G8 (go / no-go), work_started_beyond:true means production was changed before the decision: Hold (R3), not a Go with a modifier. Call without evidence to list what the gate needs. Returns a receipt hash of the inputs.
| Argument | Type | Description |
|---|---|---|
| gate* | string | Gate id, e.g. g.g5 |
| lang | string | Answer language, default en |
| context | object | Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data. |
| evidence | object | Map artifact id → state or {state, reason, ref, by, date}. A waiver is {state:'waived', reason, by}: by is the role id of a decider of this gate (see gate.deciders, e.g. r.client_owner) or 'name, role'. Unknown ids are reported as warnings with a suggestion. |
| grace_days | number | Overrides both limits. Default: 80% of planned_stage_days, else by approach (predictive/hybrid 10, agile/flow 5); required evidence then waits twice as long |
| days_in_stage | number | |
| invalid_stage | string | With earlier_stage_invalid: the stage to return to, if known |
| invalid_artifact | string | With earlier_stage_invalid: the artifact that is no longer true, to find where to return |
| planned_stage_days | number | Planned length of the stage in days. With it, missing critical evidence is overdue after 80% of it and missing required evidence after all of it |
| business_case_valid | boolean | false → Stop |
| work_started_beyond | boolean | True if work of later stages already started (adds the 'work started without the gate' modifier; at G8 it is a Hold) |
| earlier_stage_invalid | boolean | true → Recycle; the answer names the stage to return to |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"gate"
],
"properties": {
"gate": {
"type": "string",
"maxLength": 40,
"description": "Gate id, e.g. g.g5"
},
"lang": {
"enum": [
"en",
"ru"
],
"type": "string",
"description": "Answer language, default en"
},
"context": {
"type": "object",
"properties": {
"ap": {
"type": "string",
"description": "Delivery approach: predictive | agile | flow | hybrid"
},
"sc": {
"type": "string",
"description": "Scale: single (one team) | multi (several teams)"
},
"ui": {
"type": "boolean"
},
"con": {
"type": "string",
"description": "Contract model: fixed | tm | capped | internal (own budget)"
},
"dom": {
"type": "string",
"description": "Project type: software | package | data | infra | process | nonit. package = SaaS / ERP / CRM platform; nonit = any non-IT project (a launch, a programme, an event, a move: add physical for works on site)"
},
"reg": {
"type": "boolean"
},
"svc": {
"type": "boolean"
},
"unc": {
"type": "string",
"description": "Uncertainty (complexity domain): clear | complicated | complex | chaotic"
},
"data": {
"type": "boolean"
},
"date": {
"type": "boolean"
},
"migr": {
"type": "boolean"
},
"size": {
"type": "string",
"description": "Project size: solo | small | medium | large, default medium. solo = one person does all the work (small tailoring, no Daily Scrum or Kanban meeting); small ≈ up to 3 months and 5 people in one team; large ≈ several teams, over 12 months or a programme. Small and solo lower some gate documents one level (never under regulation) and drop the steering committee, large raises some"
},
"integ": {
"type": "boolean"
},
"legacy": {
"type": "boolean"
},
"shared": {
"type": "boolean"
},
"physical": {
"type": "boolean",
"description": "Physical works in any domain: premises, construction, equipment or on-site events (an office move, a fit-out, an event on site). Adds the site inspection (G7), supplier contracts (G5), plan B with a fixed date and the permits note. A non-IT launch, programme or online event is dom=nonit without it"
},
"bottleneck": {
"type": "boolean"
},
"high_stakes": {
"type": "boolean",
"description": "A failure hits customers, money, safety or a regulated function: operational readiness and a rehearsed rollback at G8"
}
},
"description": "Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.",
"additionalProperties": {}
},
"evidence": {
"type": "object",
"description": "Map artifact id → state or {state, reason, ref, by, date}. A waiver is {state:'waived', reason, by}: by is the role id of a decider of this gate (see gate.deciders, e.g. r.client_owner) or 'name, role'. Unknown ids are reported as warnings with a suggestion.",
"propertyNames": {
"type": "string",
"maxLength": 100
},
"additionalProperties": {
"anyOf": [
{
"type": "string",
"maxLength": 20,
"description": "present | missing | stale | waived"
},
{
"type": "object",
"required": [
"state"
],
"properties": {
"by": {
"type": "string",
"maxLength": 200
},
"ref": {
"type": "string",
"maxLength": 500
},
"date": {
"type": "string",
"maxLength": 40
},
"state": {
"type": "string",
"maxLength": 20,
"description": "present | missing | stale | waived"
},
"reason": {
"type": "string",
"maxLength": 1000
}
}
}
]
}
},
"grace_days": {
"type": "number",
"minimum": 0,
"description": "Overrides both limits. Default: 80% of planned_stage_days, else by approach (predictive/hybrid 10, agile/flow 5); required evidence then waits twice as long"
},
"days_in_stage": {
"type": "number",
"minimum": 0
},
"invalid_stage": {
"type": "string",
"maxLength": 100,
"description": "With earlier_stage_invalid: the stage to return to, if known"
},
"invalid_artifact": {
"type": "string",
"maxLength": 100,
"description": "With earlier_stage_invalid: the artifact that is no longer true, to find where to return"
},
"planned_stage_days": {
"type": "number",
"minimum": 0,
"description": "Planned length of the stage in days. With it, missing critical evidence is overdue after 80% of it and missing required evidence after all of it"
},
"business_case_valid": {
"type": "boolean",
"description": "false → Stop"
},
"work_started_beyond": {
"type": "boolean",
"description": "True if work of later stages already started (adds the 'work started without the gate' modifier; at G8 it is a Hold)"
},
"earlier_stage_invalid": {
"type": "boolean",
"description": "true → Recycle; the answer names the stage to return to"
}
}
}For a set of ids: antipatterns in the set and detected by rules, conflicts, redundant alternatives (e.g. seven estimation methods), items to avoid or not applicable here, risks, missing inputs and suggested additions. ok = no antipatterns, conflicts, avoid or not-applicable items; a detected pattern of severity warning (e.g. output over outcome on a client contract) does not change ok.
| Argument | Type | Description |
|---|---|---|
| ids* | array | |
| lang | string | Answer language, default en |
| context | object | Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"ids"
],
"properties": {
"ids": {
"type": "array",
"items": {
"type": "string",
"maxLength": 100
},
"maxItems": 200,
"minItems": 1
},
"lang": {
"enum": [
"en",
"ru"
],
"type": "string",
"description": "Answer language, default en"
},
"context": {
"type": "object",
"properties": {
"ap": {
"type": "string",
"description": "Delivery approach: predictive | agile | flow | hybrid"
},
"sc": {
"type": "string",
"description": "Scale: single (one team) | multi (several teams)"
},
"ui": {
"type": "boolean"
},
"con": {
"type": "string",
"description": "Contract model: fixed | tm | capped | internal (own budget)"
},
"dom": {
"type": "string",
"description": "Project type: software | package | data | infra | process | nonit. package = SaaS / ERP / CRM platform; nonit = any non-IT project (a launch, a programme, an event, a move: add physical for works on site)"
},
"reg": {
"type": "boolean"
},
"svc": {
"type": "boolean"
},
"unc": {
"type": "string",
"description": "Uncertainty (complexity domain): clear | complicated | complex | chaotic"
},
"data": {
"type": "boolean"
},
"date": {
"type": "boolean"
},
"migr": {
"type": "boolean"
},
"size": {
"type": "string",
"description": "Project size: solo | small | medium | large, default medium. solo = one person does all the work (small tailoring, no Daily Scrum or Kanban meeting); small ≈ up to 3 months and 5 people in one team; large ≈ several teams, over 12 months or a programme. Small and solo lower some gate documents one level (never under regulation) and drop the steering committee, large raises some"
},
"integ": {
"type": "boolean"
},
"legacy": {
"type": "boolean"
},
"shared": {
"type": "boolean"
},
"physical": {
"type": "boolean",
"description": "Physical works in any domain: premises, construction, equipment or on-site events (an office move, a fit-out, an event on site). Adds the site inspection (G7), supplier contracts (G5), plan B with a fixed date and the permits note. A non-IT launch, programme or online event is dom=nonit without it"
},
"bottleneck": {
"type": "boolean"
},
"high_stakes": {
"type": "boolean",
"description": "A failure hits customers, money, safety or a regulated function: operational readiness and a rehearsed rollback at G8"
}
},
"description": "Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.",
"additionalProperties": {}
}
}
}One node with its description, conditions, source, level and its links grouped by type, each with a link id (Lxxxx) to cite. Filter with link_types, direction and limit.
| Argument | Type | Description |
|---|---|---|
| id* | string | |
| lang | string | Answer language, default en |
| limit | integer | |
| direction | string | |
| link_types | array |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"maxLength": 100
},
"lang": {
"enum": [
"en",
"ru"
],
"type": "string",
"description": "Answer language, default en"
},
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1
},
"direction": {
"enum": [
"in",
"out",
"both"
],
"type": "string"
},
"link_types": {
"type": "array",
"items": {
"type": "string",
"maxLength": 40
},
"maxItems": 30
}
}
}Call first. Returns the context dimensions and flags (with defaults and how many rules each flag drives), stages, gates, evidence states and levels, the gate outcome precedence and the suggested workflow.
| Argument | Type | Description |
|---|---|---|
| lang | string | Answer language, default en |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"lang": {
"enum": [
"en",
"ru"
],
"type": "string",
"description": "Answer language, default en"
}
}
}Route from presale to closure for a project context. Default is compact (ids by strength + a names dictionary, core items and gate evidence for all stages, about 6–10k characters). Ask for one stage with stages:['st.design'] and format:'full' for reasons, avoid texts and gate details. 'core' = do it here (context rule, flag or gate-critical artifact), at most 8 work items per stage (producers of the gate's critical artifacts first, then context rules, then flags).
| Argument | Type | Description |
|---|---|---|
| lang | string | Answer language, default en |
| format | string | Default compact |
| stages | array | Stage ids or codes, e.g. ['st.analysis','design']. Default: all |
| context | object | Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data. |
| include | array | Default all four |
| min_strength | string | Default: core for all stages, all when stages are given |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"lang": {
"enum": [
"en",
"ru"
],
"type": "string",
"description": "Answer language, default en"
},
"format": {
"enum": [
"compact",
"full"
],
"type": "string",
"description": "Default compact"
},
"stages": {
"type": "array",
"items": {
"type": "string",
"maxLength": 40
},
"maxItems": 20,
"description": "Stage ids or codes, e.g. ['st.analysis','design']. Default: all"
},
"context": {
"type": "object",
"properties": {
"ap": {
"type": "string",
"description": "Delivery approach: predictive | agile | flow | hybrid"
},
"sc": {
"type": "string",
"description": "Scale: single (one team) | multi (several teams)"
},
"ui": {
"type": "boolean"
},
"con": {
"type": "string",
"description": "Contract model: fixed | tm | capped | internal (own budget)"
},
"dom": {
"type": "string",
"description": "Project type: software | package | data | infra | process | nonit. package = SaaS / ERP / CRM platform; nonit = any non-IT project (a launch, a programme, an event, a move: add physical for works on site)"
},
"reg": {
"type": "boolean"
},
"svc": {
"type": "boolean"
},
"unc": {
"type": "string",
"description": "Uncertainty (complexity domain): clear | complicated | complex | chaotic"
},
"data": {
"type": "boolean"
},
"date": {
"type": "boolean"
},
"migr": {
"type": "boolean"
},
"size": {
"type": "string",
"description": "Project size: solo | small | medium | large, default medium. solo = one person does all the work (small tailoring, no Daily Scrum or Kanban meeting); small ≈ up to 3 months and 5 people in one team; large ≈ several teams, over 12 months or a programme. Small and solo lower some gate documents one level (never under regulation) and drop the steering committee, large raises some"
},
"integ": {
"type": "boolean"
},
"legacy": {
"type": "boolean"
},
"shared": {
"type": "boolean"
},
"physical": {
"type": "boolean",
"description": "Physical works in any domain: premises, construction, equipment or on-site events (an office move, a fit-out, an event on site). Adds the site inspection (G7), supplier contracts (G5), plan B with a fixed date and the permits note. A non-IT launch, programme or online event is dom=nonit without it"
},
"bottleneck": {
"type": "boolean"
},
"high_stakes": {
"type": "boolean",
"description": "A failure hits customers, money, safety or a regulated function: operational readiness and a rehearsed rollback at G8"
}
},
"description": "Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.",
"additionalProperties": {}
},
"include": {
"type": "array",
"items": {
"enum": [
"gates",
"avoid",
"notes",
"backbone"
],
"type": "string"
},
"description": "Default all four"
},
"min_strength": {
"enum": [
"core",
"recommended",
"all"
],
"type": "string",
"description": "Default: core for all stages, all when stages are given"
}
}
}Search names, ids, descriptions and aliases in English and Russian (word stems, small typos tolerated). Returns total and the best matches.
| Argument | Type | Description |
|---|---|---|
| lang | string | Answer language, default en |
| type | string | |
| limit | integer | |
| query* | string |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"query"
],
"properties": {
"lang": {
"enum": [
"en",
"ru"
],
"type": "string",
"description": "Answer language, default en"
},
"type": {
"enum": [
"school",
"stage",
"gate",
"scenario",
"stream",
"event",
"practice",
"technique",
"model",
"artifact",
"tool",
"role",
"law",
"antipattern"
],
"type": "string"
},
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1
},
"query": {
"type": "string",
"maxLength": 200
}
}
}Checks an ordered list of steps (stages, gates, events, practices, techniques, notations, artifacts). Errors: empty plan, unknown ids, non-step types, stage order (analysis and design work planned early is only a warning 'early'; building before G3–G5 is an order error), contract after delivery gates, a gate after the step it authorises (G8 after the cutover), antipatterns, avoid or not-applicable items. Warnings: duplicates, redundant alternatives, early work, a cutover with no G8 or go / no-go meeting before it, antipatterns of severity warning. 'Shadow start' looks at the order: G4 or G5 must come before the first build step. 'expected' lists gate evidence not yet produced by earlier steps.
| Argument | Type | Description |
|---|---|---|
| lang | string | Answer language, default en |
| steps* | array | |
| context | object | Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data. |
| evidence | object | Artifacts that already exist |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"steps"
],
"properties": {
"lang": {
"enum": [
"en",
"ru"
],
"type": "string",
"description": "Answer language, default en"
},
"steps": {
"type": "array",
"items": {
"type": "string",
"maxLength": 100
},
"maxItems": 300
},
"context": {
"type": "object",
"properties": {
"ap": {
"type": "string",
"description": "Delivery approach: predictive | agile | flow | hybrid"
},
"sc": {
"type": "string",
"description": "Scale: single (one team) | multi (several teams)"
},
"ui": {
"type": "boolean"
},
"con": {
"type": "string",
"description": "Contract model: fixed | tm | capped | internal (own budget)"
},
"dom": {
"type": "string",
"description": "Project type: software | package | data | infra | process | nonit. package = SaaS / ERP / CRM platform; nonit = any non-IT project (a launch, a programme, an event, a move: add physical for works on site)"
},
"reg": {
"type": "boolean"
},
"svc": {
"type": "boolean"
},
"unc": {
"type": "string",
"description": "Uncertainty (complexity domain): clear | complicated | complex | chaotic"
},
"data": {
"type": "boolean"
},
"date": {
"type": "boolean"
},
"migr": {
"type": "boolean"
},
"size": {
"type": "string",
"description": "Project size: solo | small | medium | large, default medium. solo = one person does all the work (small tailoring, no Daily Scrum or Kanban meeting); small ≈ up to 3 months and 5 people in one team; large ≈ several teams, over 12 months or a programme. Small and solo lower some gate documents one level (never under regulation) and drop the steering committee, large raises some"
},
"integ": {
"type": "boolean"
},
"legacy": {
"type": "boolean"
},
"shared": {
"type": "boolean"
},
"physical": {
"type": "boolean",
"description": "Physical works in any domain: premises, construction, equipment or on-site events (an office move, a fit-out, an event on site). Adds the site inspection (G7), supplier contracts (G5), plan B with a fixed date and the permits note. A non-IT launch, programme or online event is dom=nonit without it"
},
"bottleneck": {
"type": "boolean"
},
"high_stakes": {
"type": "boolean",
"description": "A failure hits customers, money, safety or a regulated function: operational readiness and a rehearsed rollback at G8"
}
},
"description": "Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.",
"additionalProperties": {}
},
"evidence": {
"type": "object",
"description": "Artifacts that already exist",
"propertyNames": {
"type": "string",
"maxLength": 100
},
"additionalProperties": {
"enum": [
"present",
"missing",
"stale",
"waived"
],
"type": "string"
}
}
}
}For one event, practice, technique, notation, tool, artifact or antipattern: does it fit this context (fits / avoid / not_applicable / antipattern), its strength and why, alternatives and their group advice, risks, and which gates require it.
| Argument | Type | Description |
|---|---|---|
| id* | string | e.g. t.planning_poker, p.stage_gating, x.velocity_kpi |
| lang | string | Answer language, default en |
| context | object | Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"maxLength": 100,
"description": "e.g. t.planning_poker, p.stage_gating, x.velocity_kpi"
},
"lang": {
"enum": [
"en",
"ru"
],
"type": "string",
"description": "Answer language, default en"
},
"context": {
"type": "object",
"properties": {
"ap": {
"type": "string",
"description": "Delivery approach: predictive | agile | flow | hybrid"
},
"sc": {
"type": "string",
"description": "Scale: single (one team) | multi (several teams)"
},
"ui": {
"type": "boolean"
},
"con": {
"type": "string",
"description": "Contract model: fixed | tm | capped | internal (own budget)"
},
"dom": {
"type": "string",
"description": "Project type: software | package | data | infra | process | nonit. package = SaaS / ERP / CRM platform; nonit = any non-IT project (a launch, a programme, an event, a move: add physical for works on site)"
},
"reg": {
"type": "boolean"
},
"svc": {
"type": "boolean"
},
"unc": {
"type": "string",
"description": "Uncertainty (complexity domain): clear | complicated | complex | chaotic"
},
"data": {
"type": "boolean"
},
"date": {
"type": "boolean"
},
"migr": {
"type": "boolean"
},
"size": {
"type": "string",
"description": "Project size: solo | small | medium | large, default medium. solo = one person does all the work (small tailoring, no Daily Scrum or Kanban meeting); small ≈ up to 3 months and 5 people in one team; large ≈ several teams, over 12 months or a programme. Small and solo lower some gate documents one level (never under regulation) and drop the steering committee, large raises some"
},
"integ": {
"type": "boolean"
},
"legacy": {
"type": "boolean"
},
"shared": {
"type": "boolean"
},
"physical": {
"type": "boolean",
"description": "Physical works in any domain: premises, construction, equipment or on-site events (an office move, a fit-out, an event on site). Adds the site inspection (G7), supplier contracts (G5), plan B with a fixed date and the permits note. A non-IT launch, programme or online event is dom=nonit without it"
},
"bottleneck": {
"type": "boolean"
},
"high_stakes": {
"type": "boolean",
"description": "A failure hits customers, money, safety or a regulated function: operational readiness and a rehearsed rollback at G8"
}
},
"description": "Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.",
"additionalProperties": {}
}
}
}