Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.laveeshb/logicapps-mcp

NPM · LOGICAPPS-MCP · SCANNED SEP 20

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

Available components

0 this week 83 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 44 of 138 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_workflow" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 40 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.laveeshb/logicapps-mcp server?

io.github.laveeshb/logicapps-mcp runs locally as an npm package, launched with npx -y logicapps-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · logicapps-mcp

# add to Claude Code
claude mcp add laveeshb-logicapps-mcp -- npx -y logicapps-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "laveeshb-logicapps-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "logicapps-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "laveeshb-logicapps-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "logicapps-mcp"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add laveeshb-logicapps-mcp --command npx --arg -y --arg logicapps-mcp
# ~/.hermes/config.yaml
mcp_servers:
  laveeshb-logicapps-mcp:
    command: "npx"
    args: ["-y", "logicapps-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "laveeshb-logicapps-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "logicapps-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add laveeshb-logicapps-mcp -t stdio -c npx -a -y logicapps-mcp
// mcp.json
{
  "mcpServers": {
    "laveeshb-logicapps-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "logicapps-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 16 Sept 26 −3
    • Security disclosure: fail → unverified functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 13 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/logicapps-mcp@0.4.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 138 packages
Packages resolved 138
Stale 44
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 40 exposed · ~5,511 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cancel_run ~117

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
runIdstringyesThe run ID to cancel
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

clone_workflow ~228

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.

NameTypeReqDescription
logicAppNamestringyesSource Consumption Logic App name
resourceGroupNamestringyesSource Consumption Logic App resource group name
subscriptionIdstringyesSource Consumption Logic App subscription ID
targetKindstringWorkflow kind for the target (default: 'Stateful')
targetLogicAppNamestringyesTarget Standard Logic App name (must already exist)
targetResourceGroupNamestringyesTarget Standard Logic App resource group name
targetSubscriptionIdstringTarget Standard Logic App subscription ID (defaults to source subscription if not provided)
targetWorkflowNamestringyesName for the new workflow in the Standard Logic App

No output schema declared.

No examples provided.

create_connection ~291

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).

NameTypeReqDescription
connectionNamestringyesName for the new connection (e.g., 'azureblob-1', 'my-sql-connection')
connectorNamestringyesManaged connector name (e.g., 'azureblob', 'sql', 'servicebus', 'office365')
displayNamestringFriendly display name for the connection (optional, defaults to connectionName)
locationstringyesAzure region (e.g., 'westus2', 'eastus'). Should match Logic App region.
parameterValuesobjectConnection parameters for non-OAuth connectors. Examples: SQL: {server, database, username, password, encryptConnection}. ServiceBus: {connectionString}. Leave empty for OAuth connectors.
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID

No output schema declared.

No examples provided.

create_workflow ~289

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.

NameTypeReqDescription
connectionsobjectAPI connection references for Consumption SKU. Object mapping connection names used in the definition to their connection details. Example: {"office365": {"connectionName": "office365-test", "id": "/…
definitionobjectyesThe workflow definition JSON following the Logic Apps schema
kindstringWorkflow kind for Standard SKU (default: 'Stateful')
locationstringAzure region (required for Consumption SKU, e.g., 'westus2', 'eastus')
logicAppNamestringyesLogic App resource name (for Consumption, this becomes the new Logic App name)
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

delete_workflow ~98

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

disable_workflow ~106

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

enable_workflow ~98

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_action_io ~133

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.

NameTypeReqDescription
actionNamestringyesAction name
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
runIdstringyesRun ID
subscriptionIdstringyesAzure subscription ID
typestringWhich content to fetch (default: both)
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_action_repetitions ~158

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.

NameTypeReqDescription
actionNamestringyesAction name (the loop action)
logicAppNamestringyesLogic App resource name
repetitionNamestringSpecific repetition to get (e.g., '000000', '000001')
resourceGroupNamestringyesResource group name
runIdstringyesRun ID
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_action_request_history ~144

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.

NameTypeReqDescription
actionNamestringyesAction name (HTTP, connector actions)
logicAppNamestringyesLogic App resource name
requestHistoryNamestringSpecific request history entry name
resourceGroupNamestringyesResource group name
runIdstringyesRun ID
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_authoring_guide ~92

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

NameTypeReqDescription
topicstringyesThe 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

No output schema declared.

No examples provided.

get_connection_details ~71

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

NameTypeReqDescription
connectionNamestringyesAPI connection name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID

No output schema declared.

No examples provided.

get_connections ~74

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.

NameTypeReqDescription
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID

No output schema declared.

No examples provided.

get_connector_swagger ~131

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.

NameTypeReqDescription
connectorNamestringyesConnector name (e.g., 'msnweather', 'sql', 'servicebus', 'office365', 'azureblob')
locationstringyesAzure region where the connector is available (e.g., 'westus2', 'eastus')
subscriptionIdstringyesAzure subscription ID

No output schema declared.

No examples provided.

get_expression_traces ~135

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.

NameTypeReqDescription
actionNamestringyesAction name
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
runIdstringyesRun ID
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_host_status ~70

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

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID

No output schema declared.

No examples provided.

get_reference ~72

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

NameTypeReqDescription
topicstringyesThe reference topic: 'tool-catalog' for all 33 MCP tools with examples; 'sku-differences' for Consumption vs Standard deep dive

No output schema declared.

No examples provided.

get_run_actions ~128

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.

NameTypeReqDescription
actionNamestringFilter to a specific action (optional)
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
runIdstringyesThe run ID
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_run_details ~110

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
runIdstringyesThe run ID to retrieve
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_scope_repetitions ~117

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

NameTypeReqDescription
actionNamestringyesScope action name
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
runIdstringyesRun ID
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_trigger_callback_url ~118

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
triggerNamestringyesTrigger name
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_trigger_history ~146

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.

NameTypeReqDescription
filterstringOData filter (e.g., "status eq 'Failed'")
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
topnumberNumber of history entries to return (default: 25, max: 100)
triggerNamestringyesTrigger name to get history for
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_troubleshooting_guide ~113

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.

NameTypeReqDescription
topicstringyesThe 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…

No output schema declared.

No examples provided.

get_workflow_definition ~103

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU, omit for Consumption)

No output schema declared.

No examples provided.

get_workflow_instructions ~135

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.

NameTypeReqDescription
topicstringyesThe 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…

No output schema declared.

No examples provided.

get_workflow_swagger ~101

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_workflow_triggers ~102

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

get_workflow_version ~87

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

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
versionIdstringyesVersion ID (from list_workflow_versions)

No output schema declared.

No examples provided.

invoke_connector_operation ~423

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

NameTypeReqDescription
connectionNamestringyesName of the API connection (e.g., 'sql-1', 'servicebus', 'azureblob')
operationIdstringyesThe operationId from the connector swagger to invoke (e.g., 'GetTables', 'GetQueues', 'GetDataSets')
parametersobjectParameters required by the operation. Check the swagger for required parameters. For example, GetTable requires {table: 'tableName'}
resourceGroupNamestringyesResource group containing the API connection
subscriptionIdstringyesAzure subscription ID

No output schema declared.

No examples provided.

list_logic_apps ~93

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).

NameTypeReqDescription
resourceGroupNamestringFilter by resource group (optional)
skustringFilter by SKU type (default: all)
subscriptionIdstringyesAzure subscription ID

No output schema declared.

No examples provided.

list_run_history ~192

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.

NameTypeReqDescription
filterstringOData filter (e.g., "status eq 'Failed'")
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
skipTokenstringPagination token from a previous response's nextLink to fetch the next page of results
subscriptionIdstringyesAzure subscription ID
topnumberNumber of runs to return per page (default: 25, max: 100)
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

list_subscriptions ~37

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_workflow_versions ~81

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

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
topnumberNumber of versions to return (optional)

No output schema declared.

No examples provided.

list_workflows ~87

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID

No output schema declared.

No examples provided.

resubmit_run ~129

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
runIdstringyesThe run ID to resubmit
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

run_trigger ~141

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.

NameTypeReqDescription
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
triggerNamestringyesThe name of the trigger to run (e.g., 'manual', 'When_a_HTTP_request_is_received')
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

search_runs ~249

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.

NameTypeReqDescription
clientTrackingIdstringFilter by correlation/tracking ID
endTimestringFilter runs starting before this ISO timestamp
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
skipTokenstringPagination token from a previous response's nextLink to fetch the next page of results
startTimestringFilter runs starting after this ISO timestamp (e.g., 2025-12-24T00:00:00Z)
statusstringFilter by run status
subscriptionIdstringyesAzure subscription ID
topnumberNumber of runs to return per page (default: 25, max: 100)
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

test_connection ~69

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

NameTypeReqDescription
connectionNamestringyesAPI connection name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID

No output schema declared.

No examples provided.

update_workflow ~241

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.

NameTypeReqDescription
connectionsobjectAPI connection references for Consumption SKU. Object mapping connection names used in the definition to their connection details. Example: {"office365": {"connectionName": "office365-test", "id": "/…
definitionobjectyesThe new workflow definition JSON following the Logic Apps schema
kindstringWorkflow kind for Standard SKU (default: 'Stateful')
logicAppNamestringyesLogic App resource name
resourceGroupNamestringyesResource group name
subscriptionIdstringyesAzure subscription ID
workflowNamestringWorkflow name (required for Standard SKU)

No output schema declared.

No examples provided.

validate_clone_workflow ~202

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.

NameTypeReqDescription
logicAppNamestringyesSource Consumption Logic App name
resourceGroupNamestringyesSource Consumption Logic App resource group name
subscriptionIdstringyesSource Consumption Logic App subscription ID
targetKindstringWorkflow kind for the target (default: 'Stateful')
targetLogicAppNamestringyesTarget Standard Logic App name (must already exist)
targetResourceGroupNamestringyesTarget Standard Logic App resource group name
targetSubscriptionIdstringTarget Standard Logic App subscription ID (defaults to source subscription if not provided)
targetWorkflowNamestringyesName for the new workflow in the Standard Logic App

No output schema declared.

No examples provided.

Common questions

What is the io.github.laveeshb/logicapps-mcp server?

io.github.laveeshb/logicapps-mcp is listed in the public MCP registry as io.github.laveeshb/logicapps-mcp. MCP server for Azure Logic Apps - debug workflows, manage runs, and authoring. This page covers its npm package (logicapps-mcp).

Is the io.github.laveeshb/logicapps-mcp server safe to use?

io.github.laveeshb/logicapps-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.laveeshb/logicapps-mcp server expose?

io.github.laveeshb/logicapps-mcp exposes 40 tools: list_subscriptions, list_logic_apps, list_workflows, get_workflow_definition, get_workflow_triggers, and 35 more. Their descriptions and schemas cost roughly 5,511 tokens of context every time the server is loaded.

Is the io.github.laveeshb/logicapps-mcp server still maintained?

io.github.laveeshb/logicapps-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.laveeshb/logicapps-mcp server under?

io.github.laveeshb/logicapps-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.