Quicknode

io.github.quicknodePublished by GitHub account quicknodev1.0.1Updated Oct 24, 2026

Manage your blockchain infrastructure across 80+ chains with your agents.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Quicknode's remote MCP endpoint that lets an AI agent manage blockchain infrastructure across 80+ chains and plan Web3 app builds.

What you can do
  • Manage blockchain infrastructure across 80+ chains from an agent session
  • Plan Web3 app builds: chain, architecture, stack, data layer and production posture
  • Use bundled plugin guidance for Web3 development with optional Quicknode infrastructure integration
  • Work from supported clients such as Cursor, Windsurf, VS Code, Zed, Codex, Claude Code and ChatGPT
When to use it
Useful when you are building or operating Web3 applications and want an assistant to reason about chain choice, architecture and infrastructure, or to manage Quicknode-hosted blockchain resources without leaving the chat.
Requirements
A remote MCP endpoint at mcp.quicknode.com; OAuth authentication is required. A Quicknode account and a compatible MCP client are needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your Quicknode account, so review the scopes requested. Infrastructure actions may create or change billable resources on your Quicknode plan. The README notes that pricing, plan tiers and rate-limit figures in bundled references are dated snapshots that can drift from live docs.

Installation

In SourceWeft

  1. Open Quicknode in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.quicknode%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "quicknode": {
      "type": "http",
      "url": "https://mcp.quicknode.com/mcp"
    }
  }
}

README

Quicknode Agent Plugins

Agent plugins from Quicknode for building Web3 apps with AI agents.

Available plugins

PluginDescription
build-web3Build Web3 apps with your AI agent: choose a chain, architecture, stack, data layer, and production posture. Powered by optional Quicknode infrastructure integration.

Install

For Claude Code, add this marketplace and install the build-web3 plugin:

/plugin marketplace add quicknode/agent-plugins

For Codex, see the Codex install guide. Codex discovers this repository's plugin through .agents/plugins/marketplace.json and uses plugins/build-web3/.codex-plugin/plugin.json to load the bundled skill and MCP server.

For ChatGPT, use the existing listing on its marketplace.

Content rules

Plugin skills and references in this repo should stay stable, useful, and self-contained:

  • Stable concepts, product categories, capability names, and decision guidance belong in this repo so the plugin works without a network round-trip.
  • Perishable facts — plan tiers, pricing, rate-limit numbers, RPC method tables, schemas — are allowed when the repo needs to be self-sufficient for a product, but every such table must carry a dated snapshot note (e.g. "As of 2026-02-02.") and a link to the live docs (https://www.quicknode.com/docs/) so a reader knows it can drift and where to check.
  • Keep dated content current using plugins/build-web3/skills/build-web3/PRODUCT_CATALOG.md's sync runbook — it's the maintenance source of truth for which product references exist, where they live, and how to refresh them.

License

MIT. See LICENSE.md.

Source: README.md at commit 66d55fa

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts