Developers

Claude via MCP

Connect Claude or ChatGPT to your Buyerbase workspace. Ask about your buyers, viewings and properties in plain language, and make changes as yourself, each one confirmed in the client first. Scoped to your agency, every call recorded.

Two ways to connect

Sign in with Buyerbase

For Claude and ChatGPT. You sign in with your own account and the tools act as you, with your permissions: reads, and changes you confirm.

Agency API key

For integrations and scripts. Read only: a key never makes a change.

Sign in with Buyerbase

Claude (claude.ai and Claude Desktop)

Settings, Connectors, Add custom connector. Paste https://mcp.buyerbase.app, choose Connect and sign in with your Buyerbase account. Claude asks before every change.

Claude Code

Add the server, then run /mcp in Claude Code and choose Authenticate to sign in.

claude mcp add --transport http buyerbase https://mcp.buyerbase.app

ChatGPT

With developer mode on: Settings, Apps and Connectors, Create. Paste https://mcp.buyerbase.app, choose OAuth and sign in with your Buyerbase account. ChatGPT asks before every change.

Buyerbase then shows what the client may read and change, with Allow and Deny. Removing a member from your agency, or switching AI off in Settings, ends the access at once.

With an agency API key, read only

1. Create an API key

The MCP server authenticates with your agency API key: Settings, API keys, Create key. The key is shown once. Treat it like a password; revoke it there at any time and the connection stops immediately.

2. Claude Desktop

Add this block to your Claude Desktop configuration and replace bb_YOUR_KEY with your key.

{
  "mcpServers": {
    "buyerbase": {
      "type": "http",
      "url": "https://mcp.buyerbase.app",
      "headers": {
        "Authorization": "Bearer bb_YOUR_KEY"
      }
    }
  }
}

Or Claude Code

claude mcp add buyerbase https://mcp.buyerbase.app --transport http --header "Authorization: Bearer bb_YOUR_KEY"

What the tools do

The server at https://mcp.buyerbase.app offers six read tools to everyone who connects and nine changes to a member who signs in, all scoped to your agency. Document contents are never available through MCP; files stay behind the audited download endpoint.

Read

search_peopleFind buyers, sellers, tenants and landlords by name, email, phone, tag or stage.

get_personOne person's profile, tags, notes, relations, tenants and landlords.

list_viewingsViewings by status or time window.

list_propertiesProperties by status or address.

get_activityThe activity feed, optionally per person.

search_documentsDocument metadata only, never file contents.

Change, when you are signed in

The same nine changes Bas makes in the app. Each runs as you, lands in the buyer's Activity marked via MCP, and can be reversed there. A key cannot call them.

create_taskCreate a task, on a buyer or on its own.

add_noteAdd a note to a buyer.

log_touchLog a call or other contact with a buyer.

move_stageMove a buyer to another stage.

schedule_viewingSchedule a viewing; the buyer gets the confirmation.

add_saved_homesAdd homes to a buyer's saved homes.

reschedule_viewingMove a viewing; the buyer gets the new time.

record_bidRecord a bid on a house.

log_saleLog a sale, sent for approval where your agency asks for it.

Every change is confirmed first

The change tools are marked as changing data, so Claude and ChatGPT ask you before each one, and the server tells the model to say what it will change and wait for your yes. A retried call with the same request id makes the change once. MCP calls cost no credits; each member and each key can make 60 calls a minute.

Questions worth asking

Which buyers are stuck in the mortgage advice stage?
Which viewings this week are still unconfirmed?
What happened on Anna de Vries's file in the last month?
Which active properties under 450k have no viewings yet?
Which buyers are still missing an approved proof of identity?

Privacy

Every tool call is written to your agency's audit log with the tool name, its arguments and who made it: the member who signed in, or the key. A key or an account from another agency sees nothing of yours, and requests that would cross agencies are refused loudly rather than answered empty.