Cross-Server AI Tool and MCP Integration for AI Agents

Enable AI Agents to Access AI Tools and MCP Servers Across Multiple PowerShell Universal Instances
Currently, AI Agents in PowerShell Universal can only use AI Tools that are available on their local PSU instance. This limitation makes it difficult to build AI-driven workflows that span multiple specialized PSU environments.
I would like to request support for cross-server AI Tool discovery and execution, preferably by allowing AI Agents to consume MCP (Model Context Protocol) servers from other PowerShell Universal instances.

Proposed Solution
Allow administrators to register remote MCP servers and/or remote AI Tool providers from other PSU instances and expose them to local AI Agents as if they were native tools.

Possible implementation options:

• Register one or more remote MCP servers per PSU instance.
• Allow AI Agents to access tools published by trusted remote MCP servers.
• Support authentication, authorization, and tool scoping for remote resources.
• Provide the option to selectively expose AI Tools across PSU environments.

Example Use Case
We operate two dedicated PowerShell Universal environments:

• FW-PSU: Firewall management and firewall-related automation
• SM-PSU: Service management and service request processing

A typical workflow involves service requests for new firewall rules.
Today, the process looks like this:

1. An AI Agent runs on SM-PSU.
2. The agent uses a local AI Tool to extract IP addresses and FQDNs from the service request.
3. The agent invokes another local AI Tool that calls a custom API exposed by FW-PSU.
4. That API determines the corresponding firewall objects and returns the results.
5. The agent then uses another local AI Tool to generate comments or enrich the service request.

This requires additional custom API endpoints solely to bridge the gap between the two PSU environments.

Expected Benefit
If MCP servers from multiple PSU instances could be connected and made available to AI Agents, the agent on SM-PSU could directly use firewall-related tools hosted on FW-PSU.

Benefits include:

• Reduced integration complexity
• Elimination of custom API bridge endpoints
• Better separation of responsibilities between PSU instances
• Improved reuse of existing AI Tools
• Faster implementation of cross-domain AI workflows
• More scalable architecture for organizations operating multiple PSU environments

Example
Instead of:
SM Agent → Local Tool → Custom FW API → FW Logic → Local Tool
The workflow could become:
SM Agent → Remote FW MCP Tool → Result
This would provide a cleaner and more maintainable architecture while leveraging the existing MCP ecosystem and AI Tool framework within PowerShell Universal.

Business Value
Organizations often deploy multiple PowerShell Universal instances that are responsible for different operational domains such as Service Management, Identity Management, Firewall Management, Cloud Operations, or Infrastructure Automation. Enabling AI Agents to consume remote MCP servers and AI Tools would significantly improve interoperability between these environments and reduce the need for custom integration layers.