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 #

Create an API key in Settings → API Keys, grant only the access the tool needs, and copy it right away — it is shown once.

{
  "mcpServers": {
    "solosearcher": {
      "type": "http",
      "url": "https://app.solosearcher.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

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 #

Confirm the connection is live by asking the tool:

List the SoloSearcher tools you can use, then show me the companies I am tracking.

Then put it to work: ask it to run one of the built-in diligence skills — valuation, earnings quality, owner assessment — against a company you're tracking.

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.