Build / Windsurf

Synorb for Windsurf.

Give Windsurf and Cascade live, source-grounded intelligence — real, cited, dated events and claims. Add the Synorb MCP server, then start from prompts that match the live REST shape.

Get Keys Jump to starter builds ↓
What you'll set up

Connect in Windsurf. Serve from your backend.

Use Synorb in Windsurf to design with live examples. When your app is published, your frontend calls a backend route that keeps Synorb secrets off the page.

While you build in Windsurf
Synorb MCP server
Connects tomcp.synorb.com/mcp
UsesMCP token, saved in your Windsurf config
Helps youFind streams, inspect cited examples, and guide the implementation
When your app runs
Synorb REST through your backend
Connects toapi.synorb.com
Usesapi-key + secret, stored as server secrets
Helps youServe fresh, cited results without exposing credentials

Keep secrets server-sideNever put a Synorb credential in client-side code. The browser calls your backend; your backend calls Synorb. The two credentials are not interchangeable.

Connect

Add Synorb to Windsurf.

1

Get your credentials

Go to synorb.com/keys. You'll get an MCP token for Windsurf and an api-key + secret pair for your app backend. Keep each credential in the place it belongs.

2

Add the Synorb MCP server

In Windsurf: Cascade → MCP servers → Add, or edit ~/.codeium/windsurf/mcp_config.json:

{ "mcpServers": { "synorb": { "serverUrl": "https://mcp.synorb.com/mcp", "headers": { "Authorization": "Bearer YOUR_SYNORB_MCP_TOKEN" } } } }

Then refresh MCP servers in Cascade.

3

Test with a free call

Ask your agent to run this. synorb-profile is zero-quota — it never bills.

Call synorb-profile and tell me my account name, current quota, and available date window.
4

Serve it from a backend

Your app should call Synorb from a backend (Supabase Edge Function or server route) with the api-key + secret stored as server secrets — never in frontend code. See the runnable Edge Function example.

Starter builds

What can Windsurf build with Synorb?

Copy a build prompt and paste it into Windsurf. These examples are shaped around repo-level product work: multi-file UI, backend routes, refactors, and source-grounded monitors.

Company and policy monitor

A repo-level monitor for companies, policy terms, official sources, or market themes with cited feed rows.

2026 statehouse issue tracker

A state-by-state issue tracker for legislative, governor, and statehouse updates during the midterm cycle.

Alert workflow

Route fresh cited items into an operator queue, email draft, Slack-like alert, or admin review surface.

Content feed admin console

A team console for managing feed scopes, source coverage, review status, and app-facing API output.

More build recipes →

Task guides

Building a specific Windsurf project?

Use the setup above first, then start from a guide that turns Windsurf's MCP exploration into server-side production data.

Company monitor

Track companies with tag filters, optional Beacons, and source-linked monitor cards.

Open guide →
Agent research monitor

Build a reusable monitor that starts from source-grounded Streams and searches gaps.

Open guide →
Real-time web data

Understand the feed layer behind production apps and agent workflows.

Open guide →
Tools

Eight tools. One bills quota.

Synorb's Core MCP exposes eight tools. Only synorb-manifests bills quota — and only for returned, on-topic Manifests. Everything else is free.

synorb-profile
Account, quota, live date window. Zero quota.
synorb-stream-search
"What streams/sources do you have?" Zero quota.
synorb-catalog
Ranked stream candidates when search is thin. Zero quota.
synorb-manifests
The cited content. The only tool that bills; mode="count" is zero quota.
synorb-details
Richer metadata for specific streams. Zero quota.
synorb-configure-beacon + synorb-save-beacon + synorb-beacons + synorb-archive-beacon
Design, save, list, and archive re-runnable tracked queries. Zero quota.
FAQ

Questions builders ask.

Is my Synorb token safe in a deployed app?

Yes. Use the MCP token only in Windsurf's MCP config. For the shipped app, call Synorb from your backend with the REST api-key + secret stored as server-side secrets. Never put any Synorb credential in frontend code.

Do I need to know MCP details?

No. You add the Synorb MCP server to your agent once (steps above), then copy a build prompt into the chat. The agent handles the tool calls.

What does Synorb return?

Manifests: structured units with a Brief (narrative summary), a Signal (atomic claims), nested source metadata, stable IDs, and citations with real source URLs.

How much does it cost?

Free starter credentials, no card. Only synorb-manifests consumes quota, and only for returned on-topic Manifests; synorb-profile, synorb-stream-search, synorb-catalog, synorb-details, and the Beacon tools are zero quota. Quota resets monthly.

When should I still use web search?

Use Synorb first for structured, source-grounded intelligence. Fall back to web search only for genuine gaps: ultra-fresh items, very narrow local news, or topics outside Synorb's tracked scope.

One MCP, many on-ramps

Using a different agent?

The same Synorb MCP connects to major MCP-capable coding agents — same tools, same behavior.

Start building

Free credentials. No card.

Generate a starter key, connect Windsurf, and pull your first cited Manifests in minutes.

Get Keys See plans →