MCP
MCP
Foxora uses MCP in two distinct directions: connected plugins can supply tools to Fennec, while Foxora can expose a small read-only tool set to external MCP clients.
MCP overview
Foxora uses MCP in two distinct directions: connected plugins can supply tools to Fennec, while Foxora can expose a small read-only tool set to external MCP clients.
02Adding an MCP server
Studio does not currently provide a generic form for registering an arbitrary MCP URL or stdio command. Add supported external tool access through the live Plugins catalog instead.
03Configuring the Foxora MCP server
The MCP Server page generates configuration for using Foxora from another MCP client; its endpoint and authentication depend on where Studio is running.
04Using MCP-powered tools in tasks
Supported plugin connections add tools to Foxora's discovery surface. Availability in a task still depends on the selected agent, policy, credentials, and any channel-specific restrictions.
05Using Foxora as an MCP server
Use this mode when an external MCP client should call Foxora's deliberately limited read and web tool set. It does not expose the full Fennec execution surface.
06Managing and removing MCP connections
Foxora's outward MCP configuration is owned by the external client. Connected plugin accounts are managed separately in Studio, so remove the correct side of the integration.
07MCP security and troubleshooting
Treat the local and cloud MCP endpoints differently. Desktop loopback is intended for programs on the same computer, while the cloud endpoint requires authenticated requests.