QuickNode MCP
for LuumenAI

Read endpoint traffic, usage, and billing, then change limits with approval

Connect QuickNode and your agent can see the whole account: every endpoint across chains and networks, request logs, per-method rate limits, security rules, RPC usage, and billing. Those reads answer right away. Changes — creating an endpoint, tightening a rate limit, adding a security rule — are previewed and sent for approval first. Access follows the Viewer or Admin role on the connected account.

Book a DemoDownload Luumen

The QuickNode MCP toolbox

22 tools: 11 read, 11 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadCall-rpcCall an allowed read-only JSON-RPC method through authenticated Quicknode Tooling Access.
  • ReadGet-billingGet billing data for the user's Quicknode account.
  • ReadGet-endpointGet a specific web3 Quicknode endpoint details by id
  • ReadGet-endpoint-log-detailsGet detailed request and response information for a specific log entry.
  • ReadGet-endpoint-metricsGet metrics for a specific Quicknode endpoint.
  • ReadGet-rpc-usageGet the usage data for the user's Quicknode RPC account.
  • ReadList-chainsList all chains and network slugs supported by Quicknode.
  • ReadList-endpoint-logsList the request/response logs for a specific Quicknode endpoint
  • ReadList-endpoint-method-rate-limitsList all method rate limits for a specific Quicknode endpoint
  • ReadList-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.
  • ReadList-endpoint-securityList all security options and rules for a Quicknode endpoint.
  • WriteCreate-endpointCreate a new web3 RPC endpoint for a given chain and network under user's Quicknode account. Approval by default
  • WriteCreate-endpoint-method-rate-limitCreate a new method-specific rate limiter for a Quicknode endpoint Approval by default
  • WriteCreate-security-ruleCreate a security rule for a Quicknode endpoint. Approval by default
  • WriteDelete-endpointArchive a Quicknode endpoint by its ID. Approval by default
  • WriteDelete-endpoint-method-rate-limitDelete a method-specific rate limit from a Quicknode endpoint. Approval by default
  • WriteDelete-security-ruleDelete a security rule from a Quicknode endpoint. Approval by default
  • WriteDisable-tooling-accessDisable account-level Quicknode Tooling Access. Approval by default
  • WriteEnable-tooling-accessEnable account-level Quicknode Tooling Access. Approval by default
  • WriteUpdate-endpoint-method-rate-limitUpdate an existing method-specific rate limit for a Quicknode endpoint Approval by default
  • WriteUpdate-endpoint-rate-limitsUpdate the general rate limits (RPS, RPM, RPD) for a Quicknode endpoint. Approval by default
  • WriteUpdate-endpoint-security-optionsUpdate security options for a specific Quicknode endpoint Approval by default

One prompt, start to finish

What a governed QuickNode MCP run looks like inside Luumen.

Questions

How does LuumenAI connect to QuickNode MCP?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in QuickNode MCP on its own?

Read actions answer immediately. Anything that writes — create-endpoint, create-endpoint-method-rate-limit, create-security-rule, delete-endpoint, and more — is shown as a plan and requires approval by default, including the 3 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to QuickNode MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task statusAffindaRead parsed documents, collections, and annotations — change them with approvalAgent MailGive the agent its own mailbox for reading threads and sending updatesAI/ML APIInspect assistants, threads, and runs — and change them as approved steps

Put QuickNode MCP to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.

Book a DemoDownload Luumen