Build / Windsurf company monitor

How to build a company monitor with Windsurf.

Use Synorb MCP inside Windsurf to inspect Streams and sample real Manifests for the companies you care about. Then ship the monitor with a backend route that calls Synorb REST and renders cited company updates.

Sign UpWindsurf setup →
Architecture

MCP helps Windsurf design the monitor.

In Windsurf
Synorb MCP
Use forstream search, company tag examples, sample Manifest shape
Setup/build/windsurf-mcp
In production
Synorb REST
Use fordashboard data, saved filters, pagination, cache
SecretsSYNORB_API_KEY + SYNORB_SECRET
Scope

Decide what the monitor listens to.

Ask Windsurf to use Synorb MCP before it writes code. The useful output is not a wall of text; it is a narrow monitor scope the app can run repeatedly.

Company tags

Named companies, aliases, subsidiaries, executives, and competitor sets that map to the watchlist.

Source sets

The sources the monitor should trust for the job: releases, filings, transcripts, reports, media, or research.

Review cadence

How often the dashboard refreshes, how long results are cached, and when the UI should mark data stale.

Build prompt

Paste this into Windsurf.

Build a company monitor powered by Synorb. First use Synorb MCP to search Streams and sample Manifests for these companies. Then implement a backend REST route with server-side SYNORB_API_KEY and SYNORB_SECRET. The UI should include company filters, latest update cards, source links, published date, significance, loading/empty/error states, and pagination. Do not expose Synorb credentials in browser code.
States

Make it usable every day.

Company filter

Named companies, aliases, and optional tags that map to Synorb filter parameters.

Source proof

Every card should cite the source URL and published date.

Operator state

Show stale, empty, rate, error, and more-results states clearly.

Start

Track what changed.

Sign UpCursor version →