Snowflake MCP not connecting

Open 💬 1 comment Opened Apr 16, 2026 by boyd-sean

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

/

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