Remote MCP[BETA]
Overview
Remote MCP lets you connect Purple Fabric to an external Model Context Protocol (MCP) server without writing code. Once added, the server's tools are available in Flow Designer, Agents and EGPT under the Remote MCP category. The MCP server must already be running outside Purple Fabric, hosted by you or a third party.
The tool definition does not store anyone's credentials. Each person who uses the tool connects with their own (or a Shared) credential when it runs, so the same MCP tool can be reused in different contexts.
Core Concepts
Authentication Types
Deprecated Features
- In published assets: the feature shows a Deprecated tag in the Flow Designer node panel, Agent tool configuration and EGPT tool configuration. The asset stays active. If a run fails because the server removed the feature, the error says the feature is deprecated on the MCP server.
- In new or draft assets: deprecated features are hidden from the Flow Designer palette, Agent tool selection and EGPT tool selection.
Governance
Remote MCP tools follow the same rules as Custom Functions for credentials, visibility (Private/Public), edit and delete permissions, and use across workflows and agents. The BETA tag includes a feedback option.
How To
Add an MCP Server
Step 1: Open Remote MCP
- Go to Tools and select the Remote MCP tab.
- Click + Add MCP Server (or Add MCP Server in the empty state).
Step 2: Enter details
For OAuth 2.0 (Custom App), select the service provider. If it isn't listed, click + Register New Service, fill in the Client ID and Client Secret from your IT admin, and save. The new service is selected automatically.
Step 3: Discover features
- Click Discover Features.
- Provide a credential for this session:
- No Authentication: nothing to do.
- Key Based: select an existing key, or register a new one (it is saved in Credentials).
- OAuth: select an existing OAuth account, or click Add Account, sign in, and select it.
- Purple Fabric fetches the server's tool list. Each discovered tool shows its Name, Description and Input Schema.
If discovery fails, you see an error such as Authentication Failed or Unreachable Host, with a hint showing whether the problem is the tool configuration, the credential, or the server at runtime.
Step 4: Test a feature (optional)
- Click Test on any discovered tool. The Test Feature window opens with the tool name and description.
- Fill in the input fields (generated from the tool's schema). The window shows Running as:
. - Click Run Test. The raw JSON response or error appears below.
To test with another account, close the window and run Discover Features again. A failed test is logged as a warning but doesn't stop you from saving.
Step 5: Save
Click Save. The button is enabled only after discovery succeeds at least once. The tool definition (name, URL, authentication type and service provider) is saved, but not the credential you used for discovery or testing.