Windsurf
What you get
Connect Windsurf Cascade to Graphory and your IDE gains the same business memory every other AI you use can read and write. Design decisions, code review notes, and cross-repo context flow continuously across every agent and every LLM in your stack.
Graphory-specific setup
These are the pieces Graphory controls. Drop them into Windsurf's Cascade MCP config using the format Windsurf currently documents.
- MCP URL:
https://api.graphory.io/mcp - Auth header:
Authorization: Bearer gs_ak_YOUR_KEY - Get your key: app.graphory.io/settings/api-keys
Example config block, for reference. Windsurf currently uses serverUrl for remote MCP servers:
{
"mcpServers": {
"graphory": {
"serverUrl": "https://api.graphory.io/mcp",
"headers": {
"Authorization": "Bearer gs_ak_YOUR_KEY"
}
}
}
}
serverUrl, not url. Cascade will silently ignore the entry if the key name is wrong.
Once connected, Cascade can call Graphory's MCP tools to search your graph, pull timelines, and write new findings back.
Vendor setup docs
Windsurf's Cascade MCP schema has shifted across releases. We deliberately do not mirror Windsurf's docs here, because they drift. For the current, authoritative setup steps - file paths, UI panels, supported transports - go straight to the source:
Follow their latest instructions and plug in the Graphory URL, header, and API key from above.