What would you like to see?
Expansion on #2970 (Workspace-assigned Custom Skills);
Current implementation requires the MCP tool flow to manage auth to the external service in the chat context using tool parameters, or via global env supplied in AnythingLLM config that authorizes all Agent enabled Threads across all Workspaces for each configured MCP server.
Design-Agnostic - MCP Client Session per Workspace/User/Thread rather than per Server, with associated management - possible stepping stone could be to limit available tools in a Workspace according to an 'Enabled Tools' dictionary filtered upon registration to the MCP servers.
Would further enable RBAC for different users to have access to different MCP servers/tools based on their AnythingLLM User and/or Workspace.
What would you like to see?
Expansion on #2970 (Workspace-assigned Custom Skills);
Current implementation requires the MCP tool flow to manage auth to the external service in the chat context using tool parameters, or via global env supplied in AnythingLLM config that authorizes all Agent enabled Threads across all Workspaces for each configured MCP server.
Design-Agnostic - MCP Client Session per Workspace/User/Thread rather than per Server, with associated management - possible stepping stone could be to limit available tools in a Workspace according to an 'Enabled Tools' dictionary filtered upon registration to the MCP servers.
Would further enable RBAC for different users to have access to different MCP servers/tools based on their AnythingLLM User and/or Workspace.