Agents IA

How to Connect Your AI Agent to SiteSeeker

Use Claude, Cursor or any AI agent to automatically search for businesses without websites. Complete guide with MCP and REST API.

B
Baptiste
SiteSeeker
May 7, 2026
10 min de lecture

1

Introduction: Automating Your Prospecting

AI agents can now search for prospects for you — while you sleep.

If you use Claude, Cursor, Windsurf, or any AI tool in your daily workflow, you can now give them access to SiteSeeker. The result: your agent can search for businesses without websites, retrieve their contact details, and prepare a prospect list — without you ever opening a browser.

This guide shows you how to set up the connection in under 5 minutes, whether you go through MCP (for Claude Desktop, Cursor, Windsurf) or the REST API (for n8n, Make, custom scripts).

2

Step 1 — Create Your API Key

All authentication is based on a personal API key. It replaces your web session and allows your agents to act on your behalf.

Generate your key from your profile

  1. Log in to your SiteSeeker profile
  2. Click the Developer tab
  3. Give your key a name (e.g. "My Claude Agent")
  4. Click Generate
  5. Copy the key immediately — it won't be shown again after closing

The key looks like: sk_live_a1b2c3d4e5f6...

You can create up to 10 different keys and revoke each one individually.

Security

Treat your API key like a password. Don't share it, don't commit it to Git. If it's compromised, revoke it from your profile and generate a new one.

3

Step 2 — Configure Claude Desktop (via MCP)

The MCP protocol (Model Context Protocol) lets Claude Desktop call SiteSeeker as a native tool, directly from your conversations.

MCP Configuration for Claude Desktop

Open the Claude Desktop configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the mcpServers section:

{
  "mcpServers": {
    "siteseeker": {
      "url": "https://siteseeker.fr/api/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_YOUR_KEY_HERE"
      }
    }
  }
}

Restart Claude Desktop. You'll see a 🔌 icon in the interface indicating SiteSeeker is connected.

Add via Claude Code CLI (one command)

Recommended

If you use Claude Code in your terminal, register SiteSeeker with your API key in a single command:

claude mcp add --transport http siteseeker https://siteseeker.fr/api/mcp \
  --header "Authorization: Bearer sk_live_YOUR_KEY_HERE"

Replace sk_live_YOUR_KEY_HERE with the key generated in your profile. SiteSeeker tools are immediately available in all your Claude Code sessions.

Once configured, simply type in Claude:

Example prompts for Claude

Simple search:"Find plumbers in Lyon that don't have a website and give me their phone numbers."

Search with commercial context:"I need 20 prospects for my week's outreach. Find restaurants in Bordeaux without a website, with a rating above 4 stars."

Complete workflow:"Check my credit balance, then find hair salons in Marseille without a website, and show me the top 10 by number of reviews."

Claude will automatically call get_balance, then search_businesses, then get_task to return formatted results.

4

Step 3 — Configure Cursor or Windsurf (via MCP)

Cursor and Windsurf also support the MCP protocol. The configuration is nearly identical.

Cursor

In Cursor settings, go to Features → MCP Servers and add:

{
  "name": "SiteSeeker",
  "url": "https://siteseeker.fr/api/mcp",
  "headers": {
    "Authorization": "Bearer sk_live_..."
  }
}

Windsurf

Open ~/.codeium/windsurf/mcp_config.json and add:

{
  "mcpServers": {
    "siteseeker": {
      "serverUrl": "https://siteseeker.fr/api/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_..."
      }
    }
  }
}

5

Step 4 — Use the REST API (n8n, Make, scripts)

If you prefer to integrate SiteSeeker into your automations without MCP, the REST API is available directly.

REST calls with curl

Check your balance:

curl https://siteseeker.fr/api/credits/balance \
  -H "Authorization: Bearer sk_live_..."

Run a search:

curl https://siteseeker.fr/api/tasks \
  -X POST \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "query": "restaurants without website Paris",
    "country": "FR",
    "lang": "en"
  }'

Retrieve results:

curl https://siteseeker.fr/api/tasks/TASK_ID \
  -H "Authorization: Bearer sk_live_..."

When to use MCP

  • Natural conversation with Claude
  • No coding required
  • Claude handles multi-step logic
  • Ideal for daily use

When to use REST API

  • Automations in n8n or Make
  • Python or Node.js scripts
  • Integrations with other tools
  • Scheduled workflows (cron jobs)
  • 6

    Concrete Workflow Examples

    Workflow: Weekly Prospect List

    Popular

    Every Monday morning, your agent automatically generates a fresh list of 50 prospects.

    With n8n: Schedule an HTTP POST node to /api/tasks with your usual query. Connect it to a Google Sheets node to feed your CRM directly.

    With Claude: "Every time I say 'Monday list', search for 50 restaurants without a website in Paris and format the list with name, phone, and address."

    Workflow: On-Demand Search in Cursor

    While coding a client's website, ask Cursor:

    "Find other businesses similar to my current client (bakery, Lyon) without a website. I'll pitch them the same template."

    Cursor uses SiteSeeker to find 20 prospects you can contact as soon as the site is delivered.

    Workflow: Market Analysis Before a Pitch

    Before prospecting a new city or sector:

    "How many plumbers without a website are there in Toulouse? Give me their average rating and total count so I can evaluate the market potential."

    Your agent runs the search, analyzes the data, and gives you an actionable summary.

    7

    Track Your API Requests

    All searches made via API or AI agent are tracked separately in your account. In your task list, you'll see an "API" indicator distinguishing automated searches from your manual ones.

    What you can track

    • Number of searches made by your agents vs manually
    • Which API key was used (useful if you have multiple agents)
    • Credits consumed by each automated workflow
    • Full history of results, accessible from /app/tasks

    Each credit consumed is identical whether it comes from a manual action or an AI agent. Check your balance before launching intensive workflows.

    8

    The 4 Tools Available to Your Agents

    Here's exactly what your AI agent can do with SiteSeeker:

    Available MCP Tools

    Your agent has access to these 4 actions:

    search_businesses — Runs a search and returns up to 60 businesses with their contact details

    get_task — Retrieves the full result of a previous search (name, address, phone, email, website)

    list_tasks — Lists your recent searches to find results again

    get_balance — Checks your credit balance before running a search

    Conclusion

    Connecting an AI agent to SiteSeeker transforms your prospecting: instead of searching manually, your agent works for you — on demand or on a schedule.

    1

    Create your API key from the Developer tab in your profile

    2

    Configure your agent (Claude Desktop, Cursor, or REST API)

    3

    Test with a simple prompt: "Find restaurants in your city without a website"

    4

    Automate your weekly prospecting workflows

    Ready to connect your AI agent?

    Create your API key from your profile and start automating your prospecting today.

    Partager cet article

    Retour au blog

    Pret a trouver vos prochains clients ?

    Commencez a decouvrir des entreprises sans site web dans votre region. SiteSeeker vous aide a trouver des prospects qualifies en quelques secondes.