Windsurf + Steady

Windsurf integration for Steady

Windsurf is built around the idea that an AI shouldn’t just autocomplete — it should plan, run multi-step changes, and stay coherent across files. Steady plugs into that same loop. Cascade can fetch what your team is working on, what’s blocked, and what’s been promised in goals, then weave that information into whatever it’s about to do.

That tends to matter most when work spans more than one file and one moment. Picking up someone else’s project, returning to your own after a long gap, or scoping a refactor that touches several systems — the human context lives in Steady, and pulling it into Cascade keeps the agent aligned with the team rather than just the codebase.

How it shows up in Cascade

Plan against goals, not just tickets. Before kicking off a Cascade run, ask it to read the relevant Goal Story and recent updates from Steady. The plan it generates anchors on what was actually committed to, not just what a single ticket happens to say.

Long-running edits with team awareness. Cascade is happy to spend many turns working through a change. Steady’s data is available the whole time, so the agent can re-check team activity mid-flow if the work is touching something a teammate just shipped or flagged.

Close the loop with a check-in. When a session wraps, ask Cascade to file your check-in or post a Goal Story update — same conversation, same context, no need to context-switch into the Steady app to recap what just happened.

Mix MCP servers. Cascade can talk to several MCP servers at once, so Steady cohabits cleanly with whatever else you’ve registered — repository tools, issue trackers, calendars. One question, answers drawn from the right combination.

A note on scope

The MCP integration is part of Cascade specifically. Codeium’s lighter-weight in-editor completions and the standalone Codeium extension don’t carry the same connector surface — if you want Steady inside a Codeium experience, Windsurf with Cascade is the right surface to be in.

Installation

The Steady MCP server URL is https://app.steady.space/mcp.

Add Steady to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "steady": {
      "serverUrl": "https://app.steady.space/mcp"
    }
  }
}

You can also register Steady from the Cascade panel: click the MCPs icon in the top right and add a new server pointing at the URL above. Either way, the first tool call kicks off OAuth in your browser; once that completes, Steady is available to every Cascade conversation. Step-by-step instructions live in the AI Assistants doc.

Security

The connection runs on OAuth 2.1 and is scoped to your individual Steady login, so Cascade only reaches the data you’d see if you opened the product yourself. Tokens are stored locally inside your Windsurf install, never shared between teammates, and revoking them in Steady immediately cuts off Cascade’s access.

About Windsurf

Windsurf is Codeium's agentic IDE, built around Cascade — an AI panel that can plan, edit across files, and run extended tasks on your behalf. Cascade speaks the Model Context Protocol, so once Steady is registered as an MCP server it becomes one of the data sources the agent reasons over alongside your repo and terminal.

Frequently asked questions

How does Cascade use Steady?

Cascade pulls Steady tools into the same toolbelt it already uses for editing, running commands, and reading your codebase. Ask it to summarize a Goal Story before refactoring the area it covers, or to draft a check-in once a multi-step Cascade run finishes. The MCP calls happen transparently inside the Cascade conversation — no separate panel, no copy-paste.

Is this useful in Write mode, or just Chat?

Both. The MCP connection is shared across Write and Chat, so you can pull Steady context into a planning conversation, then keep that context as Cascade switches into Write mode and starts editing files. Long Cascade runs that span dozens of edits can keep referring back to the goal you tied them to.

Can the team share a single Windsurf MCP config?

Yes. Drop the Steady entry into ~/.codeium/windsurf/mcp_config.json for personal use, or share a recommended config with your team via your onboarding docs. Each teammate authenticates individually on first use, so the only thing being shared is the server registration itself.

What's a concrete first prompt?

After staging a sizeable change, ask Cascade “post a Goal Story update describing what I just did, in the voice of the most recent updates on this goal.” Cascade reads the diff, pulls the recent updates from Steady to match tone, drafts the new entry, and posts it once you confirm — about as long as it takes to sip coffee.

How does authentication work?

Windsurf authenticates to Steady’s MCP server over OAuth 2.1 against your individual account. Your tokens stay local to your Windsurf install, your view of Steady inside Cascade matches what you’d see in the product, and other teammates’ connections are completely independent.