# Cloudflare MCP server reauthorization issue in Codex: CLI workaround **URL:** \ **Category:** Codex\ **Tags:** codex, mcp, codex-cli, cloudflare, codex-app\ **Created:** [May 31, 2026, 5:30pm UTC](https://community.openai.com/t/cloudflare-mcp-server-reauthorization-issue-in-codex-cli-workaround/1382153 "2026-05-31T17:30:56Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![sergeliatko](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/sergeliatko/32/816_2.png) [@sergeliatko](https://community.openai.com/u/sergeliatko)\ **Post date:** [May 31, 2026, 5:30pm UTC](https://community.openai.com/t/cloudflare-mcp-server-reauthorization-issue-in-codex-cli-workaround/1382153/1 "2026-05-31T17:30:56Z")
I ran into an issue where the Cloudflare MCP server suddenly could not be reconnected in Codex. I could not find a UI flow inside the Codex app to reauthorize the Cloudflare MCP server, so I solved it from the CLI. This worked: ```auto codex mcp logout cloudflare-api codex mcp login cloudflare-api ``` After running the login command, Codex gave me a URL where I could log in to my Cloudflare account, select permissions, and authorize Codex again. Then I confirmed the connection with: ```auto codex mcp list ``` That showed the Cloudflare MCP server connected correctly. So the reauthorization flow works through the CLI, but I could not find the equivalent reauthorization path in the Codex app UI. Posting this in case it helps others who run into the same issue. ---
**Author:** ![PaulBellow](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/paulbellow/32/597962_2.png) [@PaulBellow](https://community.openai.com/u/PaulBellow)\ **Post date:** [May 31, 2026, 5:38pm UTC](https://community.openai.com/t/cloudflare-mcp-server-reauthorization-issue-in-codex-cli-workaround/1382153/2 "2026-05-31T17:38:25Z")
As someone who was saved more than once by an ancient forum post when coding back in the before times, this is very much appreciated. Hope it helps save someone a bit of time. ---
**Author:** ![sergeliatko](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/sergeliatko/32/816_2.png) [@sergeliatko](https://community.openai.com/u/sergeliatko)\ **Post date:** [May 31, 2026, 5:58pm UTC](https://community.openai.com/t/cloudflare-mcp-server-reauthorization-issue-in-codex-cli-workaround/1382153/3 "2026-05-31T17:58:03Z")
> [@PaulBellow](#): > > in the before times Love that, Paul. Time is flying fast now, you remember davinci? ---
**Author:** ![PaulBellow](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/paulbellow/32/597962_2.png) [@PaulBellow](https://community.openai.com/u/PaulBellow)\ **Post date:** [May 31, 2026, 6:04pm UTC](https://community.openai.com/t/cloudflare-mcp-server-reauthorization-issue-in-codex-cli-workaround/1382153/4 "2026-05-31T18:04:25Z")
I started with GPT-2 like many of us. I was talking even further back when you had to Google for answers! Haha. Seriously, though, I really like that this place is an old school forum in today’s day and age. Lots of human value here, imho. ---
**Author:** ![sergeliatko](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/sergeliatko/32/816_2.png) [@sergeliatko](https://community.openai.com/u/sergeliatko)\ **Post date:** [May 31, 2026, 6:06pm UTC](https://community.openai.com/t/cloudflare-mcp-server-reauthorization-issue-in-codex-cli-workaround/1382153/5 "2026-05-31T18:06:51Z")
> [@PaulBellow](#): > > when you had to Google for answers! You mean like “freeze the google with an otherwise not very complicated question”? Hopefully they have AI now to point the direction (often blurry but still something…) ---
**Author:** ![PaulBellow](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/paulbellow/32/597962_2.png) [@PaulBellow](https://community.openai.com/u/PaulBellow)\ **Post date:** [May 31, 2026, 6:20pm UTC](https://community.openai.com/t/cloudflare-mcp-server-reauthorization-issue-in-codex-cli-workaround/1382153/6 "2026-05-31T18:20:47Z")
Well, it was like you would search for an error code or what-not and usually on some forum (or that “Answers” site i can’t think of the name of at the moment… StackOverchange?) But yeah, the AI is trained on all those Google-able answers, so it’s a bit better these days. Now just imagine pre-internet! Haha. It’s kinda crazy how far we’ve come over the last 100 years even… ---
**Author:** ![sergeliatko](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/sergeliatko/32/816_2.png) [@sergeliatko](https://community.openai.com/u/sergeliatko)\ **Post date:** [May 31, 2026, 7:44pm UTC](https://community.openai.com/t/cloudflare-mcp-server-reauthorization-issue-in-codex-cli-workaround/1382153/7 "2026-05-31T19:44:37Z")
No need to imagine. I remember. 😂 ---
**Author:** ![sergeliatko](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/sergeliatko/32/816_2.png) [@sergeliatko](https://community.openai.com/u/sergeliatko)\ **Post date:** [June 3, 2026, 7:00am UTC](https://community.openai.com/t/cloudflare-mcp-server-reauthorization-issue-in-codex-cli-workaround/1382153/8 "2026-06-03T07:00:55Z")
0.136.0 fixed the thing by instructing me to run: codex mcp login cloudflare-api ---
**Author:** ![sergeliatko](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/sergeliatko/32/816_2.png) [@sergeliatko](https://community.openai.com/u/sergeliatko)\ **Post date:** [June 5, 2026, 7:52pm UTC](https://community.openai.com/t/cloudflare-mcp-server-reauthorization-issue-in-codex-cli-workaround/1382153/9 "2026-06-05T19:52:31Z")
Well, maybe to fast marked as solved. Today had to re-login on almost every new terminal session. I didn’t not launch the codex to debug this, but I suspect there is some misconfiguration with how the refresh token is stored.