Prerequisites
Before setting up the Relay MCP server, ensure you meet the following requirements:- A valid Cashfree Merchant account with access to Relay. You must sign in with an owner account. User accounts do not have the permissions required to connect to the Relay MCP server.
- Access to a supported AI client: Claude Desktop or ChatGPT (Plus plan or higher).
How MCP works
The Relay MCP server uses the Model Context Protocol to expose Relay’s workflow capabilities as tools that your AI agent can call directly. When you connect the MCP server to your AI client, the agent gains access to a set of tools for creating, updating, and monitoring workflows. You interact with these tools using plain language and the agent translates your instructions into the appropriate tool calls automatically. To connect the Relay MCP server, you provide your AI client with the following server URL and authenticate with your Cashfree owner account.Connect the MCP server
- Claude Desktop
- ChatGPT
Open Customise and Connectors
- Log in to the Claude Desktop application.
- In the left navigation, go to Customise.
- Select Connectors.
- Click the + icon to add connectors, then choose Add custom connectors.
Add the Relay MCP connector
- In Add custom connector, enter a name for the connector (any name you prefer).
- In the MCP Server URL field, enter the following URL.
- Click Add.
The Claude Desktop integration is not available in the Claude web app. You must use the desktop application. Whether connector access requires a paid Claude plan depends on Anthropic’s current policy; check your Claude account if connection is blocked.
Available tools
The Relay MCP server exposes the following tools to your AI agent. These tools are invoked automatically when you use Relay Skills or issue relevant instructions in plain language.Workflows and templates
| Tool | Description |
|---|---|
list_workflows | Lists workflows in your Relay account, including names, IDs, and status. |
create_workflow | Creates a new workflow with a given name and initial configuration. |
update_workflow | Updates an existing workflow’s configuration, including trigger, nodes, and settings. |
set_workflow_status | Activates or deactivates a workflow without changing its configuration. |
list_workflow_versions | Returns the version history of a workflow. |
get_workflow_template | Retrieves a specific workflow template for use when building workflows. |
search_workflow_templates | Searches available workflow templates to find a suitable template. |
Execution and testing
| Tool | Description |
|---|---|
test_workflow_from_ui | Runs a workflow test from the UI-oriented flow to validate configuration. |
list_executions | Returns execution history for workflows, including status and timestamps. |
Connections and credentials
| Tool | Description |
|---|---|
list_credentials | Lists configured connections in your Relay account; can filter by app name (for example gmail or google-sheets). |
create_credential | Creates a new connection to an external app or service in Relay. |
Nodes and triggers
| Tool | Description |
|---|---|
list_nodes | Lists node types that can be added to a workflow. |
get_node_actions | Returns the actions available for a given node (for example Gmail or Google Sheets). |
test_action_node | Tests a configured action node with sample data before you rely on it in production. |
resolve_node_options | Resolves dynamic dropdown options for a node field, such as available spreadsheets. |
list_triggers | Lists available trigger types, including schedule-based and event-based options. |
Data fetchers
| Tool | Description |
|---|---|
list_data_fetcher_templates | Lists input data templates for schedule-based triggers (for example Failed Transactions or Transaction Summary). |
test_data_fetcher | Previews the data a fetcher template returns before attaching it to a trigger. |
What’s next
Relay Skills
Use pre-built skills to create common workflows instantly using plain language.
Create a workflow
Build a workflow manually using the Relay canvas.