Synorb MCP Server — Connect Any MCP Client to Live, Cited Data
Synorb for any MCP client.
Connect any MCP client to live, source-grounded intelligence — real, cited, dated events and claims. One Streamable-HTTP endpoint, three auth options, nine tools.
Connecting an AI agent? Point it at https://synorb.com/connect — it self-provisions a 24 Hour Agent Demo key with no email, 1,000 Manifests for 24 hours, and an expiry. Bind a human email at /api/connect/bind-email, then confirm the Cognito OTP at /api/connect/bind-email/verify to upgrade the same key to Starter (free forever, 1,000 Manifests/month).
What you'll set up
Connect in your MCP client. Serve from your backend.
Use Synorb in your MCP client 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
Synorb MCP server
Connects to mcp.synorb.com/mcp
Uses Synorb Key, saved in your MCP client config
Helps you Find streams, inspect cited examples, and guide the implementation
When your app runs
Synorb REST through your backend
Connects to api.synorb.com
Uses one server-side Synorb Key, stored as server secrets
Helps you Serve fresh, cited results without exposing credentials
Keep secrets server-side Never 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.
Add Synorb to any MCP client.
Account ladder: 24 Hour Agent Demo — 1,000 Manifests, expires 24 hours after mint → Starter — free forever, 1,000 Manifests/month, after binding an email → Paid — $10/month, 10,000 Manifests/month.
Parse only credentials.synorb_key from the Connect response and read the top-level expires_at; surface that expiry to the user. Bind the email with POST https://api.synorb.com/api/connect/bind-email using Authorization: Bearer <synorb_key>. The same key keeps working. If 24 Hour Agent Demo expires, show Synorb key expired — bind an email or mint a new demo key and document the recovery path in the generated README and environment template.
Get your credentials
Go to synorb.com/connect. You'll get one Synorb Key for your MCP client and app backend. Keep it only in protected connector or server-side secret storage.
Point your client at the endpoint
Streamable HTTP: https://mcp.synorb.com/mcp (legacy SSE: https://mcp.synorb.com/sse). Authenticate with the same Synorb Key:
HeaderAuthorization: Bearer YOUR_SYNORB_KEY
Standard client config:
{
"mcpServers": {
"synorb": {
"url": "https://mcp.synorb.com/mcp",
"headers": { "Authorization": "Bearer YOUR_SYNORB_KEY" }
}
}
}
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.
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 your MCP 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. Add the Synorb MCP server to your client once, run a zero-quota profile test, then use stream search and manifests when you need cited source-grounded context.
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?
24 Hour Agent 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.
Generate 24 Hour Agent Demo credentials, connect any MCP client, and pull your first cited Manifests in minutes.