Windsurf’s Cascade can run the Moodle and Ed Discussion Model Context Protocol (MCP) servers as local processes or connect to either over a remote URL. moodle mcp connect doesn’t support Windsurf yet, so add both servers by hand. Official reference: Model Context Protocol (MCP), fetched 2026-09-21 (docs.windsurf.com redirects here).

Prerequisites

  • moodle-cli and edstem-cli installed and signed in. See Install and Install.
  • Windsurf installed.
Windsurf reads MCP servers from ~/.codeium/windsurf/mcp_config.json. Open it from Cascade: click the MCPs icon in the top-right of the Cascade panel, or go to Devin Settings → Cascade → MCP Servers. Windsurf rebranded to Devin Desktop; the config path and Cascade panel are unchanged, but the settings menu now reads “Devin Settings”.

Bridge, local

This keeps your MCP access token in the OS keychain instead of in this file.

Remote, header auth

Get <your-token> with moodle mcp connect codex --mode remote --show-token (any supported client’s --show-token prints the same Worker token). That command also writes a Codex entry to ~/.codex/config.toml; delete it afterwards if you don’t use Codex.

Verify the connection

Open the MCPs panel again — a connected server lists its tools; a failed one shows an error you can expand. Windsurf also marks official, first-party servers with a checkmark, which won’t appear for a private Moodle or Ed Worker since those are yours, not a marketplace listing.