Skip to main content
The Kestrel MCP server exposes workflow management as tools that AI coding agents (Cursor, Claude Desktop, OpenAI Codex, etc.) can call directly. This lets you create, modify, and monitor workflows through conversational AI.

Prerequisites

Install the Kestrel CLI and authenticate:
The MCP server uses your CLI credentials stored at ~/.kestrel/config.json.

Setup

The MCP server runs as a subcommand of the CLI. Configure your AI tool to run kestrel mcp.

Cursor

Add to ~/.cursor/mcp.json:

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

OpenAI Codex

Add via the Codex CLI:
Or add to ~/.codex/config.toml:
If kestrel isn’t on your PATH, use the full path (e.g., /usr/local/bin/kestrel).

Available Tools

Workflow Management

Workflow Generation

Execution Management

Approval Management

Request Management

Catalog and Integrations

Integration Management

Kubernetes, AWS, and OCI use multi-step flows and must be connected with the CLI (kestrel integrations connect <name>) instead of MCP tools. For credential safety, prefer the CLI’s interactive hidden prompts for secrets rather than pasting tokens into an agent chat.

Example Conversations

Creating a workflow:
“Create a workflow that triggers when a PagerDuty alert fires, runs K8s RCA, and posts results to #incidents on Slack”
The AI agent calls generate_workflow, reviews the result, then create_workflow and activate_workflow. Checking executions:
“Show me the last 5 failed workflow executions and what went wrong”
The agent calls list_workflows, list_executions, then get_execution for failed ones. Approving a gate:
“Are there any pending approvals? Approve the production deployment one”
The agent calls list_pending_approvals, identifies the right one, and calls approve_step. Connecting an integration:
“Connect our PagerDuty account to Kestrel”
The agent calls list_integrations to find the required credential fields, asks you for the values, then calls connect_integration and verifies with test_integration. Requesting a change with no matching workflow:
“Request a Redis cluster for the cache layer”
The agent calls request_workflow. When no workflow matches, it gets back pending_confirmation and asks whether you want to send the request to your platform team; based on your answer, it calls confirm_workflow_request to file or dismiss it.