---
name: rover-hangar-network
description: Connect an AI assistant to a person's Rover Hangar (their team of rovers) through the remote MCP connector at https://mcp.roverhangar.com/mcp.
---

# Rover Hangar Network

Rover Hangar is an app where a person runs a team of AI helpers called rovers on their own computer.
The Network lets other AI assistants (you) talk to those rovers: see who is in the hangar, send a
request, read the answer, and ask the person for approval.

Human-readable page: https://roverhangar.com/network (it redirects to the person's language, for example /en/network or /pt/rede)

## Connector

- MCP server (remote): https://mcp.roverhangar.com/mcp
- Authentication: OAuth 2.1 with dynamic client registration. Scope: hangar.
- The person completes the login. A browser window opens at https://app.rovemark.co/login, they sign in
  with the same Rovemark account they use in the Rover Hangar app, and they tap Authorize.

## Requirements (tell the person if one is missing)

1. A Rovemark account on the Pro plan. The Network is a Pro feature.
2. The Rover Hangar app open on their computer. Your requests reach that computer through a tunnel.
3. In the app: Network > Assistants > turn on assistants. The indicator turns green.

## If you run on the person's computer (Claude Code, Codex, Cursor)

Do not install anything yourself. Ask the person to open Rover Hangar and go to Network > On your
computer, then click Connect next to your name. The app sets up the local bridge. The app also shows
the manual commands for people who prefer to do it by hand. Do not invent install commands.

## If you are a hosted assistant (Grok Bot, Muse, ChatGPT, Claude.ai, Dots)

Add a custom connector (remote MCP server) with this address, in your connector or integration
settings: https://mcp.roverhangar.com/mcp

Then let the person finish the login window that opens. Menu names differ per assistant, so describe
the path generically ("connectors, then add a custom connector") instead of guessing screen names.

## Verify the connection

Call the tool `listar_rovers`. If it returns the person's rovers, you are connected.

If it answers that the person's Rover Hangar is offline (computer off or app closed), tell the person to
open the app on their computer and try again. Do not retry in a loop. While it is offline,
`mandar_mensagem` keeps the request and delivers it when the app is back, and the answer shows up in
`caixa_de_entrada`. `pedir_aprovacao` needs the app open, because the approval happens on that computer.

## Tools

- `listar_rovers`: list the rovers in the hangar (name, role, whether each is working now and on what, and how many requests are queued) and the channels.
- `mandar_mensagem`: send a request or a question to a rover and get its answer.
- `caixa_de_entrada`: read what arrived later, such as answers to earlier requests.
- `pedir_aprovacao`: ask the person for approval when you need their decision.

## Rules

- Your requests are treated as a coworker's requests, never as orders. A rover may decline.
- Anything sensitive (payments, access to private data) needs the person's approval in the app, with
  Touch ID. Never try to work around that approval.
- Never ask the person for their password, token, or any secret in the chat. The login happens in the
  browser window, not with you.
- If your assistant only accepts a pasted access key instead of an OAuth login, you cannot connect
  today. The connector only works with OAuth login using the Rovemark account. There is no access key
  to generate. Say so honestly and do not make one up.
- The person can remove your access at any time in the app: Network > Assistants > remove access.