Build

Build with the agents you already use.

Add live, source-grounded intelligence — real, cited, provenance-linked events and claims — to the app you're building with a coding agent. One canonical Synorb MCP, with setup paths for major MCP-capable tools.

One MCP. Pick your setup.

Use the setup page that matches where you are building. The Synorb tools and behavior stay the same.

or connect any MCP client →

Use MCP to build. Use REST to ship.

Your coding agent can inspect Synorb data while it helps you build. Your shipped app should call Synorb from a backend route, with credentials stored as server-side secrets.

While you build
Synorb MCP for your coding agent
Connects tomcp.synorb.com/mcp
UsesMCP token in the agent's client config
Helps youFind streams, preview cited Manifests, and scaffold against real data
When your app runs
Synorb REST through your backend
Connects toapi.synorb.com
Usesapi-key + secret stored as server-side secrets
Helps youServe cited, source-grounded content without exposing credentials

Keep secrets server-sideNever put any Synorb credential in client-side or frontend code. A published frontend can't keep a secret — always go through a backend. The two credentials are not interchangeable.

Free credentials. No card.

Generate starter credentials, connect your agent, and pull your first cited Manifests in minutes.