MCP server doesn't start

[galuszkak]

Pre-reqs

• I've searched the current open issues
• I've updated to the latest versions

Extension Version

0.1.7

Gemini CLI Version

0.26.0

Environment

Linux basilisk 6.18.7-200.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Jan 23 16:42:34 UTC 2026 x86_64 GNU/Linux

Current Behavior

when starting Gemini I've got an error:

Tips for getting started:
1. Ask questions, edit files, or run commands.
2. Be specific for the best results.
3. /help for more information.
✕ Error during discovery for MCP server 'bigquery_data_analytics': spawn /home/galuszkak/.gemini/extensions/bigquery-data-analytics/toolbox ENOENT

Expected Behavior

MCP Server starts from extension and I can use it.

Steps to reproduce?

Install Gemini-CLI 0.26.0

Install extension:

gemini extensions install https://github.com/gemini-cli-extensions/bigquery-data-analytics

Additional Details

It worked on previous version of extension and Gemini.

[averikitsch]

Hi @galuszkak, can you run gemini --debug and share the error message? Thanks!

[averikitsch]

Hi @galuszkak please update to the latest versions of Gemini CLI and the extension. Let us know if you continue to experience issues.

[pentium10]

It happens me randomly multiple times per day. I have everything updated to the latest version as we speek. I have 4 other MCPs and they work.

 Debug Console (F12 to close)                                                                                                                                                                                                                                                 │
│                                                                                                                                                                                                                                                                              │
│ ℹ  Loaded cached credentials.                                                                                                                                                                                                                                                │
│                                                                                                                                                                                                                                                                              │
│ ℹ  Detected terminal background color: #012456                                                                                                                                                                                                                               │
│                                                                                                                                                                                                                                                                              │
│ ℹ  Loading extension: bigquery-data-analytics                                                                                                                                                                                                                                │
│ ⚠  [Feedback Details for "Error during discovery for MCP server 'bigquery_data_analytics': MCP error -32000: Connection closed"] McpError: MCP error -32000: Connection closed                                                                                               │
│        at McpError.fromError (file:///C:/Users/user/AppData/Roaming/npm/node_modules/@google/gemini-cli/node_modules/@modelcontextprotocol/sdk/dist/esm/types.js:2035:16)                                                                                                   │
│        at Client._onclose (file:///C:/Users/user/AppData/Roaming/npm/node_modules/@google/gemini-cli/node_modules/@modelcontextprotocol/sdk/dist/esm/shared/protocol.js:259:32)                                                                                             │
│        at _transport.onclose (file:///C:/Users/user/AppData/Roaming/npm/node_modules/@google/gemini-cli/node_modules/@modelcontextprotocol/sdk/dist/esm/shared/protocol.js:223:18)                                                                                          │
│        at ChildProcess.<anonymous> (file:///C:/Users/user/AppData/Roaming/npm/node_modules/@google/gemini-cli/node_modules/@modelcontextprotocol/sdk/dist/esm/client/stdio.js:85:31)                                                                                        │
│        at ChildProcess.emit (node:events:508:28)                                                                                                                                                                                                                             │
│        at cp.emit (C:\Users\user\AppData\Roaming\npm\node_modules\@google\gemini-cli\node_modules\cross-spawn\lib\enoent.js:34:29)                                                                                                                                          │
│        at maybeClose (node:internal/child_process:1101:16)                                                                                                                                                                                                                   │
│        at ChildProcess._handle.onexit (node:internal/child_process:305:5) {                                                                                                                                                                                                  │
│      code: -32000,                                                                                                                                                                                                                                                           │
│      data: undefined                                                                                                                                                                                                                                                         │
│    }                                                                                                                                                                                                                                                                         │
│ ℹ  Authenticated via "oauth-personal".                                    

I can add that after gemini cli starts with restart it does work. So only happens at initial launch.

/extensions restart bigquery-data-analytics
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄

ℹ Restarting 1 extension...

  1 extension restarted successfully.

[averikitsch]

Hi @pentium10 , do you see any logs like:

│ 🔍 [DEBUG] [MCP STDERR (bigquery_data_analytics)]:  2026-02-24T14:06:58.401703-08:00 ERROR "unable to parse tool file at \"/Users/USER/.gemini/extensions/bigquery-data-analytics/tools.yaml\": error parsing │
│    environment variables: environment variable not found: \"BIGQUERY_PROJECT\""    

Where do you have your env vars/setting set?

[pentium10]

no I don't get your referenced errors
extensions tools.yaml has a section like:

sources:
  bigquery-source:
    kind: "bigquery"
    project: ${BIGQUERY_PROJECT}
    location: ${BIGQUERY_LOCATION:}
    useClientOAuth: ${BIGQUERY_USE_CLIENT_OAUTH:false}

I keep my BIGQUERY_PROJECT in project folders
eg:

projectA/.gemini/.env
projectB/.gemini/.env

this is picked up nicely by Gemini CLI ecosystem, and your extension picks it up as well, when does start.

if you need my opinion, maybe extension starts too soon and hence some other process didn't yet set these variables for the extension to be ready and used. Based on the questions you put I assume gemini CLI core does load them as .env and exposes to extensions as well.

[averikitsch]

The Gemini CLI team is working on fixing this issue of loading the .env (via the settings is currently broken for User settings but should be working for Workspace settings). I recommend downgrading to an older version for now.

[averikitsch]

This issue should be fixed in Gemini CLI v0.31.0+. Let us know if you continue to experience any issues.