Logicapps Mcp

io.github.laveeshbPublished by GitHub account laveeshbv0.4.3Updated Oct 24, 2026

MCP server for Azure Logic Apps - debug workflows, manage runs, and authoring

Overview

AI-generated overview

An MCP server for Azure Logic Apps that lets an assistant debug workflows, manage runs and author changes in natural language.

What you can do
List and inspect Logic Apps workflows and run history, tracing failures through actions, loops and scopes. Create, update and delete workflows, and enable or disable them. Trigger workflow runs or cancel runs in progress. Discover connectors and create connections. Works with both Consumption and Standard Logic Apps.
When to use it
Use it when you need to investigate failed Azure Logic Apps runs, understand workflow definitions, or create, edit, enable, disable, trigger or cancel workflows through an assistant instead of the portal.
Requirements
Runs locally as an npm package, so Node.js is needed. Requires an Azure CLI login (az login) and Azure permissions on the target subscriptions and Logic Apps. Integration tests connect to real Azure resources.
Before you install
Has write operations: it can create, update and delete workflows, enable or disable them, trigger or cancel runs, and create connections, so changes affect live Azure resources. It acts with the permissions of the logged-in Azure identity; use a least-privilege account and review changes before applying.

Installation

In SourceWeft

  1. Open Logicapps Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Azure Logic Apps MCP Server

[MCP Registry] [npm]

[Azure Logic Apps]

Manage and debug Azure Logic Apps using natural language. Ask your AI assistant to investigate failed runs, explain workflows, or make changes—no portal clicking required.

You:  Why did my order-processing workflow fail this morning?
AI:   Looking at the run history... Found a failed run at 10:15 AM.      The HTTP action "Call-Payment-API" failed with 503 Service Unavailable.      The payment service at api.payments.com was down for 3 minutes.
You:  Add retry logic to that action - 3 attempts with exponential backoff.
AI:   Done. Updated the workflow with retry policy. Want me to test it?

Works with GitHub Copilot, Claude Desktop, or any MCP-compatible AI client. Supports both Consumption and Standard Logic Apps.

Quick Start

bash
# 1. Installnpm install -g logicapps-mcp
# 2. Login to Azureaz login
# 3. Configure your AI assistant (example for VS Code)

Add to .vscode/mcp.json in your workspace:

json
{  "servers": {    "logicapps": {      "type": "stdio",      "command": "logicapps-mcp"    }  }}

Reload VS Code and start chatting with Copilot about your Logic Apps!

Cloud MCP Server: Need a hosted deployment? See the Getting Started Guide for Azure deployment instructions.

Features

  • 40 Tools for Logic Apps operations: list, debug, create, update, delete workflows
  • Dual SKU Support: Works with both Consumption and Standard Logic Apps
  • Run Debugging: Trace failures through actions, loops, and scopes
  • Write Operations: Create workflows, run triggers, cancel runs
  • Connector Support: Discover connectors, create connections

Example Prompts

"List my Logic Apps in subscription xyz""Show failed runs from the last 24 hours""What went wrong in run ID abc123?""Add retry logic to the HTTP action""Disable the order-processing workflow"

Documentation

Development

bash
npm run dev              # Run in development modenpm test                 # Run unit testsnpm run test:integration # Run integration tests (requires Azure setup)npm run test:all         # Run all tests

Integration Testing

Integration tests run against real Azure resources. They auto-discover your subscriptions and Logic Apps:

bash
az login                     # Login to Azurenpm run test:integration     # Tests find resources automatically

License

MIT

Source: README.md at commit 49fd90c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts