A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Agile Today is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Project management methodology graph: route planning, stage-gate decisions and plan checks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http agile-today-mcp 'https://agile-today.org/api/mcp?src=mcp-registry'
# 2 — ask your agent for something these tools do
# list_context, plan_project, check_gate and 5 more
Agile Today costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ATAll 1 server
agile-today1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http agile-today-mcp 'https://agile-today.org/api/mcp?src=mcp-registry'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lang | string | no | 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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| context | object | no | 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. |
| stages | array | no | Stage ids or codes, e.g. ['st.analysis','design']. Default: all |
| min_strength | string | no | Default: core for all stages, all when stages are given |
| format | string | no | Default compact |
| include | array | no | Default all four |
| lang | string | no | Answer language, default en |
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 crit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gate | string | yes | Gate id, e.g. g.g5 |
| context | object | no | 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 | no | 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 |
| work_started_beyond | boolean | no | True if work of later stages already started (adds the 'work started without the gate' modifier; at G8 it is a Hold) |
| business_case_valid | boolean | no | false → Stop |
| earlier_stage_invalid | boolean | no | true → Recycle; the answer names the stage to return to |
| invalid_artifact | string | no | With earlier_stage_invalid: the artifact that is no longer true, to find where to return |
| invalid_stage | string | no | With earlier_stage_invalid: the stage to return to, if known |
| days_in_stage | number | no | — |
| planned_stage_days | number | no | 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 |
| grace_days | number | no | 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 |
| lang | string | no | Answer language, default en |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | e.g. t.planning_poker, p.stage_gating, x.velocity_kpi |
| context | object | no | 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. |
| lang | string | no | Answer language, default en |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | — |
| context | object | no | 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. |
| lang | string | no | Answer language, default en |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| steps | array | yes | — |
| context | object | no | 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 | no | Artifacts that already exist |
| lang | string | no | Answer language, default en |
Search names, ids, descriptions and aliases in English and Russian (word stems, small typos tolerated). Returns total and the best matches.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| type | string | no | — |
| limit | integer | no | — |
| lang | string | no | Answer language, default en |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| link_types | array | no | — |
| direction | string | no | — |
| limit | integer | no | — |
| lang | string | no | Answer language, default en |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Agile Today or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.3.2.
2.3.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Agile Today can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.