Windsurf / Cascade

Bring shared project knowledge into the Cascade coding agent: specifications, design choices, debugging findings and session handoffs. Notes saved here remain available to your other connected agents and MindWiki apps.

Let Cascade prepare setup

Paste this into Cascade with its configuration-editing tools enabled. It can prepare the connection; you complete browser sign-in and any host approval.

Configure Cascade

Open Cascade's Actions (…) → Open MCP config file and merge this server entry into its mcpServers object:

{
  "mcpServers": {
    "mindwiki": {
      "serverUrl": "https://api.mindwiki.io/mcp"
    }
  }
}

Save the file, refresh the servers and complete OAuth from the server's connection controls. Preserve any other configured servers.

Current vendor documentation separates legacy Cascade from the Devin Local agent. If your editor session is running Devin Local, use the Devin guide instead of editing Cascade's configuration.

Complete the MindWiki connection

On MindWiki's authorization page, MindWiki Email + Access Key is the recommended sign-in method. Existing email-and-password accounts can choose Legacy Sign In; Sign in with Apple remains available. All methods open the same account and vault—no replacement account is required. New users choose Create a new vault, save their generated access key and continue. Review the requested permissions and choose read-only access when that is all you need. Access Keys explains the supported methods.

Return to your agent after approving. Your sign-in key belongs on MindWiki's pages, not in chat or an MCP configuration file. The client handles its own OAuth credentials.

Check that it works

Ask your agent:

Use MindWiki to read my account status, then search for a note about one of my projects. Read a matching page and cite its title and path. Tell me if the vault is empty rather than making up a result.

Inspect the tool result and compare it with a page in MindWiki Cloud. For a new vault, the agent can read the operating guide and initialize the starter pages when account status permits it.

To check saving after granting write or capture access, ask “Save a new MindWiki capture titled Connection check with today's date, then read it back and give me its path.” The same file is available in your MindWiki apps.

Useful Cascade workflows

• “Read the project context in MindWiki and identify constraints before editing this feature.”
• “Save the root cause and reproduction steps for this bug so another agent can reuse the finding.”
• “Create a handoff note with what changed, what was verified and what remains.”

Use a shared project page for decisions and separate session notes for individual investigations. That makes it easier for another agent to find the current state without treating every experiment as a final decision.

Troubleshooting

If your configuration has no effect, confirm whether the selected agent is Cascade or Devin Local. On a managed organization, MCP may need to be enabled by an administrator. Refresh the server after configuration changes, and check its authentication state before retrying tool calls.

Permissions and disconnecting

Available tools depend on the scopes you approved, your MindWiki plan and vault permissions, and the tools your client exposes. Free includes one external AI connection with core vault tools. See MCP tool access.

To disconnect just this client, revoke its grant in MindWiki Connections. Other agents keep their own connections. Never send access keys or OAuth tokens to support.

More help

MCP tools · Agent permissions · All AI agents

Setup reference: Cascade MCP documentation, checked October 20, 2026.