mcp-graph-loop
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_project_graphA | Initialize a new project workflow graph with task nodes, phase milestones, dependencies, and validation commands. |
| get_graph_stateA | Retrieve current workflow graph state, including visual ASCII progress table, Mermaid diagram, phase progress, nodes, error logs, and execution timeline. |
| get_phase_statusA | Get phase progress summary, completion percentages, phase gate statuses (BLOCKED, IN_PROGRESS, COMPLETED), and blocking reasons. |
| get_ready_tasksA | Get all task nodes whose dependencies and phase gates are satisfied and are ready to be worked on. |
| start_taskA | Mark a task node as IN_PROGRESS to start working on it. Enforces phase gates before allowing execution. |
| validate_task_loopB | Execute the validation command for a task node with duration tracking and attempt error logging. Streams live output via progress notifications when supported. |
| validate_parallel_tasksA | Run validation commands for multiple READY/IN_PROGRESS tasks concurrently with atomic sequential state accumulation (race-condition free). |
| add_task_nodeA | Add a new task node dynamically into the active workflow graph with optional phase and category. Validates dependency references and checks for cycles before inserting. |
| update_task_nodeA | Update an existing task node properties, phase, status, or validation command. Re-validates dependency references and cycle-checks after update. |
| reset_task_nodeA | Reset a task node status to PENDING and clear its error logs, allowing a fresh retry from the beginning. |
| bulk_reset_phaseA | Reset all FAILED (and optionally IN_PROGRESS) nodes in a phase back to PENDING, skipping COMPLETED nodes. |
| get_node_timelineA | Get chronological execution timeline for a node, including timestamped attempts, exit codes, error logs, and duration in milliseconds. |
| save_graph_stateA | Persist the current workflow state to disk using atomic write (write-to-temp then rename) to prevent corruption. |
| load_graph_stateA | Load a workflow graph state from a JSON file on disk with full Zod schema validation. |
| switch_projectA | Switch the active project context to a different project that was previously initialized with init_project_graph. Lists available projects if the requested one is not found. |
| scaffold_project_docsA | Generate standard project documentation files (Architecture/ER Diagram, Phase-wise Tasks, and Test Cases) in the project workspace based on provided project requirements. Useful for initializing a project plan before creating the graph. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/denishmistry07/mcp-graph-loop'
If you have feedback or need assistance with the MCP directory API, please join our Discord server