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 the Synorb Key, then start from prompts that match the live REST shape.
Choose a real product, watch the short build video, and copy the complete one-shot prompt. Cursor builds the product layer; Synorb supplies the current, structured, source-grounded content.
0:59
Build an AI assignment desk for regional newsroom product leaders: market-specific story drafts, claim packs, source receipts, and editor-ready leads on first live load.
Built for: AI product lead, newsroom transformation lead, or product engineer at a regional publisher or media company responsible for rolling out AI tools to reporters across multiple local markets.
0:59
Build a state policy dashboard for data-center bills, executive actions, incentives, zoning fights, and grid pressure.
Built for: Policy product lead or developer building an internal monitor for state data-center legislation and executive action.
0:59
Build a local 2026 midterm radar that turns state, congressional, and economic signals into cited market-level leads.
Built for: Developer or AI product lead building a source-grounded local election issue board.
0:59
Build a BLS-backed regional economy dashboard with metro charts, local explainers, and cited claim exports.
Built for: Product engineer building a regional economy dashboard for analysts, operators, or business users.
0:59
Build a sports market intelligence tool that connects official team, venue, campus, labor, and local business signals.
Built for: Developer or product lead building a sports business, venue operations, campus athletics, civic technology, or regional strategy product.
0:59
Build a repo-aware dependency, SDK, AI-model, and API-change watchdog that opens cited upgrade briefs.
Built for: Engineering lead or developer using Cursor inside a production repository.
0:59
Build a cited economic analyst dashboard where every macro claim is typed, evidence-graded, and source-linked.
Built for: Developer or analyst building a source-grounded macro dashboard.
0:59
Build a company, competitor, vendor, or sector monitor with cited changes, saved watchlists, and workflow digests.
Built for: Developer or product lead building a private market-intelligence surface for a known watchlist.
0:59
Build a cited policy-intelligence app for congressional hearings, bills, agency releases, enforcement, and regulatory guidance.
Built for: Developer building a federal policy monitor for an enterprise, legal, compliance, product, or public-affairs workflow.
0:59
Build a reusable backend package that exposes normalized Synorb Manifests, Briefs, Signals, claims, filters, and pagination to an existing app.
Built for: Developer adding Synorb to an existing application or internal platform.
No builds match those filters. Try a broader search or clear one filter.
One prompt. A few product choices. A working product powered by fresh Synorb streams.
Open the one-shot promptUse 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 same Synorb Key is used for both MCP and REST; keep it server-side.
Account ladder: 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 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.
Go to synorb.com/connect. You'll get one Synorb Key for both MCP and your app backend. Store the same value only in the platform's protected connector or server-side secret field.
This opens Cursor and pre-fills the server URL:
Then paste your Synorb Key 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 Synorb Key stored as server secrets — never in frontend code. See the runnable server-side example.
Synorb's Core MCP exposes nine 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 Synorb Key only in Cursor's MCP config. For the shipped app, call Synorb from your backend with the REST Synorb Key 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.
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.
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.
Mint a DEMO key, connect Cursor, and pull your first cited Manifests in minutes.