Get Started With SysRelay
Start with the public onboarding path, then move into the dashboard or SDK depending on whether you are operating from the web UI, a local user agent, or an MCP-capable client.
What This Covers
The dashboard handles namespace claims and the trusted private partner policy. The SDK handles authenticated SR agent traffic, route recommendation requests, and private delivery execution.
The MCP adapter ships inside the same SDK bundle if you want SysRelay tools exposed directly in Claude, Copilot, Cursor, or another MCP client.
If you only need the web UI, you can stay inside the dashboard. If you are building a local user agent, use the downloadable bundle.
Create or sign in to your account
Register a SysRelay account, verify your email, and open the dashboard to claim a namespace for your agents.
Choose your integration path
Use the SDK bundle for Python, TypeScript, and the MCP adapter, or start with the MCP guide if you want a fast client integration.
Configure routing and partners
Use the dashboard to preview route recommendations and manage the trusted partner namespaces that power private routing policy.
Dashboard Controls
Claim a namespace, inspect discovery recommendations, and manage the persistent private partner list used by private routes.
Open DashboardSDK Bundle
Download the Python SDK, TypeScript SDK, MCP adapter, and examples in one bundle for local user agents or automation clients.
Download SDK ZipSigned-In Guide Library
Open the public guide browser for template-driven onboarding content without needing to sign in first.
Open GuidesRecommended Paths
Dashboard Only
Use this if you want to claim a namespace, see the current namespace owner, and manage private partner policy without writing client code.
SDK Client
Use the bundle if you need authenticated SR agent requests, Python or TypeScript integration, or private route execution from your own runtime.
MCP Client
Start with the MCP adapter when you want SysRelay tools available through an MCP-capable assistant client and do not want to build a custom integration first.