Developer Tools

agile-today.org

An MCP server for planning software projects, evaluating gates, and advising when to use practices or tools while detecting conflicts and antipatterns.

1 endpoint8 known toolsFirst detected October 4, 2026Last detected October 4, 2026

ENDPOINT 1

https://agile-today.org/api/mcp?src=mcp-registry

No auth detected

MCP server metadata

Name: agile-today
Version: 2.3.1

Capabilities

tools.listChangedprompts.listChanged

Server instructions

Methodology graph for project management, business and systems analysis (read-only, deterministic). Workflow: list_context → plan_project (compact) → plan_project for the current stage (full) → check_gate at each gate → validate_plan for a proposed plan. Every answer is an envelope {graph_version, data, warnings, errors}; errors carry did_you_mean. Cite link ids (Lxxxx) from explain_node. Verdicts are recommendations; people decide.

Known tools 8

list_context

Call first.

Inferred read-only

plan_project

Route from presale to closure for a project context.

Inferred read-only

check_gate

Evaluates gate g.

Inferred read-only

when_to_use

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.

Inferred read-only

check_mix

For a set of ids: antipatterns in the set and detected by rules, conflicts, redundant alternatives (e.

Inferred read-only

validate_plan

Checks an ordered list of steps (stages, gates, events, practices, techniques, notations, artifacts).

Inferred read-only

search_graph

Search names, ids, descriptions and aliases in English and Russian (word stems, small typos tolerated).

Inferred read-only

explain_node

One node with its description, conditions, source, level and its links grouped by type, each with a link id (Lxxxx) to cite.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.agile-today]
url = "https://agile-today.org/api/mcp?src=mcp-registry"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "agile-today": {
      "type": "http",
      "url": "https://agile-today.org/api/mcp?src=mcp-registry"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: agile-today
Remote MCP URL: https://agile-today.org/api/mcp?src=mcp-registry

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "agile-today": {
      "url": "https://agile-today.org/api/mcp?src=mcp-registry"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "agile-today": {
      "type": "http",
      "url": "https://agile-today.org/api/mcp?src=mcp-registry"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "agile-today",
  "transport": "streamable-http",
  "url": "https://agile-today.org/api/mcp?src=mcp-registry"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.