Build / Claude research dashboard

How to build a research dashboard with Claude.

Use Claude with Synorb MCP to explore sources, choose dashboard panels, and inspect real cited Manifests before writing code. Then ship the dashboard with backend REST calls that fetch Briefs or Signals, normalize them into panels, and keep Synorb credentials out of the browser.

Get Keys Claude setup guide →
Prerequisites

A useful dashboard starts with bounded panels.

1

Claude connected to Synorb MCP

Follow /build/claude-mcp for Claude Code, Claude, or Claude Desktop setup. MCP lets Claude inspect the data shape while it builds.

2

Panel definitions

Define each panel as a topic, company, domain, source group, or Beacon. Panels work best when each has a clear filter and date window.

3

Backend environment

Use server-side secrets for SYNORB_API_KEY and SYNORB_SECRET. The frontend calls your backend and never sees Synorb credentials.

Architecture

Claude explores with MCP. The app serves with REST.

Claude can use MCP to decide which Streams and filters matter. A shipped dashboard should use REST from your backend because dashboards need predictable refreshes, caching, and user-safe responses.

During development
Claude + Synorb MCP
Use forPanel discovery, source coverage checks, sample Manifests
Toolssynorb-stream-search, synorb-manifests, Beacon tools when needed
Setup/build/claude-mcp
In production
Backend + Synorb REST
Use forPanel data fetches, pagination, refresh cadence, quota state
CredentialREST api-key + secret in server-side env
Reference/docs

Credential safetyDo not paste real credentials into prompts, source files, browser code, or screenshots. Let the runtime load secrets from the server environment.

Response shape

Panel data should be normalized and cited.

Each panel can call the same backend endpoint with a different saved filter. Keep source URLs visible so researchers can verify every item.

type ResearchPanel = { title: string; items: Array<{ headline: string; summary: string; publishedDate: string; sourceUrl: string; significance?: string; }>; pagination?: { hasMore: boolean; nextPage?: number }; usage?: { remaining?: number }; };
Build prompt

Paste this into Claude.

Claude research dashboard prompt

Guides Claude through panel discovery, REST backend implementation, citations, and credential safety.

FAQ

Questions builders ask.

Should Claude use MCP or REST for the dashboard?

Use MCP while Claude is designing and coding. Use REST from your backend for the shipped dashboard so credentials stay server-side and the app has a stable contract.

What belongs in a research dashboard panel?

A panel should show cited items for a clear topic, company, source group, or Beacon. Include headline, summary, date, source URL, significance, and empty-state guidance.

Can the dashboard expose Synorb credentials?

No. Store the REST api-key and secret only as server-side secrets. The browser should receive prepared dashboard data.

Where is the Claude setup guide?

The canonical setup page is /build/claude-mcp.

One MCP, many on-ramps

Using a different agent?

The same Synorb MCP connects to major MCP-capable coding agents. The deployed dashboard should still use REST from a backend.

Start building

Free credentials. No card.

Generate credentials, connect Claude, and build a cited research dashboard.

Get Keys See plans →