BuildMapper
BuildMapper MCP
Included with ProNew

BuildMapper MCP. Your account, in your AI assistant.

Connect the AI assistant you already use (Claude today, more as they support MCP) to your BuildMapper account and work it from the conversation: every permit scored for you, your pipeline and documents, your catalog, and the customer list you already keep in a spreadsheet or CRM, checked against this week's permits without importing it. Reads just happen; every change asks you first.

Claude· BuildMapper MCP connected
Open my “Key accounts 2026” sheet and tell me which of those builders pulled a permit in the last 90 days.
Read 48 names from the sheet and checked them against BuildMapper. 31 are builders on file; 9 of those filed in the last 90 days.
Filing now · scored for you
Carrington Construction · 3 permits · newest: 1200 Lakeshore Dr, Kelowna · $4.2M · Hot
Polygon Construction Management · 2 permits · 880 Clement Ave · $12M · Hot
Jayman Built (Calgary) · 4 permits · newest: 22 Cityscape Way NE · $610K · Warm
Save Carrington's Lakeshore project to my pipeline and draft an email to the builder. Don't send it.
Saved to your pipeline in New (your score: 84). Here's a draft for the Carrington estimator, from your signature. Nothing was sent.
Setup

Connected in three steps. No IT ticket.

One address, your own login, and the assistant lists what it can do before you sign in. The full walkthrough for Claude, with what to ask first, is in the Learn guide.

01
Copy the address
In BuildMapper, Settings → Integrations → Claude and other AI apps. One address for every user.
02
Add it to your AI app
In Claude: Customize → Connectors → Add custom connector → paste. On a Team or Enterprise plan an owner adds it once for everyone. Other MCP apps take the same address.
03
Sign in once
The app sends you to BuildMapper. Sign in, read what it can and cannot do, press Allow. You are back in the chat, connected.
What to ask

Everything the app does, in plain words.

Permits
  • “What permits over $2M were filed in Kelowna this month? Newest first.”
  • “What's within 5 km of 1200 Lakeshore Drive?”
  • “Who is the builder on the Glenmore permit, and what do we know about them?”
Your pipeline
  • “Which of my leads have gone quiet, and what did I last note on each?”
  • “Prepare me for Thursday's call about the Clement Ave project.”
  • “Move the Lakeshore lead to Quoted and set a follow-up for Friday.”
Your own data
  • “Check the accounts Dana owns in Salesforce against BuildMapper. Who is building?”
  • “Which companies in this export have a permit over $1M in Calgary this year?”
  • “Keep this list as my customers in BuildMapper.”
Your catalog & team
  • “What's our list price on 5/4x6 cedar decking? (quoted only from your own price book)”
  • “What did Carrington buy from us last quarter? (your ERP, read-only)”
  • “Which builders in Vernon are not yet our customers? (Territory Intelligence, managers)”
Your data, without the import

Your customers live in a sheet. Leave them there.

Every supplier has a list somewhere: a spreadsheet, the CRM, an ERP export. Claude can usually read it already. So instead of asking you to upload it, Claude reads the names where they are and asks BuildMapper which of them are filing permits now. Nothing is copied, nothing is stored. Say “keep this list” and it lands exactly where a dropped file would.

  • Reads Google Sheets, Drive, Salesforce, HubSpot, a pasted list or an email, whatever you have connected to Claude
  • Matches each name to the builder on file and says how sure it is; a guess is marked as a guess
  • Returns the newest permits per company, scored for you, with locked projects masked as in the app
  • Run it every Monday on the same sheet; a read-through has no side effects
The sheet
48 names in “Key accounts 2026”, read by Claude from your Drive.
The check
31 matched to builders on file. 9 filed in the last 90 days. 17 not found: new names, or not builders.
The answer
Carrington, Polygon and Jayman are building this month, with addresses, values and your score on each.
Only if you ask
“Keep this list” files it as named accounts for the branch and contacts for you, duplicates skipped.
How it behaves

Your login. Your view. Your say on every change.

BuildMapper MCP is not an API key and not a shared account. Each person signs in as themselves, the AI app holds a token it can only use as them, and the rules Scout follows in the app hold over MCP too.

  • It sees what you see. Every tool runs as your account with the app's visibility rules: locked projects stay masked, a rep sees their pipeline, a manager sees the team's.
  • Reads run on their own; changes ask first. Claude searches and reads without a prompt and asks you before every change. You can set any tool to always allow, ask, or blocked.
  • It never sends anything. Emails come back as drafts; quotes and contracts are started for you to finish in the app.
  • Changes can be undone. Every reversible change comes back with an undo; say “undo that”.
  • A price is your price book's or it is not quoted. The same rules Scout follows apply over MCP.
  • Disconnect any time. Settings → Integrations lists every app you have allowed; one press ends its access.

Common questions.

MCP (Model Context Protocol) is the open standard AI apps use to reach other products. BuildMapper MCP is BuildMapper's own MCP server: add its address to an AI app that supports it, sign in with your BuildMapper login, and the assistant can work your account as you. Claude supports it today; other MCP apps use the same address.
Reaches

The whole product, one connector.

Permit Map
Searches come back as an interactive map inside the chat, a project as its card.
Pipeline
Read it, move a stage, add a note, set the next action. Each change asks first.
Scout
The same tools and rules Scout runs on, from the AI assistant you already use.
Team Flow & Territory
Managers read the team's board and the coverage gap list from the chat.

Already working in an AI assistant? Bring BuildMapper with you.

Copy the address from Settings → Integrations, add it to your AI app, sign in once. Your first question is waiting.