INDIVIDUAL MCP TOOL

search_graph

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

agile-today.orgnone authenticationAvailability not checked

LIVE ENDPOINT

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

No auth detected

Connect to this endpoint to inspect the live schema for search_graph and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

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.

list_context — Call first.
plan_project — Route from presale to closure for a project context.
check_gate — Evaluates gate g.
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.
check_mix — For a set of ids: antipatterns in the set and detected by rules, conflicts, redundant alternatives (e.
validate_plan — Checks an ordered list of steps (stages, gates, events, practices, techniques, notations, artifacts).
explain_node — One node with its description, conditions, source, level and its links grouped by type, each with a link id (Lxxxx) to cite.