[CON-918] Document MCP blockchain RPC tools in build-web3 - #9
Open
0xsergen wants to merge 2 commits into
Open
Conversation
The Quicknode MCP server exposes call-rpc, enable-tooling-access, and disable-tooling-access for read-only blockchain calls through Tooling Access. The skill's MCP reference covered only account management. - mcp-reference.md: new "Blockchain RPC (Tooling Access)" section covering inputs, network slugs, read-only enforcement, and the account-wide effect of disabling; new tool table, example prompts, and updated role table - SKILL.md: prefer call-rpc for one-off onchain reads instead of asking the user for an endpoint URL - Plugin manifests, server.json, marketplace entries, and README: descriptions now cover live reads alongside management - Plugin version 1.0.1 -> 1.0.2
johnpmitsch
reviewed
Aug 21, 2026
|
|
||
| ### Enabling And Disabling | ||
|
|
||
| `enable-tooling-access` provisions the endpoint and caches the credential. `disable-tooling-access` turns the setting off. Both take no arguments and are idempotent, and both require the **Admin** role. A Viewer connection can call `call-rpc` once Tooling Access is on, but cannot turn it on; if `call-rpc` fails because the setting is off, ask the user to reconnect with Admin or enable it from another interface. |
There was a problem hiding this comment.
Same feedback here as the docs PR, can we not use "endpoint" for tooling access? You can say setting or the tooling access URL
Describe Tooling Access as an account setting rather than an endpoint, simplify the network slug guidance, and use a real address in the example prompt.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Quicknode MCP server exposes
call-rpc,enable-tooling-access, anddisable-tooling-accessfor read-only blockchain calls through ToolingAccess. The skill's MCP reference covered only account management.
references/quicknode/mcp-reference.md: new "Blockchain RPC (Tooling Access)" section covering inputs, network slugs, read-only enforcement, and the account-wide effect of disabling; new tool table and example prompts; updated role tableSKILL.md: prefercall-rpcfor one-off onchain reads instead of asking the user for an endpoint URLserver.json, marketplace entries, and README: descriptions now cover live reads alongside management