# io.github.laveeshb/logicapps-mcp (npm · logicapps-mcp)

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

- Trust score: 70/100 (medium)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- npm · `logicapps-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/laveeshb-logicapps-mcp/logicapps-mcp.md), [page](https://verifymcp.io/servers/laveeshb-logicapps-mcp/logicapps-mcp)

## Channel facts

- Registry: `npm`
- Package: `logicapps-mcp`
- Version: `0.4.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (136 of 137), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 204 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 5511 tokens (~137/item across 40 items; 40 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add laveeshb-logicapps-mcp -- npx -y logicapps-mcp
```

### Codex

```bash
codex mcp add laveeshb-logicapps-mcp -- npx -y logicapps-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "laveeshb-logicapps-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "logicapps-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add laveeshb-logicapps-mcp --command npx --arg -y --arg logicapps-mcp
```

### Hermes

```yaml
mcp_servers:
  laveeshb-logicapps-mcp:
    command: "npx"
    args: ["-y", "logicapps-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "laveeshb-logicapps-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "logicapps-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 70, 0)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-02 (score 70, +57)

- [security regression] Provenance: fail → unverified
- [security regression] Install scripts: pass → unverified
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Maintenance: pass → unverified
- [functional regression] Dependency health: partial → unverified
- [functional regression] License: pass → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional] Licence: MIT

### 2026-08-01 (score 13, +8)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional] Licence: MIT

### 2026-07-31 (score 5, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 6, −76)

- [security regression] Install scripts: pass → unverified
- [security regression] Provenance: fail → unverified
- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: partial → unverified
- [functional regression] Maintenance: pass → unverified
- [functional regression] Dependency health: partial → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] License: pass → unverified
- [functional] Licence: MIT

### 2026-07-27 (score 82, +57)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] License: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] Licence: MIT

### 2026-07-26 (score 25)

First indexed and scored.

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (40)

### `list_subscriptions` (~37 tokens)

List all Azure subscriptions accessible to the authenticated user. Use this first to discover available subscriptions, then use list_logic_apps to find Logic Apps.

### `list_logic_apps` (~93 tokens)

List all Logic Apps in a subscription or resource group. Returns both Consumption and Standard SKUs. Consumption Logic Apps have a single workflow; Standard Logic Apps can have multiple workflows (use list_workflows to see them).

Input parameters:

- `resourceGroupName` (string): Filter by resource group (optional)
- `sku` (string): Filter by SKU type (default: all)
- `subscriptionId` (string, required): Azure subscription ID

### `list_workflows` (~87 tokens)

List workflows within a Logic App. Standard SKU can have multiple workflows; Consumption SKU returns a single workflow with the same name as the Logic App. Use this to discover workflow names before calling other workflow-specific tools.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID

### `get_workflow_definition` (~103 tokens)

Get the full workflow definition JSON for a Logic App workflow. For Consumption SKU, omit workflowName. For Standard SKU, workflowName is required. Use update_workflow to modify the definition.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU, omit for Consumption)

### `get_workflow_triggers` (~102 tokens)

Get trigger information for a workflow including last/next execution times. For Standard SKU, workflowName is required. Use run_trigger to manually fire a trigger, or get_trigger_history to see past executions.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `list_run_history` (~192 tokens)

Get the run history for a workflow with optional filtering. For Standard SKU, workflowName is required. Use search_runs for easier filtering by status/date. After finding a run, use get_run_details and get_run_actions to debug. Returns a nextLink if more pages are available - use skipToken to fetch the next page.

Input parameters:

- `filter` (string): OData filter (e.g., "status eq 'Failed'")
- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `skipToken` (string): Pagination token from a previous response's nextLink to fetch the next page of results
- `subscriptionId` (string, required): Azure subscription ID
- `top` (number): Number of runs to return per page (default: 25, max: 100)
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_run_details` (~110 tokens)

Get detailed information about a specific workflow run including status, timing, and error summary. For Standard SKU, workflowName is required. Use get_run_actions to see which specific action failed.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `runId` (string, required): The run ID to retrieve
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_run_actions` (~128 tokens)

Get the action execution details for a specific workflow run including status, timing, and trackedProperties. For Standard SKU, workflowName is required. Use get_action_io to see actual inputs/outputs for an action.

Input parameters:

