BasedOnBusinessBasedOnBusiness
LoginSign Up
Back to Blog

basedonb is now a Claude.ai connector — say 'find restaurants in Istanbul' and Claude does the rest

Ilyas Yıldırım
Ilyas Yıldırım
2026-05-10

Until today, hooking basedonb's MCP server up to an AI assistant meant editing config files (Claude Code, Claude Desktop, Cursor) and pasting long API keys. From now on, Claude.ai users can connect basedonb from inside a chat — sign in, click Authorize, done.

The same plumbing also works for ChatGPT custom connectors and n8n's MCP Client node.

Why it matters

The earlier flow worked, but it had friction. If you wanted Claude to scrape leads for you, you had to leave the chat, drop into a terminal, copy a key out of basedonb, paste it into a JSON file, restart the client. The "tell the AI what you want" promise leaked through a technical fence.

The new connector flow fixes that:

  • One-time consent: click Authorize in Claude.ai once. Refresh tokens keep the connection alive in the background.
  • No keys on the AI side: your basedonb API keys stay in our dashboard. They never leave it.
  • Revoke whenever: list of connected apps in Connectors → Authorized apps. One click and the AI loses access.
  • Full tool surface: all 9 MCP tools (submit_scrape, get_scrape_status, list_countries, etc.) become available to Claude in the same conversation.

Three minutes to connect

  1. In Claude.ai: Settings → Connectors → Add custom connector.
  2. Paste https://basedonb.com/api/mcp as the URL.
  3. You'll be redirected to basedonb. Sign in (or skip if already in).
  4. Click Authorize.
  5. Done. You land back where you started; Claude.ai remembers the connection.

From now on the tools just show up — Claude will call submit_scrape, get_scrape_results, etc. as needed.

Example uses

You: "Find me 100 restaurants in Istanbul. Prioritize ones with phone + address. Give me a CSV summary."

Claude: (calls basedonb) Found 100 restaurants. Top 10 below… [CSV blob]

Or:

You: "Which scrape jobs ran this week, and were any of them aborted?"

Claude: (list_scrapes + get_scrape_status) 12 jobs in the last 7 days. 11 completed, 1 cancelled due to insufficient credits.

Works for ChatGPT and n8n too

ChatGPT custom connectors (Plus/Pro/Team) accept the same URL. n8n workflows that use the MCP Client node can authenticate with a single OAuth approval instead of dropping API keys into every node.

What about existing API key users?

Nothing changes. Your bdb_live_* keys keep working on the same endpoint. Connectors run alongside the API key flow — Claude Code, cron jobs, server automation still use keys; Claude.ai / ChatGPT / n8n use OAuth.

Reference

The dashboard shows what's connected and lets you revoke access in one click whenever you want.