What should Cursor inspect before coding?

Ask Cursor to use Synorb MCP to search Streams and pull a small sample of Manifests so it can build against the real response shape.

What should be stored in the dashboard?

Store normalized rows, filters, panel definitions, refresh state, and source URLs. Keep Synorb credentials server-side.

Build / Cursor research dashboard

How to build a research dashboard with Cursor.

Use Cursor with Synorb MCP to learn the available Streams and Manifest shape. Then ship a dashboard where each panel is powered by server-side Synorb REST and every card links back to its source.

Get Keys Cursor setup →

Panels

A dashboard is a set of repeatable questions.

Company panel

Recent source-backed updates for a company or watchlist.

Topic panel

A stream of Manifests for a topic, sector, policy area, or market theme.

Source panel

Items from a specific channel, source type, or media format.

Build prompt

Paste this into Cursor.

Build a research dashboard powered by Synorb. First use Synorb MCP in Cursor to search Streams and sample Manifests for the dashboard panels. Then implement a backend REST route with SYNORB_API_KEY and SYNORB_SECRET as server-side environment variables. Return normalized rows by panel: id, headline, summary, publishedDate, sourceUrl, sourceName, streamNames, tags, significance. Build panel filters, source links, loading/empty/error states, refresh timestamp, and Load more. Do not expose credentials in client code.

Architecture

Cursor learns with MCP; the app runs on REST.

Development

MCP sampling

Use forstream discovery, sample rows, schema-aware implementation

Production

Server REST

Use fordashboard data, caching, saved panel filters

Start

Build a dashboard with citations.

Get Keys Claude version →