Connect Core MCP
Use Streamable HTTP. One Synorb Key works for MCP and REST. Discovery is keyless — you can call the discovery and reference tools (synorb-catalog, synorb-stream-search, synorb-details, synorb-configure-beacon, and the other read-only catalog/tag tools) over /mcp with no key. Add the Synorb Key to unlock Manifest pulls and account tools, then initialize once for the user or workspace and reuse the same session across tool calls.
{
"mcpServers": {
"synorb": {
"url": "https://mcp.synorb.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_SYNORB_KEY"
}
}
}
}
Typical Agent Flow
synorb-profile.stream_ids.Plan and Resume Safely
For MCP, resolve a canonical tag and select explicit stream_ids before calling synorb-manifests. Do not treat required_surfaces as execution scope, and never leave intended scope empty: an empty scope can become a global pull. Count and orient are zero-quota preflight tools; a final answer needs a normal content pull and its returned citations.
For a deterministic REST workflow, use POST /manifests/plan, then replay that exact request to POST /manifests/exec with only plan_token added. The token fingerprints all fields, so any addition or change invalidates it; re-plan for free. See the agent guide for exact calls and the full Beacon lifecycle.
Core or Advanced?
Start with Core MCP for normal assistant access. Use Advanced MCP only when the workflow has been configured for expanded tools such as digest management, sync ontology, labels, prompt templates, or full record access.
Building a live product
Use MCP while the coding agent explores Synorb. For the product it builds, use REST in a server-side route, keep the Synorb Key in the platform secret store, and show the Manifest citation URL with each factual update. The agent guide is the runtime reference.