Connect an MCP Client
Step by step instructions to connect Claude, Cursor, ChatGPT, Codex or any MCP client to Cakewalk's MCP server.
Connecting an MCP client to Cakewalk takes a few minutes. You add the server URL, authorize access, and you're ready to go.
Server URL
All clients use the same URL:
https://mcp.getcakewalk.io/mcpBefore You Start
You need an active Cakewalk account with at least the User role.
Your AI assistant must support MCP with OAuth authentication.
Cursor
Click the button below to install automatically:
Or manually:
Open Cursor and go to Settings > MCP.
Click Add new MCP server.
Set the URL to
https://mcp.getcakewalk.io/mcpand authentication to OAuth.Cursor will open your browser to Cakewalk's authorization page.
Review the requested scopes and click Authorize.
Return to Cursor. The connection is active.
Claude Desktop
Run this in your terminal:
The CLI install requires the latest Claude Desktop release. If the command doesn't work yet, add it manually through Settings > MCP Servers using the server URL and OAuth authentication.
Claude Cloud, Cursor Cloud and Other Clients
For any MCP client with a UI for adding servers:
Add a new MCP server.
Set the URL to
https://mcp.getcakewalk.io/mcp.Set authentication to OAuth.
The client will redirect you to Cakewalk's authorization page.
Review the requested scopes and click Authorize.
Done.
Authorization and Scopes
During setup, Cakewalk's consent screen asks you to approve specific scopes. Each scope controls what data the AI assistant can access:
mcp:users.read
Read user profiles and access details
mcp:workapps.read
Read app data (names, permission levels, custom fields)
mcp:requests.read
View access requests
mcp:requests.write
Create and manage access requests
Troubleshooting
"Authorization failed" or blank screen after clicking Authorize Make sure you are logged into Cakewalk in the same browser. Try clearing cookies for idp2.getcakewalk.io and retrying.
Client says "server not found" or "connection refused" Double check the URL: https://mcp.getcakewalk.io/mcp. The trailing /mcp is required.
Tools not showing up in the assistant Your granted scopes determine which tools are available. If you only authorized mcp:users.read, you will not see app or request tools. Reconnect and authorize additional scopes.
Next Steps
MCP Tool Reference: See all available tools, what they do, and what scopes they need.
Last updated
Was this helpful?