QuickNode MCP for AI agents
Agents read QuickNode MCP at once. Changes and sends are held for a person's approval by default.
About QuickNode MCP
QuickNode MCP reads live blockchain data and manages endpoints, security, rate limits, logs, usage, and billing according to the connected Viewer or Admin role.
What an agent can do in QuickNode MCP
Every QuickNode MCP action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in QuickNode MCP without asking first. 11 actions.
- Call-rpcCall an allowed read-only JSON-RPC method through authenticated Quicknode Tooling Access. Use the network slug from list-chains; call list-chains first if it is unknown.
- Get-billingGet billing data for the user's Quicknode account. Use type to get invoices or payments.
- Get-endpointGet a specific web3 Quicknode endpoint details by id
- Get-endpoint-log-detailsGet detailed request and response information for a specific log entry. This provides the raw request payload and full response that were logged for a particular request
- Get-endpoint-metricsGet metrics for a specific Quicknode endpoint. Supports various metrics like method calls, response status, and response times over different time periods
- Get-rpc-usageGet the usage data for the user's Quicknode RPC account. Use breakdown_by to get usage by endpoint, method, or chain. The start_time and end_time parameters are ISO 8601 date strings.
- List-chainsList all chains and network slugs supported by Quicknode.
- List-endpoint-logsList the request/response logs for a specific Quicknode endpoint
- List-endpoint-method-rate-limitsList all method rate limits for a specific Quicknode endpoint
- List-endpointsGet web3 Quicknode endpoints for the user, this is a list of all the endpoints that the user has created across all chains and networks. Supports pagination via limit and offset parameters
- List-endpoint-securityList all security options and rules for a Quicknode endpoint. Shows which security features are enabled/disabled and all configured rules (ip, jwt, referrer, domain_mask, token) with their rule IDs.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 11 actions.
- Create-endpointCreate a new web3 RPC endpoint for a given chain and network under user's Quicknode account. This can error if the chain and network combination is not supported or if the user has reached their endpo
- Create-endpoint-method-rate-limitCreate a new method-specific rate limiter for a Quicknode endpoint
- Create-security-ruleCreate a security rule for a Quicknode endpoint. Supports types: ip, jwt, referrer, domain_mask, token. Provide the type-specific fields alongside the type parameter.
- Delete-endpointArchive a Quicknode endpoint by its ID. This will archive the endpoint and make it inactive. THIS IS A DESTRUCTIVE ACTION
- Delete-endpoint-method-rate-limitDelete a method-specific rate limit from a Quicknode endpoint. THIS IS A DESTRUCTIVE ACTION
- Delete-security-ruleDelete a security rule from a Quicknode endpoint. THIS IS A DESTRUCTIVE ACTION. Use the list-endpoint-security tool first to find the rule type and rule_id.
- Disable-tooling-accessDisable account-level Quicknode Tooling Access.
- Enable-tooling-accessEnable account-level Quicknode Tooling Access. This provisions an account-level shared RPC endpoint for use by Quicknode developer tools and caches its short-lived access credential.
- Update-endpoint-method-rate-limitUpdate an existing method-specific rate limit for a Quicknode endpoint
- Update-endpoint-rate-limitsUpdate the general rate limits (RPS, RPM, RPD) for a Quicknode endpoint. Pass a positive integer to set a user override for that bucket, or pass -1 to remove an existing user override and fall back to
- Update-endpoint-security-optionsUpdate security options for a specific Quicknode endpoint
Changes wait in Needs you
Changes and sends in QuickNode MCP are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
QuickNode MCP questions
Can an agent change data in QuickNode MCP on its own?
Not by default. Changes and sends in QuickNode MCP are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in QuickNode MCP?
This connector lists 11 read actions. Reads run at once, without waiting for approval.
How does QuickNode MCP connect?
It connects with dcr oauth. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.