Missing account:read blocks Pages access

Aperta
  • Qualcosa non va?
#385 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
44/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
authentication, backend-api-design

Direzione di ricerca

Start by tracing how the Cloudflare API Code Executor checks OAuth permissions and where the missing account:read error is produced. The issue does not identify the relevant files or establish whether this server controls the approval flow, so first determine whether the supported fix belongs in the MCP server or in Cloudflare's app authorization. Done means users can request the required permission through a supported path, or receive accurate approval instructions while preserving existing authorization.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
MCP Client

Other (please specify below)

MCP Client Version

No response

Authentication Type

OAuth

OAuth Scopes (if applicable)

Exact granted scope list unavailable. The managed OAuth connection reports that account:read is missing.

MCP Server Configuration
Grok Bot manages this Cloudflare MCP connection through its installed Cloudflare connector using HTTP transport and OAuth. The actual client configuration and server URL are not exposed through the available connection settings. No configuration JSON is available to attach. The registered desktop is offline, so local configuration files could not be inspected.
Failing Endpoint / Tool

execute (Cloudflare API Code Executor)

Bug Description

The Cloudflare connection in Grok Bot works, but a Pages read request through execute (Cloudflare API Code Executor) fails because account:read is missing. The error says an administrator must approve the permission before signing in again and instructs us not to retry. No supported way to request the missing permission is exposed through the available connection controls.

Steps to Reproduce
  1. Connect Cloudflare in Grok Bot using OAuth.
  2. Confirm the connection is reported as connected.
  3. Attempt a Pages read request through execute (Cloudflare API Code Executor).
  4. Receive the missing account:read permission error.

The failed request has not been retried because the error explicitly instructs us not to retry.

Expected Behavior

The Pages read request succeeds when the necessary permissions are granted. If account:read is missing, the connection provides a supported way to request it while preserving existing authorization, or clear instructions identifying who must approve it and where.

Actual Behavior

The connection reports connected, but the Pages read request is blocked with a missing account:read permission error. The error says another sign-in will not add the permission until an administrator approves it. No supported approval or incremental-consent action is available through the exposed connection controls.

Relevant Logs / Error Output
Cloudflare needs one more permission to Cloudflare API Code Executor. Permission: account:read. The last sign-in came back without it, so signing in again will not add it. An admin must approve this permission for the app in Cloudflare first, then the user signs in again. Tell the user exactly this. Do not retry this call.
Additional Context

The managed connection uses HTTP transport and OAuth. Available tools are docs, search, execute and whoami. The exact MCP client version, raw client configuration and full granted scope list are unavailable.

The failed request has not been retried. Existing authorization has not been revoked or replaced. Please identify the supported way to request account:read while preserving existing permissions, and which administrative approval is needed, if any. The source of the error wording has not been established.

Lingua principale
TypeScript
Stelle
1.1k
Fork
171
Merge medio
1g 2h
PR unite (30g)
60

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudflare/mcp

Tutte le issue di cloudflare/mcp

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.