Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.xysq.ai/llms.txt

Use this file to discover all available pages before exploring further.

Use the xysq MCP server in Windsurf so Cascade can call xysq tools for memory and identity-aware context directly from your editor. Windsurf supports remote MCP servers over Streamable HTTP natively — no mcp-remote wrapper required.

​
Before You Connect

Sign in to your xysq account at app.xysq.ai.

​
Step 1 — Generate Your API Key

  1. After logging in, click the Connect Agent button.
  2. Select the Windsurf tab (or use the Cursor tab — the schema is compatible).
  3. Click Generate API Key. Copy the xysq_... key — it won’t be shown again.

​
Step 2 — Open Windsurf’s MCP Config

You can edit the config file directly, or use the Cascade UI. Config file path:
OSPath
macOS / Linux~/.codeium/windsurf/mcp_config.json
Windows%USERPROFILE%\.codeium\windsurf\mcp_config.json
UI alternative: open the Command Palette → Windsurf Settings → Cascade → MCP Servers → Add custom server +.

​
Step 3 — Add the xysq Entry

Paste this into mcp_config.json (create the file if it doesn’t exist): 
{
  "mcpServers": {
    "xysq": {
      "serverUrl": "https://api.xysq.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Replace YOUR_API_KEY with the key you generated in Step 1. For safer secret handling, export the key in your shell and reference it via env-var expansion: 
{
  "mcpServers": {
    "xysq": {
      "serverUrl": "https://api.xysq.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:XYSQ_API_KEY}"
      }
    }
  }
}
Then run export XYSQ_API_KEY=xysq_... in your shell before launching Windsurf.
Windsurf uses serverUrl for remote HTTP servers — not url (which is what Cursor uses). Copying the Cursor schema verbatim won’t work.

​
Step 4 — Restart Windsurf

Restart Windsurf so it picks up the new MCP entry. After restart, open Cascade and click the MCPs icon (top-right of the Cascade panel) — xysq should appear in the list with its tools.

​
Step 5 — Connect from Cascade

In any Cascade chat, type: 
Connect to xysq
Cascade will load the tools and authenticate automatically. From there you can ask things like: 
Remember that I prefer tabs over spaces in all projects.

What's my current project context?

​
Pinning Windsurf to a team vault

By default Windsurf connects to your personal vault. To scope it to a specific team, swap the URL: 
{
  "mcpServers": {
    "xysq-acme": {
      "serverUrl": "https://api.xysq.ai/mcp/team/YOUR_TEAM_ID",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Find YOUR_TEAM_ID in Team Settings at app.xysq.ai. On a team-pinned connection, every memory action routes to that team’s vault, personal-vault writes are blocked, and personal-only tools (memory_tags, skill_sync, list_teams) are disabled.

​
Troubleshooting

ProblemFix
xysq doesn’t appear in MCPs panelConfirm you restarted Windsurf after editing the config. Validate the JSON — a missing comma silently breaks the file.
Repeated auth errorsRegenerate the API key in the xysq dashboard and update the Authorization header.
Tools listed but calls failCascade has a 100-tool limit across all MCPs combined. Disable tools you don’t use on other servers.
Wrong vault scopeConfirm you’re using the right serverUrl — /mcp for personal, /mcp/team/<id> for a team.
serverUrl not recognisedYou may have pasted a Cursor schema using url. Windsurf requires serverUrl.

​
Next: install the Skill

The MCP connection gives Cascade the tools. The xysq Skill teaches it how to use them. Install the skill →