- `actionName` (string): Filter to a specific action (optional)
- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `runId` (string, required): The run ID
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_connections` (~74 tokens)

List API connections (e.g., Office 365, SQL, Service Bus) in a resource group. Connections are shared resources used by Logic Apps for authentication. Use get_connection_details or test_connection for more info.

Input parameters:

- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID

### `create_connection` (~291 tokens)

Create a new API connection for a managed connector (e.g., azureblob, sql, servicebus, office365). For OAuth-based connectors (like azureblob with OAuth, office365), returns a consent link that must be opened in a browser to authorize. For parameter-based connectors (like SQL with connection string), provide the parameters directly. Common OAuth connectors: azureblob, office365, outlook, onedrive, sharepoint, dynamicscrm. Common parameter connectors: sql (server, database, username, password), servicebus (connectionString).

Input parameters:

- `connectionName` (string, required): Name for the new connection (e.g., 'azureblob-1', 'my-sql-connection')
- `connectorName` (string, required): Managed connector name (e.g., 'azureblob', 'sql', 'servicebus', 'office365')
- `displayName` (string): Friendly display name for the connection (optional, defaults to connectionName)
- `location` (string, required): Azure region (e.g., 'westus2', 'eastus'). Should match Logic App region.
- `parameterValues` (object): Connection parameters for non-OAuth connectors. Examples: SQL: {server, database, username, password, encryptConnection}. ServiceBus: {connectionString}. Leave empty for OAuth connectors.
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID

### `get_connector_swagger` (~131 tokens)

Get the OpenAPI/Swagger definition for a managed connector (e.g., msnweather, sql, servicebus, office365). Returns available operations, paths, and schemas. ESSENTIAL for discovering correct action paths when creating or updating workflows with connector actions.

Input parameters:

- `connectorName` (string, required): Connector name (e.g., 'msnweather', 'sql', 'servicebus', 'office365', 'azureblob')
- `location` (string, required): Azure region where the connector is available (e.g., 'westus2', 'eastus')
- `subscriptionId` (string, required): Azure subscription ID

### `invoke_connector_operation` (~423 tokens)

Invoke a dynamic operation on an API connection to fetch connection-specific data like dropdown values, schemas, or metadata. This is the equivalent of what the Logic Apps designer does when you click on a dropdown or text field - it calls the connector to populate the options.

WHEN TO USE THIS TOOL:
\- After getting connector swagger with get_connector_swagger, you see operations with 'x-ms-dynamic-values' or 'x-ms-dynamic-schema'
\- You need to list available tables, queues, folders, or other resources from a connection
\- You need to get the schema/columns for a specific table or entity
\- You're authoring a workflow and need to know valid values for action parameters

WORKFLOW FOR AUTHORING WITH CONNECTORS:
1\. Use get_connector_swagger to discover operations and see x-ms-dynamic-values annotations
2\. Use get_connections to find existing connections in the resource group
3\. Use invoke_connector_operation to call the dynamic operation (e.g., GetTables, GetQueues)
4\. Use the returned values to populate your workflow action parameters

COMMON EXAMPLES:
\- SQL: operationId='GetTables' returns list of tables, operationId='GetTable' with table parameter returns column schema
\- Service Bus: operationId='GetQueues' returns available queues
\- SharePoint: operationId='GetDataSets' returns sites, then GetTables for lists
\- Blob Storage: operationId='GetDataSets' returns containers

Input parameters:

- `connectionName` (string, required): Name of the API connection (e.g., 'sql-1', 'servicebus', 'azureblob')
- `operationId` (string, required): The operationId from the connector swagger to invoke (e.g., 'GetTables', 'GetQueues', 'GetDataSets')
- `parameters` (object): Parameters required by the operation. Check the swagger for required parameters. For example, GetTable requires {table: 'tableName'}
- `resourceGroupName` (string, required): Resource group containing the API connection
- `subscriptionId` (string, required): Azure subscription ID

### `get_host_status` (~70 tokens)

Get host status for a Standard Logic App including runtime version, extension bundle version, and diagnostics. Only available for Standard SKU.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID

### `list_workflow_versions` (~81 tokens)

List all versions of a Consumption Logic App workflow with creation and change times. Only available for Consumption SKU.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `top` (number): Number of versions to return (optional)

### `get_trigger_history` (~146 tokens)

Get the execution history of a specific trigger, showing when it fired, succeeded, or failed. Essential for debugging why a workflow didn't run when expected.

Input parameters:

- `filter` (string): OData filter (e.g., "status eq 'Failed'")
- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `top` (number): Number of history entries to return (default: 25, max: 100)
- `triggerName` (string, required): Trigger name to get history for
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_action_repetitions` (~158 tokens)

