Make
Add Cakewalk's MCP Gateway to Make using the MCP Client module. The connection authorizes via OAuth with Make's published redirect URI.
Last updated
Was this helpful?
Add Cakewalk's MCP Gateway to Make using the MCP Client module. The connection authorizes via OAuth with Make's published redirect URI.
Make consumes external MCP servers through the MCP Client module. Add Cakewalk's gateway by creating a new MCP server in the module's connection, and Make handles the OAuth flow.
Custom form on the MCP Client module's connection. The connection is created from inside a scenario and can be reused across scenarios.
Open Make and sign in.
Open the scenario where you want Cakewalk access.
Add the MCP Client module to the scenario.
On the MCP Client module, click create a connection.
In the connection window, click + new mcp server.
Enter the server URL: https://mcp-gateway.getcakewalk.io/mcp.
Enter the credential. For OAuth, leave the api key / access token field empty; Make handles the OAuth flow itself.
Make starts the OAuth flow with Cakewalk's gateway. Make's published redirect URI is https://www.make.com/oauth/cb/mcp. Make walks you through the consent flow in your browser. Sign in with your Cakewalk account and approve the Connection.
After the consent flow returns, click save. Make stores the connection on your account. Future scenarios can pick this same connection without re-authenticating.
In the MCP Client module, the available tools dropdown lists tools the Cakewalk gateway exposes. In Cakewalk, the Make card on My Agents flips to Connected after the first agent call.
+ new mcp server option is missing: the connection dropdown lists Make's verified servers first. Scroll or search to find the custom option.
OAuth flow returns to an error page: copy the full callback URL from your browser's address bar and paste it back into the prompt at make.com.
MCP Client app from Make.
Last updated
Was this helpful?
Was this helpful?