Azure / Azure/LogicAppsUX

Enable/Disable whether a workflow considered a MCP tool or not

Open
#8,210 0 comments 0 reactions 1 assignee Claimed by @preetriti1 View on GitHub
MCP
Dominant language
TypeScript
Stars
111
Forks
109
Avg merge
1d 23h
Merged PRs (30d)
20

Description

### Severity

P1 - Critical (Blocking production)

### MCP Server Creation Source

MCP Server in Logic Apps

### Describe the Bug with repro steps

Currently, if a workflow has an HTTP Trigger and HTTP response it is considerd an MCP Tool .

There are some scenarios where a customer may not want to expose that workflow as an MCP Tool. We need to provide the ability to enable/disable whether or not the workflow is a Tool.

This may require an app setting to be used under the hood

NOTE: Even if the workflow is not considered a tool, the customer may still want it enabled.

### Screenshots or Videos

_No response_

### Environment

NA

### Are you experiencing a regression?

_No response_

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.