Gemini CLI
What you get
Connect Gemini CLI to Graphory and your terminal AI gains the same business memory every other AI you use can read and write. Scripted briefings, release notes, and incident summaries all share continuous context across every agent and every LLM in your stack.
Graphory-specific setup
These are the pieces Graphory controls. Drop them into Gemini CLI's settings file using the format Google currently documents.
- MCP URL:
https://api.graphory.io/mcp - Auth header:
Authorization: Bearer gs_ak_YOUR_KEY - Get your key: app.graphory.io/settings/api-keys
Example config block, for reference. Gemini CLI currently uses httpUrl for remote MCP servers:
{
"mcpServers": {
"graphory": {
"httpUrl": "https://api.graphory.io/mcp",
"headers": {
"Authorization": "Bearer gs_ak_YOUR_KEY"
}
}
}
}
Once connected, Gemini can call Graphory's MCP tools to search your graph, pull timelines, and write new findings back.
Vendor setup docs
Gemini CLI's MCP config shape has shifted across releases (different versions have used httpUrl, url, or a transport key). We deliberately do not mirror Google's docs here, because they drift. For the current, authoritative setup steps, go straight to the source:
Follow their latest instructions and plug in the Graphory URL, header, and API key from above.