Claude OpenRush connectorWhat Claude can do in your OpenRush account.
The Claude OpenRush connector exposes 20 tools. 19 read data, 0 write, 1 stays undocumented. Below: what Claude analyzes for your SEO and ad campaigns, what each call costs in credits, and what you need to hook up on the Google side before you start.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when you have to explain why a competitor outranks you
OpenRush feeds Claude fresh marketing data: live Google results, a search index, backlinks, site audits, and your own Search Console, Google Analytics and Google Ads numbers. You ask in plain words, and Claude picks the tools it needs while it answers.
Size up a market. inspect_domain maps a domain, discover_competitors finds its organic rivals, and compare_keyword_coverage isolates the keywords where they rank and you don't.
Find where to earn links and mentions. compare_backlink_gap lists the sites linking to several competitors but not to you; inspect_ai_visibility measures how often a domain is cited in Google's AI Overviews.
Read your real numbers. get_search_performance, get_website_analytics and get_ad_performance read Search Console, Google Analytics and Google Ads, not estimates, since that data comes from Google itself rather than from a model.
What Claude doesn't do here: change a site, a campaign or a Google account, since no source describes a writing tool. Every call uses credits, deducted the moment it starts. And nothing fires on its own: no report unless you ask. Scheduled tracking belongs to an automation platform, covered in the Integrations hub.
The vocabulary, in one minute
Five words to keep in mind before connecting OpenRush.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can use it while it answers you.
- Tool
- One named capability the connector opens to Claude. Claude picks which ones to call; the directory sheet gives the full list.
- Authorization
- OpenRush's sign-in screen, where you give Claude the access it will use. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for in the chat before an action that would change your account on your behalf.
- MCP
- The open standard behind connectors: it is what lets an assistant fetch data from an outside service.
Connect the Claude OpenRush connector in three steps
- 01
Find OpenRush
In Claude's settings, open Customize, then Connectors, and search for OpenRush. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization first.
- 02
Sign in to OpenRush
Click Connect on its row and sign in through the window OpenRush opens itself. If the connection breaks, Disconnect and a fresh connection sort it out.
- 03
Confirm the access
Read OpenRush's authorization screen before you accept: OpenRush, not Claude, sets what the access covers. You can withdraw it later from Claude or from your OpenRush account.
The 20 tools in the Claude OpenRush connector
OpenRush gives Claude 20 tools: 19 that read your account, 0 that change something in it, and 1 no official source describes.
Nineteen tools read data and one stays undocumented. Names stay as Claude shows them; credit costs come from OpenRush's documentation.
- 19 read
- 1 not documented
What Claude reads (19)
19 toolsResearch, competition, links, visibility and your own Google numbers, with nothing changed.
audit_site
Runs a quick technical and content health audit over a sample of a domain's pages, ten by default and twenty at most, for 9 credits.
compare_backlink_gap
Computes in one call the domains linking to several of your competitors, ranked by how many rivals they link to and then by authority, with the ones you already earned flagged. It is the priciest tool, at 40 credits.
compare_keyword_coverage
Surfaces the keywords where competitors rank and your domain doesn't, plus the ones where you're losing ground, for 12 credits.
discover_ai_citations
Shows which domains AI cites across a whole category: the map of places where a mention would count. After the backlink gap, it is the most expensive call, at 22 credits.
discover_competitors
Finds a site's rivals in organic search, either from domain overlap or from seed keywords, for 7 credits. OpenRush's documentation points to it whenever the goal is to find search competitors.
export_dataset
Fetches every row of a dataset flagged in an earlier response, instead of re-running the same queries. A single credit per call.
get_ad_performance
Reads real figures from an activated Google Ads account: spend, impressions, clicks, conversions and value, with CTR, CPC, ROAS and cost per conversion recomputed. One call reads one account, in its own currency.
get_search_performance
Reports the data Google Search Console measured for your site: real clicks, impressions, CTR and weighted position. These are Google's own numbers, not an OpenRush estimate.
get_website_analytics
Reads your measured Google Analytics traffic: sessions, users, new users, engaged sessions, page views and engagement time, with ratios recomputed from the raw counts.
inspect_ai_visibility
Measures how often a domain is cited as a source in AI answers, alone or against named competitors, for 20 credits.
inspect_backlinks
Inspects a domain's inbound link profile from the backlink index, sliced into views, each view being one call to OpenRush's data provider. OpenRush calls it a lean building block, not a bundle.
inspect_domain
Gives a factual snapshot of one domain: top keywords, top pages, estimated traffic, dominant intents and likely competitors. OpenRush frames it as the starting map, for 9 credits.
inspect_keyword
Drills into a single keyword rather than a whole list, for 5 credits. OpenRush's documentation points here when the goal is to drill into one keyword rather than a list, and the tool only reads data about that term.
inspect_page
Analyzes one exact URL rather than the whole domain, for 3 credits. OpenRush's documentation points here when the goal is to drill into one page, and the tool reads that URL's data without changing anything on it.
inspect_search_visibility
Checks where a domain ranks across a set of keywords you supply, for 10 credits. OpenRush points to it for checking where a site ranks on specific keywords.
inspect_serp
Grabs a snapshot of live Google results for one query, as they appear at the moment of the call. It is one of the cheapest calls, at 2 credits.
list_connections
Lists the websites tied to your OpenRush account with each one's connection state per source, plus the activated ad accounts. This call uses no credits.
list_websites
Alias OpenRush keeps for list_connections: it returns the same list of websites and ad accounts, at no credit cost. OpenRush notes that the name exposed to agents is list_connections, and that list_websites still answers.
research_keywords
Expands a seed term into a ranked list of demand, for 3 credits. OpenRush's documentation points to it when you are looking for keyword ideas, and the output is ranked by demand.
Undocumented (1)
1 toolA name published on the sheet that no official source describes.
describe_capabilities
The directory sheet publishes this name, but no official source describes what the tool does or what it costs in credits. OpenRush's documentation doesn't mention it, so nothing reliable can be said about it, and the general approval rule applies.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you.
For OpenRush, no source describes a confirmation specific to any of the twenty tools, so the general rule applies, the undocumented one included. One practical point matters more here: every call uses credits as soon as it starts, and Claude chooses on its own which tools to call. On Team and Enterprise, owners decide whether a member may let some actions through, and they can limit the connector for the whole organization.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan: for OpenRush, that answer isn't published anywhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members connect. For the current state, the OpenRush sheet in the official directory is the reference, and the only place that shows it.
Where the OpenRush connector stops
A connector isn't an automation: Claude queries OpenRush while it is answering you, and no report goes out by itself.
By default the sheet only exposes reading, an observed floor and not a guarantee: an admin can open actions that appear on no public sheet. The directory badge isn't a security audit. Only OpenRush documents this connector, and one of its tools, describe_capabilities, isn't described there. Its limits below come from OpenRush's own pages. More connectors the team has studied sit in the Claude connectors hub.
Need help connecting OpenRush to Claude?
A person reads every message.
