Support Grouping (Multi-MCP Servers)
- Dominant language
- TypeScript
- Stars
- 111
- Forks
- 109
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 20
Description
### Severity
P2 - High (Major functionality broken)
### MCP Server Creation Source
MCP Server in Logic Apps
### Describe the Bug with repro steps
Lower priority for now, may be elevated based upon partner conversations.
Currently, our model is:
1 Logic App = 1 MCP Server
We are anticipating:
1 Logic App = 1 or more MCP Servers
This introduces the need for a grouping concept where a customer can create multiple MCP Servers and then choose when to group specific tools (workflows) together.
The driver for this behavior is that a customer may not want to have conflicting tools i.e. an MCP Server that sends Emails from both Office 365 and Google and don't want ambigous tool names/descriptions that lead to inconsistent behavior.
Each MCP Server will have their own URL. The base URL will be the same but we will unique paths so that a customer can choose to add 1 or more MCP Servers to their Agents.
As part of Grouping feature we will need to support:
- Create
- Read
- Update
- Delate
### 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.