Docs / Connect Mindola

Gemini CLI

Connect the Gemini CLI to Mindola's hosted MCP server and create a lens from your terminal.

Mindola’s MCP server is hosted and remote. There is nothing to download or run locally: you add one URL to the Gemini CLI settings, and it gains tools for building a lens. A lens is your public AI page at one shareable link, where anyone can ask questions and get answers grounded only in your material, with citations.

What you get

Once connected, the Gemini CLI can call three tools:

  • create_digital_twin_lens creates a new lens from a profile you confirm in the conversation.
  • add_lens_knowledge adds text or link items to an unclaimed lens so it can answer from them.
  • get_lens_status reports whether the lens is claimed and how much of its knowledge is ready.

No account or API key is needed to start. Anonymous creation returns an unclaimed lens that is live immediately at its share link, plus a claim URL. Open the claim URL and sign up for free to make the lens yours. Unclaimed lenses expire after 30 days. The full tool reference is at MCP server.

Requirements

  • A recent version of the Gemini CLI with MCP support.
  • Nothing else: no Mindola account, no API key, no local server process.

Install

Add this to the mcpServers object in ~/.gemini/settings.json:

{
  "mcpServers": {
    "mindola": {
      "httpUrl": "https://app.mindola.ai/mcp/lens"
    }
  }
}

Note that the Gemini CLI uses the key httpUrl, not url.

Verify it works

Start a new Gemini CLI session and ask: “What Mindola tools do you have?” The assistant should name exactly three tools: create_digital_twin_lens, add_lens_knowledge, and get_lens_status.

Try this

Ask the Gemini CLI:

Create a Mindola lens about my newsletter and add my three latest posts as links.

It will build a profile with you, ask you to confirm it, call the create tool, add the posts as url items, and give you the share link and the claim link. You can try what a finished lens feels like at the Charles Darwin demo.

If it does not work

If the server does not appear or tool calls fail, see Troubleshooting. For other clients and the general setup pattern, see the connections overview.