Give your Lovable app live, source-grounded intelligence — real, cited, dated events and claims, not stale training data or scraped guesses. Use Synorb MCP in the Lovable chat to design with real data, then serve fresh results from a backend your users can safely call. No MCP knowledge required.
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 living map of what your state legislature is actually doing - every bill cited to the official source, refreshed daily through the 2026 midterms.
A beautiful public site that explains what NASA and space science actually did this month - every fact cited, key moments you can listen to, refreshed automatically.
An embeddable Q&A box for health and medicine that answers from tracked FDA, NIH, CDC, and clinical-trial sources, with a real citation on every sentence.
A browsable weekly feed of what podcasts said - each episode shows the readable Brief and the structured Signals (claims), with filters by show, topic, and person/company, and a link to every episode.
Use Synorb in the Lovable chat to build with live examples. When your app is published, your frontend calls a server-side function that keeps Synorb secrets off the page.
mcp.synorb.com/mcpapi.synorb.comKeep secrets server-sideNever put a Synorb credential in a VITE_ variable or client-side code. The browser calls your server-side function; that function calls Synorb.
Go to synorb.com/connect. You'll get an MCP token for the Lovable chat and an api-key + secret pair for your app backend. Keep each credential in the place it belongs.
In the Lovable editor: Connectors → Chat connectors → New MCP server. This lets Lovable inspect Synorb data while it helps you build.
https://mcp.synorb.com/mcpIf your Lovable version requires the older transport, use https://mcp.synorb.com/sse instead. Try /mcp first.
In the Lovable chat, paste this. synorb-profile is zero-quota — it never bills.
In Lovable's Cloud → Secrets (or your framework's server-side secret store), add two secrets — do not use the VITE_ prefix:
Your frontend calls a server-side function; the server-side function calls Synorb with the secret. The REST API wraps responses as { data, usage } — cite each row's source_url and surface usage for 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-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 Lovable's chat connector. For the shipped app, call Synorb from a server-side function with the REST api-key + secret stored as server-side secrets. Never put any Synorb credential in frontend code or a VITE_ variable.
No. You paste the Synorb MCP server URL and your token into Lovable's chat connector UI, then copy a build prompt into the chat. The agent does the rest.
Manifests: structured units with a Brief (narrative summary), a Signal (atomic claims), nested source metadata, stable IDs, and citations with real source URLs. Render them as cards, feed them to RAG, or store them.
Free starter credentials are available with 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 on the first of each month.
Use Synorb first for structured, source-grounded intelligence. Fall back to web search only for genuine gaps: ultra-fresh items from the last hour or two, 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, paste it into Lovable, and pull your first cited Manifests in minutes.