QuickNode 远程 MCP 服务器 – 官方端点、工具列表与一键连接指南
QuickNode 官方托管的远程 MCP 服务器。QuickNode 远程 MCP,为代理提供多链 RPC 访问:查询区块、交易与智能合约状态。
本页收录其官方远程端点、传输协议、认证方式、全部工具 Schema、实时可用性拨测与安全审计结果,并为 Cursor、Claude Code、VS Code、ChatGPT 等 10 大客户端提供一键接入指引。
🔒 Client-side only — never leaves your browser.
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"quicknode": {
"url": "https://mcp.quicknode.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}claude mcp add --transport http quicknode https://mcp.quicknode.com/mcp
With credential header:
claude mcp add --transport http quicknode https://mcp.quicknode.com/mcp --header "Authorization: Bearer YOUR_API_KEY"
Or add to .vscode/mcp.json:
{
"servers": {
"quicknode": {
"type": "http",
"url": "https://mcp.quicknode.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://mcp.quicknode.com/mcp - Provide your API key / Bearer token when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"quicknode": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.quicknode.com/mcp",
"--header",
"Authorization: Bearer YOUR_API_KEY"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"quicknode": {
"serverUrl": "https://mcp.quicknode.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"quicknode": {
"url": "https://mcp.quicknode.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.quicknode] url = "https://mcp.quicknode.com/mcp" bearer_token_env_var = "QUICKNODE_TOKEN"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"quicknode": {
"type": "streamableHttp",
"url": "https://mcp.quicknode.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"quicknode": {
"httpUrl": "https://mcp.quicknode.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}🧰 QuickNode MCP 工具与 Schema(0)
| Tool | Safety | Description | Parameters |
|---|
🛡️ 安全评级、质量与上下文 Token 审计
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- Static credential (Bearer token / API key) — protect it in client config
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
🔐 OAuth 2.1 与安全
- 认证方式
- Bearer Token
- 动态客户端注册(DCR)
- —
- PKCE S256
- —
- 受保护资源元数据
- https://mcp.quicknode.com/.well-known/oauth-protected-resource
📡 官方远程端点与传输协议
远程端点 https://mcp.quicknode.com/mcp 采用 Streamable HTTP(流式 HTTP,2025-03-26 规范)。Streamable HTTP 在单一 POST 端点上完成 JSON-RPC 双向交互,是当前 MCP 规范推荐的传输方式,可直接被 Claude、Cursor、VS Code 等客户端以 URL 形式接入,无需 npx mcp-remote 桥接。
接入前可将端点粘贴至本站 在线 MCP Inspector 实测 initialize / tools/list 握手,确认真实协议行为。
🔐 认证与权限机制
认证方式为 Bearer Token。需要在客户端配置中提供 Authorization: Bearer <你的密钥> 请求头,凭据可在 QuickNode 控制台获取。
🛡️ 上下文开销与安全审计
该服务端当前登记 0 个工具。安全评级为 A,官方直营来源。工具名与 Schema 越精简,对上下文窗口的"税"越低;可用 feecalculator.app 估算每次调用的边际成本。
🧩 主流客户端快速接入
本站为 QuickNode 生成了 Cursor / Claude Code / VS Code / ChatGPT / Windsurf / Kiro / Codex / Cline / Gemini 等 10 大客户端的专属配置——包括一键 deeplink、claude mcp add 命令与 JSON/TOML 片段。下方选择你的客户端即可查看 1 分钟接入步骤。
📖 QuickNode 详解
QuickNode — Remote MCP Server
QuickNode's remote MCP gives agents multi-chain RPC access — query blocks, transactions and smart-contract state across dozens of blockchain networks. The remote endpoint means there is nothing to install — point your MCP client at the URL and supply your credential as a bearer token. QuickNode operates and versions the server themselves, so tool coverage tracks their API surface as it ships.
Official QuickNode Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.quicknode.com/mcp - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. QuickNode does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
QuickNode uses bearer-token authentication. Create an access token in your QuickNode account settings, then send it as Authorization: Bearer <token>. No OAuth redirect flow is involved.
All 0 cataloged tools are read-only — QuickNode cannot mutate your account data, which makes it safe to connect broadly.
Common Troubleshooting & Connection Tips
- 401/403 responses — your credential is missing or rejected. Regenerate the key/token and make sure it is sent as an
Authorization: Bearerheader on every request, including theinitializecall. - "Session expired" / stale
Mcp-Session-Id— just re-sendinitialize; stateless clients can ignore session headers entirely.
🚀 如何接入 QuickNode 远程 MCP
- 获取远程端点 — 复制官方端点 https://mcp.quicknode.com/mcp,并先在 QuickNode 控制台申请 API 凭据。
- 写入客户端配置 — 在 Cursor 的 mcp.json / Claude Code CLI / 其他客户端中添加该 URL 与 Authorization 头(见下方分客户端指南)。
- 授权并验证 — 保存配置后,在本站 Inspector 中运行 initialize 与 tools/list 验证连通性。
🔌 QuickNode × 各客户端连接指南
❓ 常见问题
QuickNode 远程 MCP 服务器是官方提供的吗?
本条目标记为「官方直营」。端点由 QuickNode 官方运营,所有收录端点均经过真实 MCP initialize 握手验证。
如何在 Claude / Cursor 中连接 QuickNode?
复制远程端点 https://mcp.quicknode.com/mcp:Claude Code 执行 claude mcp add --transport http quicknode https://mcp.quicknode.com/mcp;Cursor 可直接使用本页的一键 deeplink 或在 ~/.cursor/mcp.json 中添加 { "mcpServers": { "quicknode": { "url": "https://mcp.quicknode.com/mcp" } } }。
连接时返回 401 或需要密钥怎么办?
该端点需要 Bearer Token / API Key:在 QuickNode 控制台申请凭据后,按对应客户端文档将其写入 headers 配置。
本地 stdio MCP 和这个远程 MCP 有什么区别?
本地 MCP 通过 npx/uvx 在你的机器上启动 stdio 子进程,依赖本地运行时且密钥以明文写入配置文件;远程 MCP 是 QuickNode 托管的 HTTPS 端点,免安装、支持 OAuth 2.1 授权流,且同一端点可跨桌面与移动端复用。详见 本地 vs 远程 MCP 对比。