Your first connection.
Download the connector, link your account, and reach your local agents from your own MCP client.
Get Peerband Connector.
Download the installer for your machine. It installs Peerband as a Herdr plugin. Activation needs the personal pairing command from your account in the next step.
Give your machine a home.
Open the dashboard and sign in with Google. In Connect a machine, name your machine and generate an enrollment grant. Copy the installer command for your operating system and run it in your terminal.
The command downloads the connector, links it to your account, and registers it in Herdr. The grant is short-lived and works once. Your machine will appear online when the helper connects.
Open your workspaceBring your own client.
In your MCP client, add the endpoint shown in the dashboard. An OAuth-capable client discovers Peerband sign-in, opens a browser, and asks you to approve access. Sign in to the Peerband account that owns your machine. The client stores its authorization; you do not need to copy a bearer token. OAuth availability depends on the backend configuration and is shown in the dashboard.
Approve agents:read to list your agents and read their status, output, and delivery receipts. Grant agents:messageonly if you want the client to send instructions. Messaging also requires writes to be enabled locally on your connector. Read access covers machines on your account, including machines you enroll later.
Copy your machine’s installation ID from the dashboard. Start with list_agents using that ID, then use get_agent_status or get_agent_output to check in on one agent.
list_agents(installation_id="your-machine-id")To send instructions, approve message access and enable writes on your connector, then use send_agent_message with an explicit agent ID. Delivery receipts can be checked with get_request_status. Revoking a machine stops access to that machine.
In the dashboard, disconnect a connected app to revoke that client’s access. Signing out of Peerband does not revoke its grant, and disconnecting a client does not revoke your machine.
Advanced / manual token setup
For clients that cannot complete OAuth, generate a personal MCP token in the dashboard and configure it as an Authorization: Bearer <token> header. Treat it like a password. Use the dashboard’s token revoke action if you need to invalidate these credentials.
Reconnect, then check in.
Your laptop needs to be awake with Herdr running. The connector retries after network interruptions; the dashboard shows whether it’s connected. The Herdr plugin’s start, status, and stop actions let you manage the helper locally.