SoloSearcher

Connect your AI

Connect Gemini CLI to your search.

The Gemini CLI discovers the sign-in flow from the server itself, so the browser route needs no key at all. A machine that cannot open a browser uses an API key instead.

These steps follow the Gemini CLI's own documentation. We have not connected Gemini to SoloSearcher ourselves, so if a screen or a flag does not match what you see, trust the CLI — and tell us, so we can fix this page.

Browser sign-in #

Gemini CLI discovers the sign-in flow from the server, so there is no key to create or store.

  1. Register the server. --scope user writes it to ~/.gemini/settings.json, so it works from any directory:
    gemini mcp add --scope user --transport http \
  solosearcher https://app.solosearcher.com/mcp
  2. Start gemini, then authorise SoloSearcher:
    /mcp auth solosearcher
  3. Your browser opens SoloSearcher. Sign in, then choose what Gemini is allowed to do — read-only or read-and-write.
  4. Run /mcp to confirm the SoloSearcher tools are listed.

The token is kept in ~/.gemini/mcp-oauth-tokens.json and refreshed automatically. Revoking it in SoloSearcher takes effect immediately.

API key #

For a machine that cannot open a browser — a server, a container, a CI job.

  1. Create an API key in Settings → Connections → API keys and copy it right away — it is shown once.
  2. Register the server with your key in place of YOUR_API_KEY:
    gemini mcp add --scope user --transport http \
  --header "Authorization: Bearer YOUR_API_KEY" \
  solosearcher https://app.solosearcher.com/mcp
  3. Run gemini and use /mcp to confirm the SoloSearcher tools are listed.

That writes the key into ~/.gemini/settings.json in plain text, so treat the file like a password store.

Choose what Gemini can do #

Every connection is scoped when you approve it. Read-only lets Gemini search and read your companies, notes, contacts, and financials. Read-and-write also lets it save its work — finished reports, notes, and updates land on the company record instead of staying in the chat.

A read-only connection can still run any skill; it returns the analysis to you in the conversation rather than storing it. You can revoke access at any time, and every request is recorded in the product audit trail.

First thing to try #

One prerequisite: skills stay locked until you've saved a Buyer Profile — your display name plus at least one of your background, your thesis, or a target range. Two minutes, once. See Buyer Profile for what it unlocks and exactly how to set it. Skills are scored against your criteria, which is why the profile comes first.

Then ask Gemini for something you actually want to know:

Which of my companies have financials on file? Run an earnings quality review on one of them.

With read-and-write access, the result of a skill run saves onto the company record as a report — run it again later and you get a new version next to the old one. On a read-only connection the analysis comes back in the conversation instead.

Troubleshooting #

If SoloSearcher works in one directory and vanishes in another, the server was registered with the CLI's default --scope project, which writes ./.gemini/settings.json. Remove it and register again with --scope user as above.

Read more #

Signed in? The same steps live at Settings → Connections alongside your live connection status. See API keys & access for key mechanics, or head back to Connect your AI for the other tools.