QuickNode connects AI agents to blockchain infrastructure, enabling read-only on-chain queries across supported networks, endpoint creation and management, RPC usage analytics, security configuration, rate-limit controls, log inspection, and billing review.
Visual Studio Code runs MCP servers for Copilot Chat in agent mode, so the model can use external tools while it works on your code.
This guide connects QuickNode MCP to VS Code through MewCP, so VS Code can use QuickNode MCP's 22 tools, like list-endpoints, get-endpoint and create-endpoint, without your QuickNode MCP credentials ever reaching the app.
QuickNode MCP signs in through managed OAuth. MewCP stores the token encrypted, refreshes it before it expires and injects it only at call time. Your agent never holds it, so it can never leak it.
More apps
Manage repositories, pull requests, issues, branches and development workflows on GitHub. Automate software delivery and collaborate across engineering projects.
Connect to external APIs, webhooks and internet services through standard HTTP requests. Build integrations with virtually any platform that exposes a web-based interface.
Access cryptocurrency market data, portfolios and trading operations on Binance. Monitor assets, retrieve market information and automate crypto trading workflows.
Coinfuty provides cryptocurrency market intelligence for tracking digital asset prices, analyzing market trends, monitoring trading activity, and researching crypto opportunities to support data-driven investment decisions.
Other clients
QuickNode MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact QuickNode MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
A browser window opens the first time the client connects. Sign in and approve access. No API key needed.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
Get web3 Quicknode endpoints for the user, this is a list of all the endpoints that the user has created across all chains and networks. Supports pagination via limit and offset parameters
Get a specific web3 Quicknode endpoint details by id
Create a new web3 RPC endpoint for a given chain and network under user's Quicknode account. This can error if the chain and network combination is not supported or if the user has reached their endpoint limit, in which case the user should try a different chain and network combination (can request list-chains tool for information on supported chains) or delete an existing endpoint
Delete a Quicknode endpoint by its ID. This will make the endpoint inactive. THIS IS A DESTRUCTIVE ACTION
List the request/response logs for a specific Quicknode endpoint
Get detailed request and response information for a specific log entry. This provides the raw request payload and full response that were logged for a particular request
Get metrics for a specific Quicknode endpoint. Supports various metrics like method calls, response status, and response times over different time periods
Update the general rate limits (RPS, RPM, RPD) for a Quicknode endpoint. Pass a positive integer to set a user override for that bucket, or pass -1 to remove an existing user override and fall back to the plan default; -1 on a bucket that has no override is a no-op and is reported in the `skipped` array. Each plan has a maximum rate limit per bucket; if you request a value above that maximum, the request still succeeds but the plan's maximum is applied for that bucket (e.g. setting rps=1000 on a plan with a 500 rps ceiling results in 500 rps enforced). Available to Build plans and higher (Discover/Free are read-only here). Returns a `before` and `after` snapshot of the enforced rate-limit rows so the caller can see what changed.
List all method rate limits for a specific Quicknode endpoint
Create a new method-specific rate limiter for a Quicknode endpoint
Update an existing method-specific rate limit for a Quicknode endpoint
Delete a method-specific rate limit from a Quicknode endpoint. THIS IS A DESTRUCTIVE ACTION
Update security options for a specific Quicknode endpoint
List all security options and rules for a Quicknode endpoint. Shows which security features are enabled/disabled and all configured rules (ip, jwt, referrer, domain_mask, token) with their rule IDs.
Create a security rule for a Quicknode endpoint. Supports types: ip, jwt, referrer, domain_mask, token. Provide the type-specific fields alongside the type parameter.
Delete a security rule from a Quicknode endpoint. THIS IS A DESTRUCTIVE ACTION. Use the list-endpoint-security tool first to find the rule type and rule_id.
Get the usage data for the user's Quicknode RPC account. Use breakdown_by to get usage by endpoint, method, or chain. The start_time and end_time parameters are ISO 8601 date strings.
Get billing data for the user's Quicknode account. Use type to get invoices or payments.
List all chains and network slugs supported by Quicknode.
Enable account-level Quicknode Tooling Access. This provisions an account-level shared RPC endpoint for use by Quicknode developer tools and caches its short-lived access credential.
Disable account-level Quicknode Tooling Access.
Call an allowed read-only JSON-RPC method through authenticated Quicknode Tooling Access. Use the network slug from list-chains; call list-chains first if it is unknown.
