Gemini CLI Oxford Ledge ol_glossary_term

How to: Gemini CLI Oxford Ledge ol_glossary_term

client:Gemini CLI transport:streamable-http tool:ol_glossary_term

Add Oxford Ledge to Gemini CLI

01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "oxford-ledge": {
      "httpUrl": "https://www.oxfordledge.com/mcp"
    }
  }
}

02
Save the file and restart Gemini CLI.
03
Ask for something ol_glossary_term does. Gemini CLI lists the server's tools on connect and calls ol_glossary_term itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that Oxford Ledge's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Set these first

Oxford Ledge will not start until these are set, so ol_glossary_term never becomes available.

OXFORD_LEDGE_URL
OXFORD_LEDGE_API_KEY
FRED_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 4 October 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Oxford Ledge MCP server