Conductor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONDUCTOR_API_PATH | No | API path prefix | /api |
| CONDUCTOR_SERVER_URL | No | Base URL of your Conductor server | http://localhost:8080 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workflowsB | List workflow executions with optional filters. Returns a list of workflow executions matching the criteria. |
| get_workflow_statusA | Get the current status and details of a specific workflow execution by its ID. Returns complete workflow execution details including tasks, input/output, and current status. |
| start_workflowC | Start a new workflow execution. Returns the workflow execution ID of the newly started workflow. |
| pause_workflowA | Pause a running workflow execution. The workflow will pause and can be resumed later. |
| resume_workflowC | Resume a paused workflow execution. The workflow will continue from where it was paused. |
| terminate_workflowC | Terminate a workflow execution. This will stop the workflow and mark it as terminated. |
| restart_workflowB | Restart a workflow execution from the beginning. This creates a new execution with the same input. |
| retry_workflowB | Retry a failed workflow execution from the last failed task. |
| search_workflowsB | Advanced search for workflow executions using query syntax. Supports complex queries with multiple criteria. |
| get_workflow_definitionA | Get the definition of a workflow by name and version. Returns the complete workflow definition including all tasks and configuration. |
| list_workflow_definitionsC | List all registered workflow definitions. Returns metadata about all workflows registered in Conductor. |
| create_workflow_definitionB | Create or update a workflow definition. If the workflow already exists, it will be updated. |
| get_task_detailsB | Get details of a specific task execution by task ID. Returns task status, input/output, and execution details. |
| get_task_logsC | Get execution logs for a specific task. Returns log entries generated during task execution. |
| update_task_statusB | Update the status of a task execution. This is typically used by workers to update task status. |
| get_task_definitionC | Get the definition of a task by name. Returns the task definition including configuration and metadata. |
| list_task_definitionsC | List all registered task definitions. Returns metadata about all tasks registered in Conductor. |
| create_task_definitionB | Create or update a task definition. If the task already exists, it will be updated. |
| get_event_handlersB | Get all event handlers or filter by event and active status. Event handlers define how Conductor responds to external events. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| troubleshoot_workflow | Troubleshoot a failed or stuck workflow |
| analyze_failures | Analyze recent workflow failures and identify patterns |
| create_workflow | Guide to create a new workflow definition |
| monitor_workflow | Monitor a running workflow execution |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Workflow Definitions | List of all registered workflow definitions in Conductor |
| Task Definitions | List of all registered task definitions in Conductor |
| Running Workflows | List of currently running workflow executions |
| Failed Workflows | List of recently failed workflow executions |
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/opensensor/conductor-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server