Google · Coding agents

Memrio for Gemini CLI

Gemini CLI runs in your terminal and picks up MCP servers from settings.json. Point it at the registry and it can browse your approved pages while it works through a task.

Jump to setup
live
Gemini CLImemrio

Why pair them

01

Terminal-native context

Pages arrive as plain text with their instruction blocks — ideal for a CLI agent.

02

Per-project or global

Use .gemini/settings.json in a repo or ~/.gemini/settings.json for everything.

03

Governed and logged

Only published pages, and every call recorded in the agent’s request log.

Setup

3 steps, about ten minutes.

You need two values from an agent page in Memrio: the workspace MCP URL and an API key. Examples use https://memrio.ai/api/mcp/acme — swap in yours.

Create an agent and key first
  1. 01

    Edit settings.json

    Gemini CLI uses httpUrl for Streamable HTTP servers. Add the Authorization header alongside it.

    ~/.gemini/settings.json
    {
      "mcpServers": {
        "memrio": {
          "httpUrl": "https://memrio.ai/api/mcp/acme",
          "headers": {
            "Authorization": "Bearer mr_live_8f3a…"
          }
        }
      }
    }
  2. 02

    Check the connection

    Start gemini and run /mcp. memrio should list its tools.

    terminal
    gemini
    > /mcp
  3. 03

    Add a standing instruction

    Put the browse-first rule in GEMINI.md so the agent checks the registry before it answers.

    GEMINI.md
    Before answering anything about our company, products, or policies, call `browse` on the memrio server, open the pages whose use-when instructions match, and answer only from those pages. If nothing applies, say so.

Try it

A first prompt for Gemini CLI

Browse the registry for our release checklist and run through it for version 2.4.

FAQ

Gemini CLI and Memrio

Does Memrio need a workspace or page-set header?
No. The API key is scoped to one workspace and one agent page set, so the key alone tells the server what the agent may read. Send only the Authorization header.
Which pages can the agent see?
Only published pages inside the agent page set you configured. Drafts and pages waiting on review are hidden unless you turn on "Read drafts" for a test agent.
Can the agent edit pages?
Only if you enable "Can edit pages" on that agent. It then gets get_page_source, create_page, update_page, and append_to_page. Edits are submitted as versions for human review unless the agent is also allowed to publish.

Other integrations