Documentation
Connect LithicBlue to Gemini
Before you start
What you need
A LithicBlue account on a paid plan, the Gemini CLI installed, and your MCP endpoint, which is your regional URL with /api/mcp/mcp appended (e.g. https://eu.lithicblue.com/api/mcp/mcp). See the MCP connector page for your exact URL.
Add the server
- Open your Gemini CLI settings at
~/.gemini/settings.json. - Add LithicBlue under
mcpServerswith your endpoint ashttpUrland OAuth enabled:
{
"mcpServers": {
"lithicblue": {
"httpUrl": "https://eu.lithicblue.com/api/mcp/mcp",
"oauth": { "enabled": true }
}
}
}- Authenticate with
/mcp auth lithicblue; this opens your browser to sign in to LithicBlue, which then shows an Approve access screen naming the connector, the host it connects back to, and what it will be able to do. Approve it, and tokens are stored and refreshed by the CLI. - Ask Gemini to list your LithicBlue projects to confirm it's working.
OAuth is auto-discovered
With oauth.enabled set, the CLI uses dynamic discovery to read LithicBlue's OAuth configuration automatically, with no client ID or secret to paste.
How to track your projects in Gemini
Ask Gemini to list your LithicBlue projects, then summarise scope fulfilment and the open data gaps on any project. It reads your scope analysis and data-gaps directly, so you can check where a piece of work stands from the command line.
How to verify AI outputs with Gemini
Ask Gemini to read a deliverable's claims and tell you which are verified, contradicted or still unverified against your sources, and to author new claim highlights anchored to the exact passage. This is how you fact-check AI-generated and human-written deliverables with traceable evidence. The full tool list and example prompts are on the MCP connector page.