Build / Claude

Synorb for Claude.

Give Claude Code, Claude, and Claude Desktop live, source-grounded intelligence — real, cited, dated events and claims. Add the Synorb MCP server or custom connector, then start from prompts that match the live REST shape.

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

Connect in Claude. Serve from your backend.

Use Synorb in Claude 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 Claude
Synorb MCP server
Connects tomcp.synorb.com/mcp
UsesMCP token, saved in your Claude 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 Claude.

1

Get your credentials

Go to synorb.com/keys. You'll get an MCP token, a Core MCP config, a tokenized connector URL for Claude custom connectors, and an api-key + secret pair for your app backend. Keep each credential in the place it belongs.

2

Add Synorb to Claude

Claude Code — one command:

claude mcp add --transport http synorb https://mcp.synorb.com/mcp \ --header "Authorization: Bearer YOUR_SYNORB_MCP_TOKEN"

Claude or Claude Desktop custom connector — open Settings → Connectors, choose Add custom connector, and paste the tokenized connector URL from your credentials email.

Claude Desktop local config — Settings → Developer → Edit Config, then add:

{ "mcpServers": { "synorb": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.synorb.com/mcp", "--header", "Authorization: Bearer YOUR_SYNORB_MCP_TOKEN"] } } }
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

Paste a prompt. Ship a feature.

Copy a build prompt and paste it into Claude. Each one names Synorb, handles secrets safely, and renders cited results.

Industry news feed

A live news page for your topic — cited Manifests as cards, refreshed from Synorb.

Subscription newsletter

Assemble a recurring newsletter from real Manifests, one cited section per topic.

Company monitor

Track companies and surface what moved — with a re-runnable saved query.

Research dashboard

A grid of always-current, always-cited cards across the topics you track.

More build recipes →

Task guides

Building a specific Claude project?

Use the setup above first, then start from a guide that keeps Claude's MCP exploration separate from your backend REST delivery path.

Research dashboard

Build panel-based research workflows with cited results, source links, and server-side credentials.

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 Claude's client 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 internals?

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 Claude, and pull your first cited Manifests in minutes.

Get Keys See plans →