Claude QuickNode connectorWhat Claude can do in your QuickNode account.
The Claude QuickNode connector exposes 19 tools. 10 read your account, 9 change it, 0 are undocumented. Below: what Claude can check on your endpoints, what it can change, the role that unlocks changes, and the confirmation it asks for first.
Verified Trustpilot reviews · AI, automation & growth agency
Your node infrastructure, one question away
Running blockchain apps on QuickNode means juggling endpoints across chains, watching logs, tuning rate limits and keeping an eye on the bill. The dashboard does all that, one screen at a time. With the connector, you ask Claude, it calls the right QuickNode tool and answers in the chat, and it asks you before any change goes through.
Diagnose a failing endpoint. Your Arbitrum app throws errors since lunch. list-endpoint-logs pulls the recent logs, get-endpoint-log-details opens the suspicious entry, and get-endpoint-metrics shows whether performance dipped at the same time.
Lock down an endpoint. Before a launch, you want JWT checks on the Ethereum mainnet endpoint. list-endpoint-security shows what is already on, then create-security-rule adds the rule once you confirm.
Keep spending in check. get-rpc-usage breaks usage down by endpoint, method or chain, and get-billing brings the invoices, so you can see which endpoint burns the most before the month closes.
Now the part the directory sheet leaves out. Every change needs the Admin role, chosen when you connect; with Viewer, Claude only reads. QuickNode's docs describe a tool for reading live blockchain data that is not among the 19 listed. And nothing runs on its own when an endpoint starts failing. For that kind of alerting, an automation tool fits, which is a different trade; the Integrations hub gathers that side.
The vocabulary in one minute
Five words you'll meet while plugging QuickNode in.
- 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 sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes something that changes your 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 QuickNode.
Plug QuickNode into Claude in three steps
- 01
Find QuickNode in Claude
In Claude's settings, open Customize, then Connectors, and look for QuickNode in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first, then each member signs in.
- 02
Start the connection
Click Connect on the QuickNode row, then sign in to QuickNode in the window QuickNode opens itself. If that link ever breaks later on, use Disconnect and plug it back in.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to QuickNode, not to Claude, so QuickNode decides what the access covers. You can withdraw that access later from your QuickNode account too.
The 19 tools, sorted by what they do
QuickNode gives Claude 19 tools: 10 that read your account, 9 that change something in it.
Two groups: what Claude reads, available with both roles, and what it changes, which needs Admin and your confirmation. The names stay exactly as Claude shows them.
- 10 read
- 9 write
What Claude reads (10)
10 toolsTen tools that look into your account without changing it, available to both roles.
list-endpoints
Returns every endpoint on your QuickNode account, so Claude knows what exists before it digs further. It is often the first call behind a question.
get-endpoint
Opens the details of a single endpoint you name, instead of the whole list. Claude can then describe its setup in plain words.
list-endpoint-security
Shows the security settings and rules currently applied to an endpoint. You see what protects it before you decide on the next step.
list-endpoint-method-rate-limits
Lists the rate limits set for specific RPC methods on an endpoint. Claude tells you which calls are throttled and at what level.
list-endpoint-logs
Fetches the recent logs of an endpoint. Claude reads through them and points out errors or patterns instead of making you scroll.
get-endpoint-log-details
Brings the full information of a single log entry picked out of the recent logs. That's where the specifics of one failed request live.
get-endpoint-metrics
Retrieves the performance metrics of an endpoint, so Claude can tell you whether it slowed down and when.
get-rpc-usage
Reports your RPC usage, with an optional breakdown by endpoint, by method or by chain. Claude can then rank what consumes the most.
get-billing
Shows your billing invoices or your payment history on QuickNode. Claude can summarise what was charged and when.
list-chains
Lists all the chains QuickNode supports and the networks available on each. Useful to get the exact network name right before you plan anything.
What Claude changes (9)
9 toolsNine tools that modify your account. QuickNode says each one needs the Admin role and your explicit confirmation.
create-endpoint
Asks you firstSpins up a new endpoint on the chain and network you specify. Claude reports what was created once QuickNode confirms.
delete-endpoint
Asks you firstRemoves an endpoint from your QuickNode account, once you've confirmed which one Claude picked.
update-endpoint-security-options
Asks you firstTurns endpoint security features on or off, such as CORS, HSTS or IP filtering. It changes how the endpoint accepts requests.
create-security-rule
Asks you firstAdds a security rule to an endpoint: an IP allowlist, JWT validation, a referrer restriction, a domain mask or an authentication token.
delete-security-rule
Asks you firstDeletes an existing security rule from an endpoint, whatever its type. The protection it provided disappears with it.
update-endpoint-rate-limits
Asks you firstSets the overall rate limits of an endpoint, per second, per minute or per day. It caps how much traffic the endpoint accepts.
create-endpoint-method-rate-limit
Asks you firstAdds a rate limit on one specific RPC method, leaving the other methods alone. Handy when a single call type gets hammered.
update-endpoint-method-rate-limit
Asks you firstAdjusts a method rate limit that already exists on an endpoint, up or down.
delete-endpoint-method-rate-limit
Asks you firstDeletes a method rate limit from an endpoint, so that method falls back to the endpoint's overall limits.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. QuickNode goes further in its own docs: every write needs the Admin role and your explicit confirmation.
On a Team or Enterprise workspace, owners decide whether a member can let some actions through without being asked every time. They can also restrict what a connector may do for the whole organization, for example keep reading open and close every write, and nobody overrides that from their account. Claude works with the QuickNode access you granted, nothing more: a teammate who connected as Viewer gets answers from the same account, never changes.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. The connector-by-connector answer is published nowhere: it is a real gap in the catalogue, not a miss in our research.
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 each member can sign in. For the current state of this one, check the QuickNode sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when an endpoint errors out, a limit is hit or an invoice arrives.
Only QuickNode documents this connector; no Claude help page covers it. The directory badge is not a security audit, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. QuickNode's page and the directory sheet don't even list the same tools, as shown below. For comparison with another connector, see the Claude airtable connector.
Can Claude read live blockchain data through the QuickNode connector?
- Claude directory sheet ↗September 2026Nineteen account tools covering endpoints, security, limits, logs, usage, billing and chains; no tool for reading the chain itself.
- QuickNode MCP documentation ↗August 2026Once connected, you can read live blockchain data, through a dedicated read-only tool.
What this page followsThe directory sheet, read in September 2026, is newer than QuickNode's page from August 2026, yet it doesn't list that tool. For Claude, the sheet's list is what counts: don't count on live chain reads until the tool shows up under your connector settings.
Need help connecting QuickNode to Claude?
A person reads every message.
