Logicapps Mcp
Let your coding agent inspect Logic App run history, debug failed workflows, and assist with workflow authoring from the IDE.
Overview
logicapps-mcp is a MCP server for the Operate phase that lets agents debug Azure Logic Apps workflows, manage runs, and help with authoring.
What is this MCP server?
- Debug Azure Logic App workflow runs and execution traces via MCP tools
- Manage and inspect workflow runs without switching to the Azure Portal
- Support workflow authoring assistance from Claude Code, Cursor, or Codex
- stdio npm package logicapps-mcp v0.4.3 for local agent wiring
- Targets Azure Logic Apps integrations common in solo SaaS and webhook glue
- Package version 0.4.3 on npm as logicapps-mcp
- Transport: stdio
- Repository: github.com/laveeshb/logicapps-mcp
Community signal: 4 GitHub stars.
What problem does it solve?
Chasing Logic App failures in the Azure Portal breaks your agent-assisted coding flow and slows down fixes to production automations.
Who is it for?
Indie builders running Azure Logic Apps for webhooks, schedules, or B2B integrations who want run-level debugging inside Claude Code or Cursor.
Skip if: Teams with no Azure footprint or builders who only need one-off HTTP scripts without Logic Apps.
What do I get? / Deliverables
Your agent can query runs and workflow context through MCP so you iterate broken Logic Apps from the same session where you edit code.
- Agent-callable tools to inspect and debug Logic App workflow runs
- Faster iteration on failed automations from the coding session
- Assisted workflow authoring context surfaced to the agent
Recommended MCP Servers
Journey fit
Logic Apps run in production; the server's emphasis on debugging runs and managing executions fits the Operate phase where you fix and tune live automation. Iterate is the shelf for tuning workflows, re-running failed branches, and adjusting definitions after you see real failures—not one-off greenfield coding.
How it compares
Azure Logic Apps MCP integration, not a generic workflow skill or Terraform module.
Common Questions / FAQ
Who is logicapps-mcp for?
Solo and small-team builders using Azure Logic Apps who want their AI agent to debug runs and manage workflows via the Model Context Protocol.
When should I use logicapps-mcp?
Use it when a Logic App fails in production or staging and you want run history, debugging, and authoring help without leaving your agent IDE.
How do I add logicapps-mcp to my agent?
Install the npm package logicapps-mcp, configure stdio MCP in Claude Code or Cursor, and authenticate to Azure with credentials your environment already uses for Logic Apps access.