Terminal-native context
Pages arrive as plain text with their instruction blocks — ideal for a CLI agent.
Google · Coding agents
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.
Why pair them
Pages arrive as plain text with their instruction blocks — ideal for a CLI agent.
Use .gemini/settings.json in a repo or ~/.gemini/settings.json for everything.
Only published pages, and every call recorded in the agent’s request log.
Setup
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.
Gemini CLI uses httpUrl for Streamable HTTP servers. Add the Authorization header alongside it.
{
"mcpServers": {
"memrio": {
"httpUrl": "https://memrio.ai/api/mcp/acme",
"headers": {
"Authorization": "Bearer mr_live_8f3a…"
}
}
}
}Start gemini and run /mcp. memrio should list its tools.
gemini
> /mcpPut the browse-first rule in GEMINI.md so the agent checks the registry before it answers.
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
“Browse the registry for our release checklist and run through it for version 2.4.”
FAQ
Other integrations