Browse docsDevelopers
Connect Rift to your agent
Add Rift as a connector, approve it by email, and revoke the connection when you no longer want it.
Rift gives agents the ability to run their work in cloud VMs. The first step in getting set up with Rift is connecting your agent of choice to Rift's MCP server.
The connector
Give your agent this URL, wherever it adds a remote MCP server:
https://fixedlabs.dev/mcp- Claude app (phone or web): Settings → Connectors → Add custom connector, paste the URL.
- Claude Code:
claude mcp add --transport http rift https://fixedlabs.dev/mcpThe client registers itself with Rift and opens a page in your browser asking for your email. A link is emailed. Opening it — on any device — creates your account if you have none and lets the agent act as you. For a new account, the link's page is a welcome page: it asks your name only when Rift does not have it, and Continue goes on. The page you started from continues on its own, and the link's page has a continue here if that page is gone.
An unopened link allows nothing. If the link lapses, connect again and a fresh one is sent. Rift is invite-only for now, and the page answers every address the same way: if no link arrives, check the address, ask whoever should have invited you, or join the waitlist at https://fixedlabs.dev/waitlist.
What the connection can do
Your agent acts as you. It can do whatever your role allows in each of your organizations: a member can use its repositories, and an admin can also invite people, connect GitHub and watch refs. Agents don't get a narrower set of permissions.
What the agent gets is spelled out in MCP tools. The short form: it opens tasks, claims VMs into them, runs commands and reads and writes files on those VMs, and does your account's setup for you. It does not see your secrets, and it can't set them.
Revoke a connection
To revoke an agent connection, sign in to Rift at https://fixedlabs.dev, open Settings, and click Revoke on the token's row under MCP tokens.
Revoking is immediate and final for that token: the agent's next request is refused, and connecting again mints a new one. A token that isn't revoked lives until it is — there is no refresh dance and no expiry to babysit.