Update, October 2026: Smithery’s hosted connect and proxy will shut down on October 31, 2026, so do not rely on Smithery to connect. Connect directly to Synorb’s MCP server at https://mcp.synorb.com/mcp (Streamable HTTP). Setup is at synorb.com/connect/start, and the direct MCP setup guide is at synorb.com/docs/mcp. The Smithery page remains only as a registry listing.
We’re excited to share that Synorb Content MCP is now listed on the Smithery registry.
Smithery is a discovery and connection hub for Model Context Protocol servers. Instead of asking every developer to find a raw MCP URL, read a hand-written config, and guess what a server exposes, Smithery gives users a browsable server page with capabilities, setup paths, and installation flows for supported clients.
For Synorb users, that means there is now a clean marketplace page for connecting agents to the Temporal Context Graph: source-grounded Streams, cited Manifests, coverage discovery, and reusable Beacons through the same MCP content surface.
What you can do now
Open the Synorb listing on Smithery to inspect the MCP content tool surface, then connect directly at https://mcp.synorb.com/mcp. Agents and builders can see the discovery, Stream, Manifest, and Beacon tools available through Synorb, then connect with a Synorb Key when they are ready to retrieve data-bearing results.
Once connected, users can ask an agent to search available Streams, inspect source coverage, pull cited Manifests for a date window, and save recurring retrieval scopes as Beacons. The useful pattern is simple: discover what Synorb covers for free, then run focused Manifest pulls when the agent needs fresh, source-grounded context.
Synorb’s public discovery methods are available for marketplace scanning and setup, while data-bearing methods remain gated by authentication, plan, usage, access, and date-window rules. That keeps the listing useful for MCP hosts without turning discovery into an unauthenticated data path.
Where it fits
The Smithery listing is a good way to evaluate the server’s shape before wiring it into a workflow. To connect, use Synorb’s direct Streamable HTTP endpoint, https://mcp.synorb.com/mcp, or REST. Both let you manage credentials and orchestration yourself.
If you already have a Synorb Key, send it as Authorization: Bearer <key> to https://mcp.synorb.com/mcp. If you are new to Synorb, start at synorb.com/connect/start, which explains how an agent gets a free demo key, then point your MCP client at the direct endpoint.