Quicknode MCP

Live

OAUTH 2.0

DEVELOPER TOOLS

Developer Tools

Connect to QuickNode MCP. Create and manage blockchain RPC endpoints, configure security rules, set rate limits, and monitor usage and logs from your AI workflows.

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Quicknode MCP
agent · Acme Q3
Run
Create-Endpoint in Quicknode MCP
S
quicknodemcp_create-endpoint
85ms
Quicknode MCP agent
Create a new web3 rpc endpoint for a given blockchain and network under the user's quicknode account..
Sources: Quicknode MCP
quicknodemcpmcp
1 tool call
18:29
Message Claude...

Quicknode MCP tools for AI agents

CALL ANY TOOL
12 tools covering create-endpoint-method-rate-limit, create-endpoint, create-security-rule.
quicknodemcp_get-billing
Get-billing
Retrieve billing data (invoices or payments) for the user's QuickNode account.
Parameters
Name
Type
Required
Description
type
string
Required
The type of billing data to retrieve: "invoices" or "payments"
quicknodemcp_list-chains
List-chains
quicknodemcp_get-endpoint
Get-endpoint
quicknodemcp_get-rpc-usage
Get-rpc-usage
quicknodemcp_list-endpoints
List-endpoints
quicknodemcp_create-endpoint
Create-endpoint
quicknodemcp_list-endpoint-logs
List-endpoint-logs
quicknodemcp_create-security-rule
Create-security-rule
quicknodemcp_get-endpoint-metrics
Get-endpoint-metrics
quicknodemcp_list-endpoint-security
List-endpoint-security
quicknodemcp_get-endpoint-log-details
Get-endpoint-log-details
quicknodemcp_update-endpoint-rate-limits
Update-endpoint-rate-limits
quicknodemcp_list-endpoint-method-rate-limits
List-endpoint-method-rate-limits
quicknodemcp_update-endpoint-security-options
Update-endpoint-security-options
quicknodemcp_create-endpoint-method-rate-limit
Create-endpoint-method-rate-limit
quicknodemcp_update-endpoint-method-rate-limit
Update-endpoint-method-rate-limit
quicknodemcp_delete-endpoint
Delete-endpoint
quicknodemcp_delete-security-rule
Delete-security-rule
quicknodemcp_delete-endpoint-method-rate-limit
Delete-endpoint-method-rate-limit
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="quicknodemcp")

mcp = MultiServerMCPClient({
"quicknodemcp": {
"url": "https://mcp.scalekit.com/quicknodemcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "quicknodemcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/quicknodemcp
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "quicknodemcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/quicknodemcp
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="quicknodemcp")
# Connect to MCP at https://mcp.scalekit.com/quicknodemcp
# Pass: Authorization: Bearer + token
Try these prompts
Paste any prompt into your agent to get started.
Get started
Copy the prompt
Copied
Update security settings (CORS, HSTS, IP allowlists, JWT, tokens, referrers, domain masks) for a QuickNode endpoint?
Copy the prompt
Copied
Update the general rate limits (requests per second, minute, or day) for a QuickNode endpoint?
Advanced
Copy the prompt
Copied
Update the rate, interval, or status of an existing method-specific rate limit on a QuickNode endpoint?
Copy the prompt
Copied
List all web3 RPC endpoints in the user’s QuickNode account with optional pagination?
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Quicknode MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Quicknode MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Quicknode MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Quicknode MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
Engineering Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Engineering Teams
Engineering standup agent
Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.
Engineering Teams
Auto release notes agent
Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
Test other agents
See the same per-user auth pattern across other connectors.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs into structured release notes, publish the page to Notion, and announce the release in Slack.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Quicknode as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Quicknode OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Quicknode?
Yes. Pass a tool name filter to listScopedTools so the DevOps agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Quicknode.

What happens when a user revokes Quicknode access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent change RPC endpoints or security rules?
Only on the authorizing user's QuickNode account, with their role. Filter the toolset to monitoring-only if you want usage and log visibility without endpoint mutations.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""quicknodemcp"": {
""url"": ""https://mcp.scalekit.com/quicknodemcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.quicknodemcp]
url = ""https://mcp.scalekit.com/quicknodemcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""quicknodemcp"": {
""url"": ""https://mcp.scalekit.com/quicknodemcp"",
""type"": ""http""
}
}
}