Resonant + Windsurf
MCP auto-discovery.
Voice input.
One workspace.
Windsurf is an AI-native IDE. Resonant's MCP server auto-configures, giving Windsurf access to your meetings, dictations, and ambient work context. Voice input for faster prompts. MCP for persistent memory.
The most context-rich AI coding experience — spoken, not typed. Everything processed locally on your Mac.
Used by engineers at
The gap
Windsurf Cascade is
only as good as
the context you give it.
Every time you abbreviate a Cascade prompt because typing the full version takes too long — that's a worse outcome. The constraints you left out. The edge case you didn't mention. The meeting decision you didn't reference because it wasn't in a file.
The bottleneck isn't Windsurf. It's the gap between what you know and what reaches the model. Voice input and MCP close it.
“add websocket support for real-time updates”
Missing: which events, what payload format, reconnection strategy, auth on the socket, backpressure handling.
“Add websocket support for real-time order status updates. Three event types: order_created, status_changed, and order_completed. Each payload includes the order ID, timestamp, and new status enum. Use the existing JWT for socket auth — validate on connection, not per message. Add exponential backoff reconnection on the client with a max of 5 retries. If the server queue backs up past 1000 messages, drop oldest first.”
Full spec. Dictated in 15 seconds. Windsurf builds it right the first time.
MCP integration
Windsurf can query your
entire voice workspace.
Resonant exposes 11 MCP tools over a local socket. Windsurf discovers them automatically. Your meetings, dictations, memos, and ambient screen context become searchable mid-conversation — no copy-pasting, no context switching.
What did the team decide about the caching strategy in this morning's standup?
Using MCP tool: search("caching strategy standup", type: "meeting")
From your 9:15am standup (Zoom, 14 min): You agreed to use Redis for session cache with a 30-minute TTL. Marcus is handling the invalidation logic. You flagged that the current cache-aside pattern in the product service needs to be replaced before launch.
I dictated a memo about the event-driven architecture for notifications — use that as the spec.
Using MCP tool: search("event-driven architecture notifications", type: "memo")
Found your memo from March 27 (4 min 12s). You specified three event channels: user actions, system alerts, and digest batches. Separate tables per channel, async fan-out via a job queue, 90-day retention on user actions, 30-day on system alerts. I'll use this as the architecture spec for the notification service...
Search my dictations for anything about the database migration this week.
Using MCP tool: search("database migration", limit: 10)
Found 3 results this week: - Monday 3:20pm (VS Code): Outlined the zero-downtime migration approach with dual-write - Wednesday 10:05am (Zoom standup): Confirmed the migration script passed staging tests - Wednesday 4:30pm (VS Code): Noted the rollback procedure and flagged the index rebuild timing
Where it fits
Six moments in an
AI-native workflow.
Prompt composition
Speak the full context into Windsurf Cascade. Every constraint, every edge case, every integration detail. Voice removes the pressure to be concise — and concise prompts produce worse code.
Code review narration
Walk through a PR the way you would explain it in person. What you approve, what concerns you, what needs to change. Dictated into Windsurf and formatted as a review comment.
Architecture brainstorms
Talk through tradeoffs before committing to an approach. Dictate the reasoning into Windsurf Cascade. Get pushback on the parts that don't hold up.
Error context dumps
Describe the stack trace, the reproduction steps, the environment, what you already tried. Give Windsurf the full picture instead of a one-line question.
Commit messages
Explain what the change does and why — the way you would tell a teammate. Resonant structures it. No more single-word commits.
Inline documentation
The reason this function exists, why this approach was chosen, what the next person should know. Spoken in 5 seconds. Would have taken 30 to type.
Architecture
Your code stays
on your machine.
Cloud dictation routes your audio through external servers. Every prompt you dictate — the internal API structure, the migration plan, the architecture decisions from this morning's meeting — travels to someone else's infrastructure.
Resonant processes everything on your Mac. Audio never leaves your device. MCP runs over a local socket — Windsurf only sees the text it requests. No cloud relay. No telemetry.
The only thing that reaches Windsurf is the finished text — exactly as if you'd typed it.
Free. Local. Auto-configures in Windsurf.
Give Windsurf the context
it actually needs.
Voice input for faster prompts. MCP for persistent memory. No subscription, no cloud, no setup.
Requires macOS 14+ · Apple Silicon