Dify.AI
Add Cakewalk's MCP Gateway to Dify from the Tools page. Dify validates the connection before registration.
Last updated
Was this helpful?
Add Cakewalk's MCP Gateway to Dify from the Tools page. Dify validates the connection before registration.
Dify reads remote MCP servers from the Tools page. Add Cakewalk's gateway as an HTTP-based MCP server and Dify validates the connection before registering it.
Custom form on Dify's Tools page. Available from Dify v1.6.0 onwards.
Open Dify and sign in.
Go to the Tools page.
Select MCP.
Click Add MCP Server (HTTP).
Fill the form:
Display Name: Cakewalk
Server URL: https://mcp-gateway.getcakewalk.io/mcp
Unique Identifier: cakewalk (or your chosen slug).
Description: optional.
Submit the form. Dify validates that it can reach Cakewalk's gateway before completing registration.
After registration, Dify initiates the OAuth flow on first tool use. Sign in with your Cakewalk account and approve the Connection in your browser.
In a Dify app, ask the agent to list its available tools. The tools surfaced through the Cakewalk gateway appear in the response. In Cakewalk, the Dify card on My Agents flips to Connected after the first agent call.
Form does not submit (validation error): Dify probes the MCP server URL before completing registration. Confirm mcp-gateway.getcakewalk.io is reachable from Dify's servers (or from your self-hosted Dify network).
OAuth flow does not start: Cakewalk's gateway expects OAuth-aware clients. If Dify falls back to anonymous access, the tool list returns empty. Confirm the Server URL points to /mcp (no trailing slash, no extra path).
Dify v1.6.0: Built-in Two-Way MCP Support from Dify.
Last updated
Was this helpful?
Was this helpful?