Base44
Build and edit Base44 apps from an AI assistant, and query data your app's users submit.
Create endpoints, set rate limits, manage security rules and read billing across 80+ chains.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The QuickNode MCP server connects a QuickNode account to Claude, ChatGPT and any MCP-compatible agent. It does not read blockchains. Its 19 tools administer the infrastructure that reads them — creating and archiving RPC endpoints, setting rate limits, managing security rules, and reading logs, metrics and billing. Sign-in is OAuth, and you pick an Admin or Viewer role.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Yes, for the write half. QuickNode states the Admin API that the MCP server runs on is available to accounts on paid plans, and the connector translates every tool into an Admin API call. QuickNode's pricing page lists a free trial of 10M credits at 15 requests per second, then Build at $34 per month billed annually.
No, not through this connector. The Admin API operation behind delete-endpoint is documented as archiving an endpoint rather than erasing it, and QuickNode's own CLI names the same action qn endpoint archive. That is a recoverable state, not a permanent erase. Anything still pointing at the endpoint URL will nonetheless stop working.
Pick the Viewer role when you authorise. QuickNode makes you choose an API key role during the OAuth flow, and documents Viewer as read-only — it can list endpoints and read metrics, logs, usage and billing, but cannot create, modify or delete anything. Admin grants full write access instead.
Remove the server from your client and add it again. QuickNode states the role is fixed to the API key created during authorisation, so there is no in-place downgrade — you re-run the OAuth flow and pick the other role. QuickNode's guidance is to choose Viewer unless the assistant genuinely needs to make changes.
Yes. QuickNode documents passing an API key as a bearer token in the Authorization header, which the server accepts in place of the OAuth flow. Generate the key from the QuickNode dashboard and assign it a role; QuickNode states that role determines the server's permissions exactly as the OAuth choice does.
Not as a per-endpoint charge that QuickNode publishes. QuickNode's pricing page meters plans by API credits and requests per second rather than by endpoint count, so a new endpoint draws on the same plan allowance. QuickNode publishes no per-endpoint fee, and we found no documented cap on how many an Admin-role assistant may create.
Not by itself. QuickNode documents endpoint rate limits as overrides beneath your plan's ceiling, where -1 means no override is set, so raising one removes a self-imposed cap rather than buying capacity. Actual spend still follows credits consumed, and lifting a cap lets real traffic consume more of your plan allowance.
.md suffix) · retrieved 2026-08-18robots.txt — https://www.quicknode.com/robots.txt (fetched 2026-08-18). Blanket Allow: /, and Content-Signal: ai-train=no, search=yes, ai-input=yes — QuickNode expressly permits AI synthesis of this content and refuses training use, which we honour · retrieved 2026-08-18https://mcp.quicknode.com/.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server, both HTTP 200 (2026-08-18) · retrieved 2026-08-18initialize — HTTP 401 with a www-authenticate Bearer challenge (2026-08-18) · retrieved 2026-08-18Connect QuickNode once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.