Connect your AI

Connect any developer tool.

Every tool on this section's other pages is an instance of one pattern: a server spoken over streamable HTTP, authenticated with a Bearer header. The protocol behind this is MCP (Model Context Protocol), so any MCP-compatible client can connect. If your client isn't listed by name, this page is enough to connect it.

One connection address #

Every client, every mode, the same URL:

https://app.solosearcher.com/mcp

The pattern #

  1. Create an API key in Settings → Connections → API keys, grant only the access the tool needs, and copy it right away — it is shown once.
  2. Register the server wherever your client keeps its configuration. Most JSON-configured clients accept this shape:
    {
      "mcpServers": {
        "solosearcher": {
          "type": "http",
          "url": "https://app.solosearcher.com/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_API_KEY"
          }
        }
      }
    }
  3. Ask the tool to list SoloSearcher's tools to confirm the server answered.

Clients that can open a browser may offer OAuth sign-in instead of a key. A client running on your own machine — a CLI, a local editor plugin — that completes sign-in on a loopback callback needs no configuration beyond the URL. A browser-hosted client can't sign in yet: SoloSearcher accepts authorization-code callbacks only from Claude's hosts or a loopback address, so anything else is refused at that step — see the ChatGPT page for a worked example of where it stops. The Gemini CLI and Claude Code pages are worked examples of each route.

Choose what the tool can do #

Every connection is scoped when you approve it. Read-only lets the tool 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 the tool for something you actually want to know:

Which three of my tracked companies best fit my buyer profile, and why?

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.

Key hygiene #

A key is a password: scope it to the least access that does the job, keep it in an environment variable or secret store rather than in shared config, use one key per tool so revoking one doesn't break the others, and revoke any key you no longer use. API keys & access covers scoping, revocation, and the audit trail in full.

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.