Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Snowflake MCP not connecting [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18147•Fetched 2026-04-17 08:32:09
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Author
boyd-seanboyd-sean
Participants
boyd-seanboyd-seangithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×5unlabeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.409.61251

What subscription do you have?

Enterprise

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex Desktop is failing to register a valid remote Snowflake MCP server as an available tool, even though the MCP endpoint itself is working.

Environment:

  • Codex Desktop on Windows
  • MCP configured in local ~/.codex/config.toml
  • Remote Snowflake MCP endpoint uses bearer token auth via env var
  • Snowflake MCP server is created successfully and exposes a tool named sql_exec_tool

The Snowflake MCP endpoint responds successfully from PowerShell using the same URL and PAT, and Codex can read the local MCP config file, and verify that the PAT is present in the environment.

I can also verify from the MCP Servers section that Codex reads the config file, and correctly assigns the bearer_token_env_var. But inside a thread, the MCP tool never becomes available to the model:

  • list_mcp_resources returns no resources.
  • list_mcp_resource_templates returns no templates.
  • The expected tool sql_exec_tool is not present in the session toolset.
  • Inspecting Codex local state shows the thread only has built-in dynamic tools and no Snowflake MCP tool registration at all.

What steps can reproduce the bug?

Codex Desktop on Windows reads a valid Snowflake MCP configuration and sees the bearer token env var, but never registers the remote MCP tool into the session. The Snowflake MCP endpoint works outside Codex, yet inside Codex the tool sql_exec_tool is unavailable and MCP discovery is empty.

Config snippet:

[mcp_servers.snowflake] url = "<url>" bearer_token_env_var = "<pat_env_name>" enabled = true required = false startup_timeout_sec = 20 tool_timeout_sec = 120 enabled_tools = ["sql_exec_tool"]

What is the expected behavior?

After Codex Desktop starts and loads the MCP config, it should connect to the Snowflake MCP endpoint, discover the published tools, and register sql_exec_tool as an available tool in the session. I should be able to call the MCP tool directly and return the Snowflake result, instead of saying the tool is unavailable.

Additional information

/

extent analysis

TL;DR

The issue is likely due to Codex Desktop failing to register the Snowflake MCP tool, despite successful configuration and endpoint connectivity, and a workaround may involve verifying the MCP configuration and environment variables.

Guidance

  • Verify that the bearer_token_env_var is correctly set in the environment and matches the one used in the MCP configuration.
  • Check the Codex Desktop logs for any errors or warnings related to MCP tool registration or authentication.
  • Ensure that the sql_exec_tool is correctly published and exposed by the Snowflake MCP server.
  • Review the MCP configuration file (config.toml) for any typos or incorrect settings, especially the url and bearer_token_env_var fields.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be related to the specific version of Codex Desktop (26.409.61251) or the Windows platform, and further investigation may be required to determine the root cause.

Recommendation

Apply workaround: Verify the MCP configuration and environment variables to ensure correct setup and authentication. This is recommended as the issue seems to be related to the registration of the MCP tool, and verifying the configuration and environment variables may help resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#authentication issue#prompt issue#agent setup#task chaining#parallel task

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Snowflake MCP not connecting [1 comments, 2 participants]