Workflow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workflowsA | List all available workflows. Returns: List of available workflow metadata. |
| start_workflowA | Start a new workflow. Args: ctx: MCP context for logging and error handling workflow_id: ID of the workflow to start. Returns: Dictionary containing session ID and first step. |
| complete_stepB | Complete current step and get next step. Args: ctx: MCP context for logging and error handling session_id: ID of the session. result: Optional result from executing the current step. Returns: Dictionary containing next step information. |
| execute_current_stepC | Execute the current step automatically. Args: ctx: MCP context for logging and error handling session_id: ID of the session. Returns: Dictionary containing next step information. |
| get_session_infoC | Get information about a workflow session. Args: ctx: MCP context for logging and error handling session_id: ID of the session. Returns: Dictionary containing session information. |
| list_sessionsB | List all available workflow sessions. Returns: List of session metadata. |
| delete_sessionB | Delete a workflow session. Args: ctx: MCP context for logging and error handling session_id: ID of the session to delete. Returns: True if the session was deleted, False if it didn't exist. |
| create_frameworkB | Create a new workflow framework. Args: ctx: MCP context for logging and error handling schema: The framework schema. name: Optional name to use for the framework file. Returns: The framework ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Tools are largely distinct, focusing on framework creation, session management, and step execution. The only potential confusion is between complete_step and execute_current_step, but their descriptions clarify different actions: completing vs executing steps.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_framework, list_sessions, complete_step). The pattern is uniform and predictable.
With 8 tools, the server covers core workflow operations without being excessive. The number is appropriate for a workflow management server's typical needs.
The tool set covers basic lifecycle (create framework, start, execute steps, manage sessions), but lacks tools for editing workflow definitions, listing steps, or pausing/aborting sessions, which are notable gaps.