Give what you build in Cursor live, source-grounded intelligence — real, cited, dated events and claims. Add the Synorb MCP server with a deeplink and token, then start from prompts that match the live REST shape.
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.
A cited dependency & AI-ecosystem watchdog that lives in your IDE and your CI - every breaking change comes with a real source link.
A deployed internal analyst dashboard where every economic claim is typed, evidence-graded, and one click from its real bls.gov / FRED / federalreserve.gov source.
A drop-in, source-cited federal-legislation data layer for your internal tool - bill tracker, policy-flow charts, and a per-bill view that links straight to Congress.gov, wired to live data in one prompt.
Use Synorb in Cursor to design with live examples. When your app is published, your frontend calls a backend route that keeps Synorb secrets off the page.
mcp.synorb.com/mcpapi.synorb.comKeep 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.
Go to synorb.com/connect. You'll get an MCP token for Cursor and an api-key + secret pair for your app backend. Keep each credential in the place it belongs.
This opens Cursor and pre-fills the server URL:
Then paste your MCP token as the Authorization: Bearer header in Cursor Settings → MCP. Prefer manual? Add to ~/.cursor/mcp.json:
Ask your agent to run this. synorb-profile is zero-quota — it never bills.
Your app should call Synorb from a backend (server-side function or server route) with the api-key + secret stored as server secrets — never in frontend code. See the runnable server-side example.
Synorb's Core MCP exposes eight tools. Only synorb-manifests bills quota — and only for returned, on-topic Manifests. Everything else is free.
synorb-profilesynorb-stream-searchsynorb-catalogsynorb-manifestsmode="count" is zero quota.synorb-detailssynorb-configure-beacon + synorb-save-beacon + synorb-beacons + synorb-archive-beaconYes. Use the MCP token only in Cursor's MCP 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.
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.
Manifests: structured units with a Brief (narrative summary), a Signal (atomic claims), nested source metadata, stable IDs, and citations with real source URLs.
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.
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.
The same Synorb MCP connects to major MCP-capable coding agents — same tools, same behavior.
Generate a starter key, connect Cursor, and pull your first cited Manifests in minutes.