Get iteration details for actions inside loops (ForEach, Until). Each iteration is a 'repetition' with its own status, inputs, outputs, and trackedProperties. For Standard SKU, workflowName is required. Essential for debugging loop failures.

Input parameters:

- `actionName` (string, required): Action name (the loop action)
- `logicAppName` (string, required): Logic App resource name
- `repetitionName` (string): Specific repetition to get (e.g., '000000', '000001')
- `resourceGroupName` (string, required): Resource group name
- `runId` (string, required): Run ID
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_action_request_history` (~144 tokens)

Get HTTP request/response details for connector actions including retries. Shows actual HTTP calls made to external services with headers, status codes, and timing. For Standard SKU, workflowName is required. Useful for debugging API failures.

Input parameters:

- `actionName` (string, required): Action name (HTTP, connector actions)
- `logicAppName` (string, required): Logic App resource name
- `requestHistoryName` (string): Specific request history entry name
- `resourceGroupName` (string, required): Resource group name
- `runId` (string, required): Run ID
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_trigger_callback_url` (~118 tokens)

Get the callback URL for request-based triggers (HTTP, manual). Returns the URL with SAS token for invoking the workflow. For Standard SKU, workflowName is required. Use run_trigger to test the workflow instead of calling the URL directly.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `triggerName` (string, required): Trigger name
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_scope_repetitions` (~117 tokens)

Get execution details for scope action iterations (Scope, Switch, Condition). Shows which branch executed, status, and trackedProperties. For Standard SKU, workflowName is required.

Input parameters:

- `actionName` (string, required): Scope action name
- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `runId` (string, required): Run ID
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_expression_traces` (~135 tokens)

Get expression evaluation traces for an action. Shows how workflow expressions (e.g., @body(), @variables()) were evaluated at runtime, including the expression text, result value, and any errors. For Standard SKU, workflowName is required. Essential for debugging expression failures.

Input parameters:

- `actionName` (string, required): Action name
- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `runId` (string, required): Run ID
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_workflow_swagger` (~101 tokens)

Get the OpenAPI/Swagger definition for a workflow. Shows trigger schemas and request/response formats. For Standard SKU, workflowName is required. Useful for API documentation or generating client SDKs.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_action_io` (~133 tokens)

Get the actual input/output data for a run action. Fetches content from inputsLink/outputsLink URLs. For Standard SKU, workflowName is required. Essential for debugging data transformation issues.

Input parameters:

- `actionName` (string, required): Action name
- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `runId` (string, required): Run ID
- `subscriptionId` (string, required): Azure subscription ID
- `type` (string): Which content to fetch (default: both)
- `workflowName` (string): Workflow name (required for Standard SKU)

### `search_runs` (~249 tokens)

Search run history with friendly parameters (status, startTime, endTime, clientTrackingId) instead of raw OData filter syntax. For Standard SKU, workflowName is required. Use this instead of list_run_history when filtering by specific criteria. Returns a nextLink if more pages are available - use skipToken to fetch the next page.

Input parameters:

- `clientTrackingId` (string): Filter by correlation/tracking ID
- `endTime` (string): Filter runs starting before this ISO timestamp
- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `skipToken` (string): Pagination token from a previous response's nextLink to fetch the next page of results
- `startTime` (string): Filter runs starting after this ISO timestamp (e.g., 2025-12-24T00:00:00Z)
- `status` (string): Filter by run status
- `subscriptionId` (string, required): Azure subscription ID
- `top` (number): Number of runs to return per page (default: 25, max: 100)
- `workflowName` (string): Workflow name (required for Standard SKU)

### `get_workflow_version` (~87 tokens)

Get a specific historical version's definition. Only available for Consumption Logic Apps. Use list_workflow_versions to see available versions.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `versionId` (string, required): Version ID (from list_workflow_versions)

### `get_connection_details` (~71 tokens)

Get detailed information about a specific API connection including authentication status, configuration, and API reference. Use test_connection to verify the connection is working.

