Connect SiteSeeker to GitHub Copilot CLI

Add SiteSeeker to GitHub Copilot CLI with one command and find leads from your terminal. Results arrive as text.

By GitHubTerminalResults as text

Before you start

  • GitHub Copilot CLI installed and signed in.
  • On Copilot Business and Enterprise, an admin must allow MCP servers.
  • A SiteSeeker agency plan. Searches spend its search credits, and hosting-only accounts cannot search.

Connect SiteSeeker

  1. Add the server from your terminal:

    copilot mcp add --transport http siteseeker https://siteseeker.ai/mcp

  2. Start Copilot CLI and sign in to SiteSeeker when it asks. Run /mcp auth to sign in again later.

Note. On Copilot Business and Enterprise, an admin must allow MCP servers in Copilot.

GitHub Copilot CLI’s own setup guide

Check it works

Start Copilot CLI and ask:

Your first search

Find roofers in Austin, TX with no website.

SiteSeeker answers with a list of scored leads, each with its rating, address and phone number. The search uses 1 search credit.

Troubleshooting

  • The sign-in window never opened, or it timed out

    Run /mcp auth inside Copilot CLI and pick siteseeker.

  • Copilot says MCP servers are turned off

    Your organization’s MCP servers in Copilot policy is off. Ask a GitHub admin to turn it on.

  • The search says your account cannot use the lead finder

    The lead finder is part of the SiteSeeker agency plans. A hosting-only account cannot search from an AI app.

  • The search stops because credits ran out

    Every search reports what it cost and what is left. Check your balance and plan in SiteSeeker, then search again. Saving leads costs no credits.

  • You want to disconnect an app

    Open Settings, MCP in SiteSeeker and press Disconnect next to the app. Its access ends at once.

Still stuck? Email team@siteseeker.ai with the app you use and what you see.