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.

Sign Up
Start builds

Three things to build with Claude and Synorb.

Each is a complete, deployable product: click in, answer a few plain-English questions, and get a working app with live, cited Synorb data — sources one click away.

Statehouse Watch

Every morning, a one-page briefing of exactly which bills moved in the states you care about - every line clicks through to the official legislature page.

Open build →
Synorb Grounded-Research Skill

Drop /synorb-brief and /synorb-watch into Claude Code and any agent gets source-grounded, cited context on what changed across the AI/dev tooling world - with the real changelog URL on every fact.

Open build →
Cited Space & Earth-Science Memo Builder

Hand it a space or earth-science question and get back a defensible research memo plus a slide deck where every finding cites a NASA brief or a real preprint - citations appendix included.

Open build →
More Claude guides Research dashboard Statehouse briefing workflow
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
UsesSynorb Key, 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
Usesone server-side Synorb Key, 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 same Synorb Key is used for both MCP and REST; keep it server-side.

Connect

Add Synorb to Claude.

1

Get your credentials

Go to synorb.com/connect. You'll get one Synorb Key. Use that same key in Claude's MCP configuration and your app backend; keep it only in protected connector or server-side secret storage.

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_KEY"

Claude or Claude Desktop custom connector — open Settings → Connectors, choose Add custom connector, and paste the Synorb Key in the connector.

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_KEY"] } } }
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 (server-side function or server route) with the one server-side Synorb Key stored as server secrets — never in frontend code. See the runnable server-side example.

Tools

Nine tools. One bills quota.

Synorb's Core MCP exposes nine 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 Key safe in a deployed app?

Yes. Use the Synorb Key only in Claude's client config. For the shipped app, call Synorb from your backend with the REST one server-side Synorb Key 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?

DEMO access is available without a 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.

Mint a DEMO key, connect Claude, and pull your first cited Manifests in minutes.

Sign Up See plans →