Claude Rapid7 Bulk Export connectorWhat Claude can analyse from your Rapid7 exports.
The Claude Rapid7 Bulk Export connector exposes 8 tools: 7 read, 1 write, 0 undocumented. Published by Rapid7, this desktop extension has Claude request an export from Rapid7, load it into a local database on your machine, then answer security questions from it.
Verified Trustpilot reviews · AI, automation & growth agency
What the Rapid7 Bulk Export connector changes
Rapid7's Bulk Export API hands over vulnerability, asset, policy and software data in files built for analysts, not for a quick question. This extension closes that gap: Claude starts the export, follows it, loads the result into a database on your own machine and runs the queries, so a question asked in plain English comes back with figures.
Rank what to patch first. Once the data is loaded, query_rapid7 runs SQL on it, for instance to list the most severe vulnerabilities, and Claude explains the result.
Get the big picture in one answer. get_rapid7_stats returns row counts, severity distribution, CVSS ranges, exploit counts and the split by cloud provider.
Track remediation over months. start_rapid7_export requests remediation data over a date range, check_rapid7_export_status follows the job, and download_rapid7_export loads it so trends can be read across the whole period.
What it will not do: it does not patch, close or reassign anything in Rapid7, and nothing runs on its own when a new scan lands; Claude acts only while it answers you, inside the desktop app where the extension lives. We have no n8n, Make or Zapier page for Rapid7; our Integrations hub lists the platforms we cover, and the Claude connectors page gathers the others.
Five words before you install
The Claude vocabulary this page relies on, in one minute.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work with it while it answers you.
- Tool
- One named thing a connector lets Claude do on that account. Claude picks the tools it needs itself; the directory sheet lists them by name.
- Authorization
- The access you hand Claude on the service, granted once per person on the service's own terms, and taken back the same way.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes an account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Rapid7.
Install the Claude Rapid7 Bulk Export connector in three steps
- 01
Find the extension in the settings
In Claude Desktop, open the settings, go to Customize then Connectors, and search for Rapid7 Bulk Export. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before members can install it.
- 02
Launch the install from its row
Start it from the Rapid7 Bulk Export line with Connect and complete the steps the service asks for. If the extension misbehaves later, Disconnect it and install it again: that is the documented repair for a broken link.
- 03
Read the access you grant
Before you confirm, read any permission or access screen carefully: it comes from the service, not from Claude, and it decides what the access covers. Claude then works with exactly that access and nothing beyond it.
The 8 tools of the Rapid7 Bulk Export connector
Rapid7 Bulk Export gives Claude 8 tools: 7 that read your account, 1 that change something in it.
One tool starts a job on Rapid7's side; the seven others follow it, load the files locally and read them. Names stay exactly as Claude shows them.
- 7 read
- 1 write
What Claude reads (7)
7 toolsSeven tools that track exports, bring their files onto your machine and query the local copy.
check_rapid7_export_status
Reports once, without waiting, where an export stands: Rapid7's own status, the local download and load progress, or for a long remediation job, which time window is loading and which are done.
download_rapid7_export
Fetches a finished export's Parquet files and loads them into the DuckDB database on your computer, in the background, returning straight away. The data becomes queryable once the status check says the load is complete.
load_rapid7_parquet
Reads Parquet files you already have straight from disk, skipping the call to Rapid7 entirely. The files must sit in the extension's imports folder in your home directory.
query_rapid7
Runs SQL against the data that has been loaded. Rapid7 locks the connection after loading, blocking file and network access at the database level.
get_rapid7_schema
Returns the column names and data types of every loaded table, so Claude knows which fields exist before it builds a query.
get_rapid7_stats
Produces an overview of the loaded data: row counts, severity distribution, CVSS score ranges, exploit counts and the breakdown by cloud provider, all in one call.
list_rapid7_exports
Shows the recent export history with IDs, dates, statuses and row counts, which makes it easy to find a previous export and reload it.
What Claude starts on Rapid7 (1)
1 toolOne tool that asks Rapid7's servers to prepare a new export.
start_rapid7_export
Approval: see the ruleAsks Rapid7's servers to begin a new export job of one of four types: vulnerability, policy, remediation or installed asset software. It returns immediately with an ID to follow.
What Claude asks before it acts
By default, Claude stops and asks before each action it carries out on an account for someone. The only tool that starts something on Rapid7's side is start_rapid7_export, and no source describes a confirmation specific to it.
On Team and Enterprise workspaces, owners decide whether a member may let certain actions through without being asked every time. They can also restrict what a connector may do for the entire organization, for example allow reading and close writing, and nobody overrides that from their own account. Claude works with the rights of the person who connected it and no more: what that person cannot reach in Rapid7, Claude cannot reach either.
Which Claude plans include it
Anthropic's general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions like this one install in Claude Desktop.
On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can use it. For this extension's current status, go to its sheet in the official directory, linked from the button at the top of this page. No official source publishes plan availability connector by connector, so that sheet is the one place to check.
What the Rapid7 Bulk Export connector does not do
Only Rapid7 documents this extension, in the README of its public repository: neither the Claude help center nor Anthropic's developer docs have a page on it.
A connector is not an automation: Claude calls its tools during a reply, and nothing fires when a scan finishes or a new vulnerability appears. The verification badge in the directory is not a security audit, and Anthropic says on every sheet that it does not control the tools a publisher exposes, so install only what you know the publisher of. A list of tools is an observed floor, never a ceiling.
Need help connecting Rapid7 Bulk Export to Claude?
A person reads every message.