Logicapps MCP server

Read from the package source without running it. The installed server may list more.

• cancel_runwrite action

  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.

• clone_workflow

  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 wi

• create_connectionwrite action

  Create a new API connection for a managed connector (e.g., azureblob, sql, servicebus, office365).

• create_workflowwrite action

  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 Consump

• delete_workflowwrite action

  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.

• disable_workflow

  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.

• enable_workflow

  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.

• get_action_io

  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.

• get_action_repetitions

  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.

• get_action_request_history

  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.

• get_authoring_guide

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

• get_connection_details

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

• get_connections

  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.

• get_connector_swagger

  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.

• get_expression_traces

  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.

• get_host_status

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

• get_reference

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

• get_run_actionswrite action

  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.

• get_run_detailswrite action

  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.

• get_scope_repetitions

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

• get_trigger_callback_url

  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.

• get_trigger_history

  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.

• get_troubleshooting_guide

  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.

• get_workflow_definition

  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.

• get_workflow_instructions

  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.

• get_workflow_swagger

  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.

• get_workflow_triggers

  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.

• get_workflow_version

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

• invoke_connector_operation

  Invoke a dynamic operation on an API connection to fetch connection-specific data like dropdown values, schemas, or metadata.

• list_logic_apps

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

• list_run_historywrite action

  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.

• list_subscriptions

  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_workflow_versions

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

• list_workflows

  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.

• resubmit_runwrite action

  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.

• run_triggerwrite action

  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.

• search_runs

  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.

• test_connection

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

• update_workflowwrite action

  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 'connectio

• validate_clone_workflow

  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.

• Code scan127 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 263 days ago4/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

75/100

higher than 45% of 48,255 servers

Tools

40

the typical server has 7

Tools that change things

25%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

6

more than 85% of 28,688 servers

Logicapps: common questions

Is Logicapps MCP server safe?

Mostly: it is graded B (75/100). Read the Logicapps safety report

How do I install Logicapps?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Logicapps need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Logicapps maintained?

The last commit was 297 days ago (2026-01-11). The latest release is v0.4.3.

How does Logicapps compare with other MCP servers?

safety score 75/100 (higher than 45% of 48,255 servers); tools 40 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.