> ## Documentation Index
> Fetch the complete documentation index at: https://rapidreview.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# OpenHands

> Connect OpenHands to Merv with a project key — the one client where a static key is the documented default.

## Install and sign in

OpenHands has no Merv plugin. You register the MCP server yourself, and because its browser flow is unsuitable headless, a **project key** is the recommended credential. Create one in the project under **Settings → MCP keys** (**All my projects** unless you want confinement).

<Tabs>
  <Tab title="Local GUI / config.toml">
    ```toml config.toml theme={"theme":{"light":"github-light","dark":"dark-plus"}}
    [mcp]
    shttp_servers = [
      { url = "https://experiments.rapidreview.io/mcp", api_key = "paste the key" }
    ]
    ```

    The value is sent exactly as `Authorization: Bearer <value>`. Paste the literal key — env-var interpolation in this value is unconfirmed.
  </Tab>

  <Tab title="CLI">
    ```bash theme={"theme":{"light":"github-light","dark":"dark-plus"}}
    openhands mcp add merv --transport http \
      --header "Authorization: Bearer <project-key>" \
      https://experiments.rapidreview.io/mcp
    ```

    Stored in `~/.openhands/mcp.json`.
  </Tab>

  <Tab title="Cloud">
    **Settings → MCP** is the only path; it can't be shipped in a repository.
  </Tab>
</Tabs>

OAuth is possible (`auth = "oauth"` / `--auth oauth`) if you have a browser at hand.

<Check>
  Ask the agent to call `project(action="list")`, then `workflow.status_and_next(project_id)`. Follow along in the web UI at [rapidreview.io/merv](https://rapidreview.io/merv).
</Check>

## Skills and reviewers

The repo-root `AGENTS.md` carries the workflow instructions. Optionally copy the canonical skill directories to `.agents/skills/<name>/SKILL.md`; keyword activation would need `triggers` frontmatter, which Merv's skills don't carry, so invoke them explicitly. No reviewer auto-discovery: start a second session or agent with the matching review skill and the handoff prompt, or follow the review inline. See [Reviewer handoff](/docs/merv/clients/reviewer-handoff).