Input parameters:

- `connectionName` (string, required): API connection name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID

### `test_connection` (~69 tokens)

Test if an API connection is valid and working. Checks connection status and validates authentication. Use this to diagnose connector failures in workflow runs.

Input parameters:

- `connectionName` (string, required): API connection name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID

### `enable_workflow` (~98 tokens)

Enable a disabled workflow, allowing it to process triggers and run. For Consumption Logic Apps, enables the entire Logic App. For Standard Logic Apps, enables a specific workflow within the Logic App.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `disable_workflow` (~106 tokens)

Disable an active workflow, stopping it from processing triggers and running. In-progress runs will continue until completion. For Consumption Logic Apps, disables the entire Logic App. For Standard Logic Apps, disables a specific workflow within the Logic App.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `run_trigger` (~141 tokens)

Manually fire a workflow trigger to start a new run immediately, bypassing any schedule or event condition. For Standard SKU, workflowName is required. Use get_workflow_triggers first to find available trigger names. Then use list_run_history to see the result.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `triggerName` (string, required): The name of the trigger to run (e.g., 'manual', 'When_a_HTTP_request_is_received')
- `workflowName` (string): Workflow name (required for Standard SKU)

### `cancel_run` (~117 tokens)

Cancel a running or waiting workflow run. Only runs in 'Running' or 'Waiting' status can be cancelled. For Standard SKU, workflowName is required. Use list_run_history or search_runs to find running runs first.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `runId` (string, required): The run ID to cancel
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `resubmit_run` (~129 tokens)

Resubmit a failed or cancelled workflow run to retry execution with the original inputs. Only runs with status 'Failed', 'Cancelled', or 'Succeeded' can be resubmitted. For Standard SKU, workflowName is required. Use get_run_details to check run status first.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `runId` (string, required): The run ID to resubmit
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `create_workflow` (~289 tokens)

Create a new workflow. For Consumption SKU, creates a new Logic App resource. For Standard SKU, creates a new workflow within an existing Logic App. Requires a valid workflow definition JSON that follows the Logic Apps schema. IMPORTANT: When adding connector actions (e.g., SQL, Service Bus, MSN Weather), use get_connector_swagger first to discover the correct action paths and schemas. For Consumption SKU with connector actions, use the 'connections' parameter to wire up API connections.

Input parameters:

