---
title: "agent-workflows-mcp"
description: "Agents and DAG workflows as MCP tools: run agent definitions and multi-step workflows from any MCP client, no native subagent support required."
canonical: https://agentpluginsdirectory.com/plugins/agent-workflows-mcp
last-updated: 2026-10-23
---

# agent-workflows-mcp
Agents and DAG workflows as MCP tools: run agent definitions and multi-step workflows from any MCP client, no native subagent support required.
- Slug: agent-workflows-mcp
- Publisher: ndmxjp
- Repository: https://github.com/ndmxjp/agent-workflows-mcp
- Manifest: plugin.json
- Version: 0.2.0
- License: MIT
- Category (editorial): other
- Skills: 1 (agent-workflows)
- MCP servers: 1 (agent_workflows)
- Stars: 0
- Repository created: 2026-09-07
- Repository last pushed: 2026-09-30
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/agent-workflows-mcp
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What agent-workflows-mcp does, in the publisher's words

An MCP server that exposes agents and DAG workflows as plain MCP tools, so a client with no native subagent or workflow feature (or one that deliberately does not enable it) can still delegate multi-step work. Agent Plugins 1.0.0 standardizes skills and MCP servers, agents and workflows are outside the spec, so shipping them as MCP tools is the client-portable route: the same repository works from Kiro-action, Claude Code, Kiro, or any other MCP client.

Definitions live in this repository (definitions/agents/*.md, definitions/workflows/*.json); the server reads them from its own directory, never from the caller's working directory, which may be an untrusted checkout. Every tool returns text. The server never posts to GitHub and needs no GitHub token; the calling agent owns its own reporting channel.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/ndmxjp/agent-workflows-mcp/HEAD/README.md

## Skills

- agent-workflows: How to delegate work through the agent_workflows MCP server, running single agents and multi-step DAG workflows as tool calls. Use when the agent_workflows tools (list_agents, list_workflows, run_agent, run_workflow) are available and a task is worth delegating to a specialized child agent or a pr…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- agent_workflows: transport: stdio; command: npx -y agent-workflows-mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.