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.
Verdict
Common use cases
- Check wallet balances across multiple chains
- Decode transaction logs for debugging
- Verify smart contract deployment status
- Monitor gas prices before transactions
- Pull NFT metadata for collection analysis
Integration
- Vendor
- QuickNode MCP
- Category
- other
- Auth
- OAUTH2
- Composio slug
quicknode_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Browse MCP Servers. 2. Search for QuickNode MCP and click Connect. 3. You'll be redirected to QuickNode's OAuth consent screen — sign in with your QuickNode account. 4. Grant Switchy read access to your endpoints and select which blockchain networks (Ethereum, Polygon, Arbitrum, etc.) you want to query. 5. After authorizing, you'll return to Switchy and see QuickNode MCP listed as Connected. 6. Open any Project and type '@QuickNode what's the current block number on Ethereum mainnet?' to test the connection. 7. If the MCP responds with a block number, you're ready to query on-chain data in any conversation.
What teammates see: by default, memories from QuickNode MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check Wallet Balance
@QuickNode check the ETH balance for 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb on Ethereum mainnet
Decode Recent Transaction
@QuickNode decode the transaction 0x8f3e... on Polygon and explain what method was called
Get Current Gas Price
@QuickNode what's the current gas price on Arbitrum in gwei?
Verify Contract Deployment
@QuickNode verify that a contract is deployed at 0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984 on Ethereum
Pull NFT Metadata
@QuickNode get the metadata for token ID 1234 in the Bored Ape Yacht Club contract on Ethereum
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@QuickNode analyze the last 50 transactions for contract 0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984 and summarize the most common function calls
Analyzed 50 recent transactions for the specified contract (Uniswap UNI token). Most frequent function calls: transfer() (32 occurrences), approve() (11 occurrences), transferFrom() (7 occurrences). Average gas used: 65,000 per transaction. Peak activity occurred 6 hours ago with 12 transactions in a 10-minute window. This pattern suggests normal token transfer activity with periodic approval grants.
This synthesis example combines blockchain data retrieval with AI reasoning. The MCP fetches raw transaction data while the AI interprets patterns. Useful for contract monitoring and anomaly detection. Analysis depth is limited by your QuickNode plan's historical data retention (typically 30-90 days).
Use-case deep-dives
When your support team needs real-time blockchain visibility
A 6-person crypto startup runs customer support for a DeFi app. Users report failed transactions or missing balances, and the team needs to verify on-chain data without asking engineers to write custom queries every time. QuickNode MCP connects your AI workspace directly to blockchain nodes—Ethereum, Polygon, Solana, whatever your app runs on. OAuth2 auth means you control which team members can query mainnet versus testnet. The catch: if your support load is under 10 blockchain lookups per day, you're paying for infrastructure you don't use. But once you hit that threshold, having instant wallet history or gas estimates in chat saves 20 minutes per ticket. Worth it if blockchain data is a daily support need.
Real-time contract monitoring for launch-day teams
A 4-person NFT project team is 48 hours from mint. The designer needs to confirm metadata uploads, the community manager is watching wallet activity, and the founder wants live gas price checks before announcing the go-live. QuickNode MCP lets the whole team query contract state and network conditions from the same Switchy workspace—no Etherscan tab-switching, no pinging the solo dev for RPC access. OAuth2 scoping means the community manager can read transaction counts but can't trigger contract writes. The trade-off: if your launch is a one-time event, you're better off with manual Etherscan checks. This setup pays off when you're running multiple drops or need post-launch monitoring for weeks.
When monthly treasury snapshots need blockchain sources
A 10-person DAO operations team publishes a monthly treasury report. The finance lead pulls wallet balances, the governance coordinator tracks proposal execution on-chain, and the comms person writes the summary. Normally this takes 3 hours of manual Etherscan exports and spreadsheet merging. QuickNode MCP centralizes the data pull: the AI workspace queries multi-chain balances, recent transactions, and token prices in one session, then formats the output for the report template. OAuth2 means read-only access for most of the team. The boundary: if your DAO treasury sits in one wallet on one chain, a monthly manual export is faster. This wins when you're tracking 5+ wallets across Ethereum, Arbitrum, and Optimism, and the reporting cycle is weekly or tighter.
Frequently asked
What does the QuickNode MCP do in Switchy?
The QuickNode MCP connects your team's Switchy workspace to QuickNode's blockchain infrastructure APIs. It lets AI agents query blockchain data, interact with smart contracts, and access node endpoints without manually writing API calls. Your team can build blockchain-aware workflows — like monitoring wallet activity or fetching transaction history — directly inside Switchy conversations.
Do I need a QuickNode account to use this MCP?
Yes. The MCP uses OAuth2, so you'll authenticate with your existing QuickNode credentials during setup. Whoever connects it needs login access to the QuickNode account your team wants to use. If your QuickNode plan has API rate limits or endpoint restrictions, those apply to requests the MCP makes on your behalf.
Can the QuickNode MCP write transactions to the blockchain?
That depends on which QuickNode endpoints your account has access to and how the MCP's tools are configured. Most blockchain MCPs focus on read operations — querying balances, fetching block data, checking contract state. If you need to sign and broadcast transactions, you'll likely still handle that outside Switchy using your own wallet tooling.
Why use this instead of calling QuickNode's API directly?
The MCP abstracts away authentication, request formatting, and error handling. Your AI agents can ask natural-language questions like "what's the latest block on Ethereum mainnet" without you writing fetch calls or managing API keys. It's faster for exploratory work and ad-hoc queries, though custom scripts still make sense for high-volume or latency-critical operations.
Who on my team should connect the QuickNode MCP?
Whoever owns your team's QuickNode account or has admin access to it. Once connected, any Switchy workspace member can invoke the MCP in their conversations, but the requests run under the connected account's permissions and rate limits. If your QuickNode plan is shared across projects, coordinate with your team to avoid quota conflicts.