Agile Today
Server Details
Project management methodology graph: route planning, stage-gate decisions and plan checks.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 8 tools
Each tool has a distinct entry point: check_gate (gate vs evidence), check_mix (set of ids), validate_plan (ordered steps), explain_node, search_graph, list_context, plan_project, when_to_use. However check_mix and validate_plan both detect antipatterns/conflicts, and check_gate overlaps validate_plan's gate checks, so an agent could occasionally pick the wrong one. Descriptions largely disambiguate these overlaps.
Seven of eight names follow a clean snake_case verb_noun pattern (check_gate, check_mix, explain_node, list_context, plan_project, search_graph, validate_plan). Only when_to_use breaks the verb_noun mold with a question-style name, a minor deviation that is still readable and snake_case-consistent.
Eight tools is well-scoped for a rich agile/PM advisory domain, covering discovery, search, planning, validation, and gate checking without redundancy. Each tool clearly earns its place.
The surface covers a full lifecycle: context discovery (list_context), lookup (search_graph, explain_node), planning (plan_project), validation (validate_plan, check_mix), gate evaluation (check_gate), and contextual advice (when_to_use). Minor gaps like no explicit plan-comparison or export operation, but core workflows are fully covered.
Available Tools
8 toolscheck_gateCheck a gateARead-onlyIdempotentInspect
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.
Inputs: gate (required), lang, context, evidence, +8 more.
check_mixCheck a mix of practicesBRead-onlyIdempotentInspect
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.
Inputs: ids (required), lang, context.
explain_nodeExplain a nodeARead-onlyIdempotentInspect
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.
Inputs: id (required), lang, limit, direction, +1 more.
list_contextList context optionsARead-onlyIdempotentInspect
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.
Inputs: lang.
plan_projectPlan a project routeBRead-onlyIdempotentInspect
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).
Inputs: lang, format, stages, context, +2 more.
search_graphSearch the graphBRead-onlyIdempotentInspect
Search names, ids, descriptions and aliases in English and Russian (word stems, small typos tolerated). Returns total and the best matches.
Inputs: query (required), lang, type, limit.
validate_planValidate a planARead-onlyIdempotentInspect
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.
Inputs: steps (required), lang, context, evidence.
when_to_useWhen to use an itemARead-onlyIdempotentInspect
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.
Inputs: id (required), lang, context.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Project planning tool for critical path calculations.
Draft-safe project planning: tasks, dependencies, resources, schedules and cost metrics.
A project planning board your AI reads and updates over MCP, so the plan stays one plan.
Project scheduling: Gantt chart, dependencies, baselines, reports and AI agents
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI orchestrators to manage hierarchical implementation roadmaps with phases, tasks, and plan-change tracking.Apache 2.0
- FlicenseAqualityNot gradedmaintenanceProvides structured project management through phase-based workflows, enabling planning, execution tracking, compliance checking, and automated documentation for software development projects.12-
- AlicenseBqualityBmaintenanceGuides product design through mandatory phases—discovery, definition, prioritization, flows, and verification—so an AI assistant can run a project from problem to verified scope, with strict or free progression modes.36170 npm3MIT
- FlicenseNot gradedqualityCmaintenanceEnforces work-readiness gates by tracking project plots, plans, stakeholder views, slots, stops, and journal entries via REST and MCP, with LLM-based plan agreement and result verification.-
Glama MCP Gateway
Add one secure layer between your agents and this server.