Continue
Add Cakewalk's MCP Gateway to Continue by dropping a YAML block file into the .continue/mcpServers/ directory in your workspace.
Last updated
Was this helpful?
Add Cakewalk's MCP Gateway to Continue by dropping a YAML block file into the .continue/mcpServers/ directory in your workspace.
Continue reads MCP server config from YAML or JSON files in the .continue/mcpServers/ directory at your workspace root. Add the Cakewalk gateway as one block. MCP only works in Continue's agent mode.
Continue must be in agent mode to use MCP servers. Other modes do not call MCP tools.
YAML config file in the workspace .continue/mcpServers/ directory.
In your project root, create a file at .continue/mcpServers/cakewalk.yaml. The directory may not exist yet; create it.
In the file, paste:
mcpServers:
- name: cakewalk
type: streamable-http
url: https://mcp-gateway.getcakewalk.io/mcpSave the file.
Switch Continue to agent mode. Continue picks up the new MCP server config on the next agent invocation.
Ask the Continue agent to run a tool exposed by Cakewalk. For example, prompt: "List the connections I have access to through Cakewalk." A successful response means Continue connected to the gateway and discovered tools. In Cakewalk, the Continue card on My Agents flips to Connected after the first agent call.
Continue does not see the server: confirm the file is in .continue/mcpServers/ at the workspace root, not in a subdirectory. Confirm the YAML parses cleanly.
Agent mode is not picking up the tool list: restart Continue or switch out of and back into agent mode to force a config reread.
Continue also accepts JSON config files alongside YAML in the same .continue/mcpServers/ directory. The YAML form above is the documented primary path.
Model Context Protocol in Continue from Continue.
Last updated
Was this helpful?
Was this helpful?