Connect SiteSeeker to any MCP app

SiteSeeker works in any app that can add a remote MCP server over Streamable HTTP and sign in with OAuth.

Any app with remote MCP servers

Before you start

  • An app that supports remote MCP servers with OAuth sign-in.
  • A SiteSeeker agency plan. Searches spend its search credits, and hosting-only accounts cannot search.

Connect SiteSeeker

Server URL
https://siteseeker.ai/mcp

  1. Add a remote MCP server with the server URL. If the app asks for a transport, choose Streamable HTTP (sometimes just HTTP).

  2. Choose OAuth for sign-in and leave any client ID field empty. SiteSeeker registers the app on its own.

  3. Sign in to SiteSeeker in your browser and allow access.

Note. Results show as an interactive table in apps that support MCP Apps, and as text everywhere else.

Check it works

In a new chat or session, 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 app asks for a client ID and secret

    Leave them empty if you can. SiteSeeker supports Dynamic Client Registration and Client ID Metadata Documents, so the app registers itself.

  • The app only offers SSE or stdio

    SiteSeeker needs Streamable HTTP. Look for an HTTP or remote server option, or use one of the apps listed here.

  • 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.