Skip to main content

Using Gemini CLI with Marrow

Use Gemini CLI when you want a terminal-first Google Gemini agent that can read your synced Marrow data over MCP.

Prerequisites

Step 1: Get Marrow credentials

From AI Hub → AI Platforms:
  • MCP server URL: https://mcp.marrow.ai/mcp/v1
  • Create an MCP key and copy it (shown only once)
See also: MCP overview

Step 2: Add the Marrow MCP server

From your project root:
Replace YOUR_MCP_KEY with your key from AI Platforms.
  • --transport http is required for remote streamable HTTP servers (default is stdio).
  • --scope project writes to .gemini/settings.json; use --scope user for ~/.gemini/settings.json.

Step 3: Reload Gemini CLI

Restart your Gemini CLI session so it loads the new MCP server. You can confirm with:

Step 4: Test the connection

If Gemini CLI returns real data from your synced accounts, you are connected.

Optional: config with an environment variable

To avoid storing the key inline, edit the Marrow entry in settings and reference an env var (supported by Gemini CLI headers interpolation):
Then export MARROW_MCP_KEY in your shell before starting Gemini CLI.

Security

  • Marrow is read-only — it never posts or changes store/ad settings.
  • Prefer env-based keys for shared machines or committed project configs.
  • Rotate or revoke keys from AI Platforms anytime.