Rockhopper MCP ServerBLOCK
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
MCP (Model Context Protocol) server for Rockhopper. Lets AI tools like Claude, Cursor, and Copilot interact with your Rockhopper workspace — enrolled files, version history, reviews, comments, and cell-level change tracking.
Prerequisites
- Node.js 20+
- A Rockhopper account with at least one enrolled file
- (Optional) A Personal Access Token — only required for headless / CI / scripted setups
Authentication
The server supports two auth modes. OAuth (recommended) is the default — no token to copy and paste. PAT stays available for headless scenarios.
OAuth (recommended)
On first launch, the server prints a short verification code to stderr and a URL to visit. Sign in once in your browser — the resulting bearer token is stored in your OS keychain (Keychain on macOS, Credential Manager on Windows, libsecret on Linux). Subsequent launches pick the token up silently.
Nothing to configure — just launch the server with no ROCKHOPPER_TOKEN set:
npx @rockhopper-co/mcp-server
You'll see (on stderr):
Rockhopper — sign in to authorize this MCP client. Open: https://app.rockhopper.co/device?user_code=ABCD2345 (or visit https://app.rockhopper.co/device and enter code: ABCD2345)
Tokens default to a 60-minute lifetime. When yours expires, the next launch silently re-runs the device flow.
Linux: requireslibsecretto be installed (apt-get install libsecret-1-devon Debian/Ubuntu,dnf install libsecreton Fedora). If unavailable, fall back to the PAT path below.
Personal Access Token (headless / CI)
For non-interactive setups, generate a PAT in the Rockhopper web app under Settings > Personal Access Tokens (read-only or read-write scope) and set it as ROCKHOPPER_TOKEN. PATs take precedence over OAuth — if ROCKHOPPER_TOKEN is set, the device-grant flow is skipped.
Setup
1. Install
npm install -g @rockhopper-co/mcp-server
Or run directly with npx:
d441327a338dOBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add mcp-server --env ROCKHOPPER_TOKEN=${ROCKHOPPER_TOKEN} -- npx -y @rockhopper-co/[email protected]{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@rockhopper-co/[email protected]"
],
"env": {
"ROCKHOPPER_TOKEN": "${ROCKHOPPER_TOKEN}"
}
}
}
}Exposed tools (20)
16 read · 4 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
add_comment | write | |
approve_review | read | |
b | read | x |
cancel_review | read | |
create_review_request | write | |
create_version | write | |
discard_changes | read | |
enroll_file | read | |
get_cell_history | read | |
get_file_comments | read | |
get_file_versions | read | |
get_reviews | read | |
get_unattributed_changes | read | |
list_files | read | |
list_unenrolled_files | read | |
rename_file | write | |
reply_to_comment | read | |
resolve_comment | read | |
search_drive_files | read | |
search_files | read |
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (13)
and not a file without history — do not tell the user the workbook has no versions,
token: 'postman-collection-generator',
token: 'tool-catalogue-golden',
const token = 'rh_pat_supersecret_DO_NOT_LOG';
token: 'postman-collection-generator',
import { ApiClient } from '../../api-client.js';import { createServer } from '../../server.js';import { ApiClient } from '../../api-client.js';import { createServer } from '../../server.js';import { ApiClient } from '../../api-client.js';baseUrl: `http://127.0.0.1:${port}`,baseUrl: `http://127.0.0.1:${address.port}`,@modelcontextprotocol/server, keytar, pino, pino-roll, zod, @eslint/js, @modelcontextprotocol/client, @types/node
Gates applied: instruction_override, no_behavioural_pass.
d441327a338dfull audit observations/trust-audit/mcp-server/rockhopper-co__mcp-server.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | d441327a338d | BLOCK | D | 69 | first audit |
Questions
What tools does @rockhopper-co/mcp-server expose?
20 in total: 16 read-only, 4 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is @rockhopper-co/mcp-server safe to connect to an agent?
No — not without reading the findings first. The audit graded it D (69/100) and found 1 critical or high issue in the source. Each one is listed on this page with the file and line it is on.
What credentials does @rockhopper-co/mcp-server need?
It reads ROCKHOPPER_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does @rockhopper-co/mcp-server run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @rockhopper-co/mcp-server at 2.1.1.
How current is this page?
The grade is for one exact copy of the source (d441327a338d), read on 2026-10-12. The repository is watched and re-audited when it changes.