- `connections` (object): API connection references for Consumption SKU. Object mapping connection names used in the definition to their connection details. Example: {"office365": {"connectionName": "office365-test", "id": "/…
- `definition` (object, required): The workflow definition JSON following the Logic Apps schema
- `kind` (string): Workflow kind for Standard SKU (default: 'Stateful')
- `location` (string): Azure region (required for Consumption SKU, e.g., 'westus2', 'eastus')
- `logicAppName` (string, required): Logic App resource name (for Consumption, this becomes the new Logic App name)
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `update_workflow` (~241 tokens)

Update an existing workflow's definition. Replaces the entire definition with the new one. For Standard SKU, workflowName is required. Use get_workflow_definition first to get the current definition, modify it, then update. IMPORTANT: When adding connector actions, use get_connector_swagger to discover correct action paths and schemas. For Consumption SKU with connector actions, use the 'connections' parameter to wire up API connections.

Input parameters:

- `connections` (object): API connection references for Consumption SKU. Object mapping connection names used in the definition to their connection details. Example: {"office365": {"connectionName": "office365-test", "id": "/…
- `definition` (object, required): The new workflow definition JSON following the Logic Apps schema
- `kind` (string): Workflow kind for Standard SKU (default: 'Stateful')
- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `delete_workflow` (~98 tokens)

Delete a workflow. For Consumption SKU, deletes the entire Logic App resource. For Standard SKU, deletes a specific workflow within the Logic App. Use with caution as this action cannot be undone.

Input parameters:

- `logicAppName` (string, required): Logic App resource name
- `resourceGroupName` (string, required): Resource group name
- `subscriptionId` (string, required): Azure subscription ID
- `workflowName` (string): Workflow name (required for Standard SKU)

### `clone_workflow` (~228 tokens)

Clone a Consumption Logic App workflow to a Standard Logic App. IMPORTANT: Always run validate_clone_workflow first to check for compatibility issues before cloning. This copies the workflow definition from a Consumption Logic App to a new workflow in an existing Standard Logic App. The target Standard Logic App must already exist and the target workflow name must not already exist. Connections will need to be reconfigured after cloning.

Input parameters:

- `logicAppName` (string, required): Source Consumption Logic App name
- `resourceGroupName` (string, required): Source Consumption Logic App resource group name
- `subscriptionId` (string, required): Source Consumption Logic App subscription ID
- `targetKind` (string): Workflow kind for the target (default: 'Stateful')
- `targetLogicAppName` (string, required): Target Standard Logic App name (must already exist)
- `targetResourceGroupName` (string, required): Target Standard Logic App resource group name
- `targetSubscriptionId` (string): Target Standard Logic App subscription ID (defaults to source subscription if not provided)
- `targetWorkflowName` (string, required): Name for the new workflow in the Standard Logic App

### `validate_clone_workflow` (~202 tokens)

Validate if a Consumption Logic App workflow can be cloned to a Standard Logic App without actually performing the clone. This checks for unsupported operations, connection compatibility, and other potential issues. Use this before clone_workflow to identify any problems that need to be addressed.

Input parameters:

- `logicAppName` (string, required): Source Consumption Logic App name
- `resourceGroupName` (string, required): Source Consumption Logic App resource group name
- `subscriptionId` (string, required): Source Consumption Logic App subscription ID
- `targetKind` (string): Workflow kind for the target (default: 'Stateful')
- `targetLogicAppName` (string, required): Target Standard Logic App name (must already exist)
- `targetResourceGroupName` (string, required): Target Standard Logic App resource group name
- `targetSubscriptionId` (string): Target Standard Logic App subscription ID (defaults to source subscription if not provided)
- `targetWorkflowName` (string, required): Name for the new workflow in the Standard Logic App

### `get_troubleshooting_guide` (~113 tokens)

Get troubleshooting guidance for Logic Apps issues. Call this when debugging failed runs, expression errors, connection problems, or to understand platform limitations. Returns detailed patterns and solutions.

Input parameters:

- `topic` (string, required): The troubleshooting topic: 'expression-errors' for null checks, type conversions, date handling; 'connection-issues' for OAuth, Managed Identity, auth problems; 'run-failures' for action failures, tr…

### `get_authoring_guide` (~92 tokens)

Get guidance for creating and modifying Logic Apps workflows. Call this when helping users build workflows, understand connector patterns, or set up deployment pipelines.

Input parameters:

- `topic` (string, required): The authoring topic: 'workflow-patterns' for triggers, control flow, error handling; 'connector-patterns' for SQL, Service Bus, Blob, Office 365; 'deployment' for ARM, Terraform, CI/CD

### `get_reference` (~72 tokens)

Get reference documentation for Logic Apps. Call this for comprehensive tool usage details or when users ask about differences between Consumption and Standard SKUs.

Input parameters:

- `topic` (string, required): The reference topic: 'tool-catalog' for all 33 MCP tools with examples; 'sku-differences' for Consumption vs Standard deep dive

### `get_workflow_instructions` (~135 tokens)

Get step-by-step instructions for handling common user requests. CALL THIS FIRST when a user asks high-level questions like 'why is my workflow failing?', 'what does this workflow do?', or 'create a workflow'. Returns detailed sequences of tool calls to complete the task.

Input parameters:

- `topic` (string, required): The instruction topic: 'diagnose-failures' when user asks about failures or errors; 'explain-workflow' to understand what a workflow does; 'monitor-workflows' to check status and health; 'create-work…

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/laveeshb-logicapps-mcp/logicapps-mcp#diagnostics

## Score history

- 2026-08-04: 70
- 2026-08-03: 70
- 2026-08-02: 70
- 2026-08-01: 13
- 2026-07-31: 5
- 2026-07-30: 6
- 2026-07-29: 82
- 2026-07-27: 82
- 2026-07-26: 25

## Links

- npm package: https://www.npmjs.com/package/logicapps-mcp
- Socket report: https://socket.dev/npm/package/logicapps-mcp
- Repository: https://github.com/laveeshb/logicapps-mcp
- Changelog RSS feed: https://verifymcp.io/servers/laveeshb-logicapps-mcp/logicapps-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/laveeshb-logicapps-mcp/logicapps-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/laveeshb-logicapps-mcp/logicapps-mcp