- Home
- Resources
- Integrations
- Rockhopper
Claude Rockhopper connectorWhat Claude can do in your Rockhopper account.
The Claude Rockhopper connector exposes 16 tools: 5 read, 8 write, 3 undocumented. They cover the history, versions, reviews and comments of your tracked workbooks. Below: what Claude digs up, what it changes, and what it can't reach.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for a finance team
When a number moves in a financial model, the question is no longer just "who?" but "a person or an AI agent?". Rockhopper keeps that trail on your tracked Excel and Google Sheets files. With the connector, you ask Claude in the chat and it pulls the history, versions, reviews or comments for you.
Trace a number back. When a figure moved between versions, get_cell_history pulls the cell or metric history across versions, and get_unattributed_changes shows what's sitting in the file without being committed.
Get a version signed off. Once a version is ready, create_version commits the current changes as a new version, then create_review_request sends it for sign-off before it becomes final.
Keep up with the discussion. When a file carries open threads, get_file_comments brings them in, reply_to_comment answers them and resolve_comment closes the thread once the point is settled.
What Claude doesn't do here: edit cell data or formulas, per the publisher. It only works on files already enrolled in your Rockhopper workspace. And nothing fires on its own: no alert lands when a cell changes. That kind of hands-off watch is a job for an automation tool; the Integrations page covers that side, and Claude connectors lists the other links you can set up.
The vocabulary in one minute
Five words worth knowing before you connect Rockhopper.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work on it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before finishing something that changes your account, shown in the chat right when it matters.
- MCP
- The common standard behind connectors: it's what lets an assistant like Claude hold a conversation with an outside service.
Connect Rockhopper to Claude in three steps
- 01
Find Rockhopper
In Claude's settings, open Customize, then Connectors, and spot Rockhopper in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in through the window the service opens itself. If the link breaks one day, hit Disconnect and connect again: that's the intended fix.
- 03
Read the authorization screen
Read the authorization screen before you approve. It belongs to the service, not to Claude, and it decides what the access covers. You can also revoke that access later from the service account itself.
The 16 tools of the Claude Rockhopper connector
Rockhopper gives Claude 16 tools: 5 that read your account, 8 that change something in it, and 3 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. Names stay as Claude shows them.
- 5 read
- 8 write
- 3 not documented
Tools index
What Claude reads (5)
5 toolsFive tools that look at history, versions, comments and file search.
get_cell_history
Pulls the history of a cell or a metric across the file's versions. You see how the value moved, version by version, without opening every copy.
get_file_comments
Brings in the comments and discussion threads on a workbook, including the latest conversation tied to that specific file.
get_file_versions
Lists the version history of a tracked file. You know which versions exist before you compare two periods or hunt for where an error crept in.
get_unattributed_changes
Surfaces work sitting in a file that hasn't been committed to a version yet, what Rockhopper calls unattributed. It's work in progress, not yet signed.
search_files
Searches the files enrolled in Rockhopper by name, comment text or version notes. Handy when you can't remember where a workbook lives.
What Claude changes (8)
8 toolsEight tools that touch your tracked files. No source spells out their confirmation: the general rule below applies.
add_comment
Approval: see the rulePosts a new comment on a tracked workbook, which joins the file's discussion in Rockhopper. It lands in the discussion already tied to that workbook.
approve_review
Approval: see the ruleSigns off on an open review request for a specific version. The version then clears the approval step Rockhopper puts in place before it counts as final.
cancel_review
Approval: see the ruleWithdraws a review request already sent for a version. Useful when the submitted version is no longer the right one and another has to take its place.
create_review_request
Approval: see the ruleOpens a review request on a given version, so the changes go through sign-off before they're final. It's where the approval loop starts.
create_version
Approval: see the ruleCommits the file's current changes as a new version. What was unattributed becomes a named step in the history.
rename_file
Approval: see the ruleChanges the name of a file enrolled in Rockhopper.
reply_to_comment
Approval: see the ruleAdds a reply under an existing comment, in the same thread. The discussion stays grouped instead of scattering into loose notes.
resolve_comment
Approval: see the ruleMarks a comment or thread as resolved once the point is handled. Open topics stay visible, settled ones get out of the way.
Undocumented (3)
3 toolsThe directory publishes these three names and nothing else. No official text says what they do, and we won't guess from a name.
discard_changes
This name sits in the directory's tool list, and no official source describes it: not the sheet, not a public help page.
get_reviews
The directory lists this name with no description at all. Rockhopper's sheet gives it not a single sentence, and no other public source mentions it.
list_files
A name published by the directory, without one official sentence to explain it. Neither the publisher nor Anthropic documents it so far.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request shows up in the chat, right when it matters.
No source says whether Claude asks before creating a version, approving a review or resolving a comment: that default rule is what covers them. On a Team or Enterprise workspace, owners decide whether a member can let certain actions through without being asked again, and they can shut off a connector's writes for the whole organization. Nobody overrides that from their own account, and Claude never sees more than you can.
Which plans include it
Out of 819 sheets in the official directory, none shows availability by plan. Connector by connector, the answer isn't published anywhere: it's a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member can connect. For the current status, the Rockhopper sheet in the official directory is where to look.
Where Rockhopper stops inside Claude
A connector isn't an automation. Claude calls these tools while it answers you: nothing starts when a cell changes or a review is waiting.
Only the publisher documents this connector, and only through the description on its sheet: Rockhopper's technical docs require a sign-in and couldn't be read when this page was written. Neither Claude's help center nor Anthropic's developer docs have a page for it. The directory's partner badge isn't a security audit. Anthropic says so on every sheet: it doesn't choose the tools a publisher exposes and doesn't guarantee they behave as described.
Need help connecting Rockhopper to Claude?
A person reads every message.