From 0e8a46f91d7e1b82e96927a73c1d6f02ff5243a9 Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Fri, 7 Aug 2026 17:47:19 +0530 Subject: [PATCH] docs: drop the removed MCP query-token auth guidance Commit 2bfb9b3b removed the "Authentication via query token (less secure)" section from docs/mcp/mcp-server.mdx as an incorrect auth method, but left two inbound references to it in place. build-a-trading-agent.mdx still linked to the deleted anchor, which `npm run build` flagged as a broken anchor. Re-anchoring alone would have been wrong: the surrounding sentence told users to append `?token=YOUR_TOKEN` for headless servers, i.e. it repeated the same method that was just removed as incorrect. Both now describe the OAuth 2.1 flow the server actually documents, and the link points at the "First Connection and Permissions" section. cursor.mdx had no link, so the build never flagged it, but its FAQ asserted the same `?token=YOUR_TOKEN` method. Fixed alongside so the incorrect instruction is gone from the MCP docs entirely. Co-Authored-By: Claude Opus 5 --- docs/mcp/build-a-trading-agent.mdx | 2 +- docs/mcp/cursor.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/mcp/build-a-trading-agent.mdx b/docs/mcp/build-a-trading-agent.mdx index 6782ce1a..2e0bd471 100644 --- a/docs/mcp/build-a-trading-agent.mdx +++ b/docs/mcp/build-a-trading-agent.mdx @@ -26,7 +26,7 @@ Pick your runtime: | Cursor | `.cursor/mcp.json` with `mcp-remote` → `https://mcp.bitquery.io/mcp` | | Claude Code | `claude mcp add bitquery -- npx -y mcp-remote https://mcp.bitquery.io/mcp` | -Sign in with a [Bitquery account](https://account.bitquery.io/) on first tool call. For headless servers, append `?token=YOUR_TOKEN` (see [MCP overview](/docs/mcp/mcp-server/#authentication-via-query-token-less-secure)). +Sign in with a [Bitquery account](https://account.bitquery.io/) on first tool call. The client opens a browser once for OAuth 2.1, then caches and refreshes the token for you (see [MCP overview](/docs/mcp/mcp-server/#first-connection-and-permissions)). ## Step 2 — Discovery loop diff --git a/docs/mcp/cursor.mdx b/docs/mcp/cursor.mdx index 3d1cf0db..63836f1b 100644 --- a/docs/mcp/cursor.mdx +++ b/docs/mcp/cursor.mdx @@ -45,6 +45,6 @@ More detail: [MCP server overview](/docs/mcp/mcp-server/). items={[ { q: "How do I add Bitquery MCP to Cursor?", a: "Add https://mcp.bitquery.io in Cursor MCP settings, or use mcp-remote in .cursor/mcp.json as shown on this page." }, { q: "Which chains can I query through MCP?", a: "Solana, Ethereum, BSC, Base, Arbitrum, Optimism, Polygon, and Tron — ask in plain English, no GraphQL required." }, - { q: "Can I use an API token instead of OAuth?", a: "Yes for headless setups — append ?token=YOUR_TOKEN to the MCP URL. OAuth is safer for daily interactive use." }, + { q: "Can I use an API token instead of OAuth?", a: "No. The Bitquery MCP server authenticates with OAuth 2.1 — Cursor opens a browser once on the first tool call, then caches and refreshes the token for you." }, ]} />