Use BiOS from Gemini CLI

Google terminal coding agent

Works today

The Gemini CLI reads MCP servers from the same mcpServers shape used by Claude and Cursor. One block in settings.json connects it to BiOS.

Before you start

You need a BiOS API key. In your dashboard, open API Keys, click Create API Key, pick a permission preset, and copy the sk_live_ key. It is shown only once.

Node.js 18 or newer must be installed; the server runs with npx, so there is nothing else to install.

Setup

Edit the settings file

Add the server to ~/.gemini/settings.json (create the file if needed). Project-level config in .gemini/settings.json works too:

~/.gemini/settings.json

{
  "mcpServers": {
    "usfbios": {
      "command": "npx",
      "args": ["-y", "@usfbios/mcp-server"],
      "env": {
        "USFBIOS_API_KEY": "sk_live_your_api_key"
      }
    }
  }
}

2
Restart and check
Start a new gemini session and type /mcp. The usfbios server should be listed with its tools.
3
Run a workflow
Ask for a task in plain English, for example: "Import databricks/dolly-15k from HuggingFace into BiOS and start a LoRA fine-tune on Mistral 7B."

Check that it works

The /mcp command lists usfbios with its tool count.
Ask "What is my BiOS wallet balance?" and confirm the get_wallet_balance call.

Try these prompts

“Search for Llama models under 13B parameters and recommend a GPU for LoRA fine-tuning”

“Upload ~/data/support-qa.jsonl and start an SFT job on Llama 3.1 8B with LoRA”

“What is the status of my running training jobs? Show the loss curve for the latest one”

“Deploy my finished fine-tune and give me the endpoint URL”

Your assistant has 38 BiOS tools in total. The tool reference documents each one.

Troubleshooting

The server never starts, or logs show "npx: command not found"

The MCP server runs on Node.js. Install Node 18 or newer from nodejs.org, restart your client, and try again. Run npx -y @usfbios/mcp-server in a terminal to confirm it starts (it waits for input; press Ctrl+C to exit).

Tools appear but every call fails with an authentication error

Check that USFBIOS_API_KEY is set to a key that starts with sk_live_ and has not expired. Keys are shown only once at creation, so if in doubt create a fresh one under Dashboard, then API Keys.

A tool call fails with a permission error

Your key may be scoped too narrowly. Ask the assistant to call introspect_api_key to see exactly which scopes the key has, then create a key with the preset you need (Read Only, Training, or Full Access).