logicapps-mcp
# Azure Logic Apps MCP Server
[](https://registry.modelcontextprotocol.io/)
[](https://www.npmjs.com/package/logicapps-mcp)
<img src="https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/Logic-Apps.svg" alt="Azure Logic Apps" width="80" align="right">
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. Install
npm install -g logicapps-mcp
# 2. Login to Azure
az 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](docs/GETTING_STARTED.md#cloud-mcp-server-setup) 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
- [Getting Started Guide](docs/GETTING_STARTED.md) - Setup for Claude, Copilot, Cloud MCP Server
- [Available Tools](docs/TOOLS.md) - All 40 tools with descriptions
- [Configuration](docs/CONFIGURATION.md) - Environment variables, auth, SKU differences
- [Changelog](CHANGELOG.md) - Release history
## Development
```bash
npm run dev # Run in development mode
npm test # Run unit tests
npm 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 Azure
npm run test:integration # Tests find resources automatically
```
## License
MIT
TDQS
Scored across 40 tools
Each tool has a clearly distinct purpose, from workflow lifecycle operations to debugging and connection management. Even tools that relate to similar aspects (e.g., run details vs. action IO) are differentiated by specific functionality and descriptions.
All tool names follow a consistent verb_noun pattern with underscores (e.g., cancel_run, get_workflow_definition). There is no mixing of conventions, and the naming is predictable across the entire set.
40 tools is large, but the domain of Azure Logic Apps management is broad, covering workflow CRUD, run history, debugging, connections, cloning, and guidance. Each tool serves a specific need, though some meta-tools (guides) could be consolidated, keeping the count slightly above ideal.
The tool set comprehensively covers the full lifecycle of Logic App workflows: creation, reading, updating, deletion, run management, debugging, connection handling, cloning, and validation. It also includes troubleshooting and authoring guides, leaving no obvious gaps for the intended domain.