Skip to content

Conversation

@diverHansun
Copy link

Summary

This PR updates the README to include installation instructions for running OpenAI Codex CLI with the Context7 MCP server on Windows 11.

Changes

  • Added a collapsible <details> section with step-by-step installation instructions.
  • Documented the required config.toml configuration.
  • Provided clear guidance for avoiding the request timed out error.

Motivation

Several Windows 11 users reported issues when running the Codex CLI with Context7 MCP server.
This documentation update provides a tested fix to help users configure and run the CLI smoothly.

Related Issue

Fixes #575 #658

README.md Outdated
"stdio"
]

[mcp_servers.context7.env]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what are these for?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the settings for context7 in codex : config.toml

@enesgules
Copy link
Collaborator

Hey @diverHansun thanks for the PR, could you put this below the existing Codex docs. this is only for windows right? you can mention that in the readme as well

@diverHansun
Copy link
Author

Hey @diverHansun thanks for the PR, could you put this below the existing Codex docs. this is only for windows right? you can mention that in the readme as well

I see ,I will add some in
image

@diverHansun
Copy link
Author

check please!

@wbdb
Copy link

wbdb commented Sep 17, 2025

I would also recommend adding the following step, since you are no longer using npx:

npm install -g @upstash/context7-mcp

Edit: Found a better way without having to update it manually:

[mcp_servers.context7]
command = "cmd"
args = [
    "/c",
    "npx",
    "-y",
    "@upstash/context7-mcp",
    "--api-key",
    "YOUR_API_KEY",
]
env = { SystemRoot="C:\\Windows" }
startup_timeout_ms = 20_000

This works for me with Codex 0.38.0 and Windows 11 Pro 24H2.

@enesgules
Copy link
Collaborator

hey @wbdb what is that startup_timeout_ms field? is that related to the context7 mcp server? this seems like a way cleaner setup tbh

README.md Outdated
]

[mcp_servers.context7.env]
CONTEXT7_MCP_URL = "https://mcp.context7.com/mcp"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this isn't how we setup the the mcp url or the api key in our server, you should just add the api key as an argument and remove the mcp url

@wbdb
Copy link

wbdb commented Sep 18, 2025

hey @wbdb what is that startup_timeout_ms field? is that related to the context7 mcp server? this seems like a way cleaner setup tbh

Codex CLI specific instruction (openai/codex#3006), as npx takes longer than 10 seconds to start up on Windows and may therefore fail. However, I and others also need the system ENV for it to work on my system.

@enesgules
Copy link
Collaborator

Oh thank you @wbdb

What do you think @diverHansun could you update the pr to include @wbdb 's config if it works for you too?

@diverHansun
Copy link
Author

I tried @wbdb ‘s config,it also works. I've updated the pr and include this config.

@diverHansun diverHansun marked this pull request as draft September 21, 2025 09:46
@enesgules enesgules marked this pull request as ready for review September 22, 2025 07:13
@enesgules
Copy link
Collaborator

This looks good to me @diverHansun was there something else you wanted to update? If not I'm going to merge. Thank you so much for the contribution!

@diverHansun
Copy link
Author

Thanks @enesgules ! No further changes from my side, please go ahead and merge. 🙌

@enesgules enesgules merged commit f791d63 into upstash:master Sep 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Codex CLI on Windows 11: MCP server (Context7) fails with “request timed out” despite fast local startup

3 participants