Data Collection
usespur.com
An MCP server that searches live property listings and manages saved real estate properties.
ENDPOINT 1
https://mcp.usespur.com/mcp
MCP server metadata
- Name
- spur-mcp-server
- Version
- 1.0.0
Spur is a real-estate prospecting platform: find properties, skip-trace owners, and reach them by SMS, email and direct mail. Typical flow: spur_search_properties → spur_save_properties → spur_enrich (owner contacts) → outreach (spur_draft_message, spur_send_sms, workflows) or direct mail. Direct mail design: postcards come in 6x4, 6x9 and 6x11; letters are US Letter in one of two types, top_first_page (address shows through the envelope window, so the top 3.15in stays empty) or insert_blank_page (Spur adds an address page, so the letter keeps the full page). Start from blank (start_from_blank=true) or redesign an existing template (base_template_id, including Spur gallery designs) with spur_create_postcard_template / spur_create_letter_template, refine with the matching update tool, then mail: spur_preview_postcard_campaign → spur_send_postcards, or spur_preview_letter_campaign → spur_send_letters. QR codes on postcards: by default, design every postcard back with an empty QR code box (<div class="qr-box">) in the message area, unless the user says they don't want a QR code. Then fill it with spur_add_postcard_qr_code (never hand-write QR markup). Manage tracked codes with spur_list_qr_codes / spur_create_qr_code / spur_update_qr_code / spur_delete_qr_code; if none fits, ask the user where scans should go. See who scanned with spur_get_qr_code_activity. The user's own images (logos, headshots, property photos): spur_list_images gives their saved images with public URLs to use in postcard, letter and email HTML. To add one from their device, including an image they attached to the chat (attachments don't reach Spur), call spur_upload_image and let them drop it in; for a public link, spur_save_image. Prefer the user's saved images over stock photos when they fit. Email and SMS: design templates with spur_create_email_template (start_from_blank=true gives a responsive, compliant layout) or spur_create_sms_template, refine with the matching update tool, and check them with spur_preview_message_template (inbox/phone view, sample or real owner data) or spur_preview_message_draft before saving; spur_send_test_email sends one to the user's own inbox. Saved templates drive outreach workflows: spur_create_workflow builds a sequence (send_email / send_sms / send_direct_mail / wait steps) as an inactive draft, spur_set_workflow_step_template swaps a step's template, then spur_set_workflow_active and spur_enroll_owners_in_workflow start it after approval. Property research: translate the user's criteria into structured filters (spur_parse_search_query previews this for free), and use event filters for change or motivation signals (price drops, back on market, stale, distress stages, FSBO, equity gaps). If a search comes back thin, read the filter/event notes it returns and relax one constraint at a time instead of guessing. Recurring research belongs in spur_create_search_automation with the same filters. Paying for Spur: when the user wants to add funds, buy credits, upgrade or compare plans, or a tool fails with "Billing limit reached", call spur_show_billing_options. It renders one-click Pay and Upgrade buttons. Or go straight to spur_top_up_wallet (amount_usd) or spur_change_plan (plan_id, billing_interval) when the user named what they want. Both return a Stripe checkout link: share it, and once the user says they paid, call spur_check_payment with its session_id. When a send is short on funds, suggest a top-up that covers the shortfall (round up to $25, $50 or $100) and offer spur_set_auto_recharge so it doesn't happen again. Rules: - Tools that spend money or contact people need explicit user approval for that exact action (confirm=true). Never assume it. - Postcards and letters always go through their preview tool first (spur_preview_postcard_campaign / spur_preview_letter_campaign); send only with that preview's confirmation_token after the user approves. - Check spur_get_billing_summary before large sends or enrichment batches. - Never ask for card numbers in the chat; payment happens only on Stripe's page. Switching an existing paid subscription and turning on auto-recharge charge the saved card, so they need confirm=true after explicit approval. - Refer to properties and owners by address/name, not ids, when talking to the user. - Spur tools are the only source for the user's templates, postcards, properties and owners. Never supplement them with web search, image search or outside examples (e.g. Etsy, Canva, Pinterest), and never invent details a tool didn't return. - When a tool renders a preview widget, that widget is the preview. Don't add other images or mockups, and don't describe the design beyond what the tool result says.
Known tools 78
spur_search_propertiesSearch live listings (Zillow data) in Spur with plain English and/or structured filters, including event filters.
Inferred read-onlyspur_parse_search_queryShow how Spur interprets a plain-English property search (filters and events) without running it.
Inferred read-onlyspur_get_propertyShow one property as a detailed card: a saved Spur property by property_id, or a live listing by zpid.
Inferred read-onlyspur_save_propertiesSave live listings into the user's Spur properties (and optionally a property list).
Inferred read-onlyspur_list_saved_propertiesList properties the user has saved in Spur, optionally filtered by city, state, list, or enrichment status.
Inferred read-onlyspur_get_property_statsTotals for the user's saved properties: counts by status, enrichment progress and similar portfolio-level numbers.
Inferred read-onlyspur_find_ownersFind property owners in the user's Spur account by name, phone, email or mailing address text.
Potential side effectsspur_get_ownerFull owner record: contact details, mailing address, enrichment status and their property portfolio in Spur.
Inferred read-onlyspur_enrichRun skip tracing to find owners and their phone numbers, emails and mailing addresses.
Inferred read-onlyspur_create_property_listCreate a property list, optionally seeding it with saved property ids.
Potential side effectsspur_list_workflowsThe user's multi-step outreach workflows (email/SMS/mail sequences) with status and enrollment counts.
Potential side effectsspur_get_workflowOne outreach workflow's steps in order (including reply/open branches built in the app), with the email, SMS or mail template each send step uses and its step_id.
Potential side effectsspur_create_workflowCreate a multi-step outreach sequence from saved templates.
Potential side effectsspur_set_workflow_step_templateSet which saved template a workflow's send step uses (send_email ← email template, send_sms ← SMS template, send_direct_mail ← postcard/letter template).
Potential side effectsspur_set_workflow_activeActivate a workflow (enrolled owners start receiving its emails, texts and mail on schedule, which uses credits) or pause it.
Inferred read-onlyspur_list_sms_conversationsSMS conversations with owners, newest first, with unread counts and the last message.
Potential side effectsspur_get_outreach_reportOutreach performance (sent, delivered, opened, replied, by channel) for all workflows or one, over an optional date range.
Inferred read-onlyspur_get_message_templateFetch an email template's subject, HTML and plain text, or an SMS template's text, for reading or editing.
Potential side effectsspur_preview_message_templateShow a saved email (inbox view, desktop and mobile) or SMS (phone view, segment count) rendered with sample data or a real owner's data, plus design checks.
Potential side effectsspur_preview_message_draftPreview email HTML or SMS text before saving it: renders it with sample or real owner data and runs the design checks.
Potential side effectsspur_create_email_templateSave a new email template and show its inbox preview.
Potential side effectsspur_update_email_templateEdit one of the user's email templates and show the updated inbox preview.
Potential side effectsspur_create_sms_templateSave a new SMS template and show its phone preview with segment count and checks.
Potential side effectsspur_update_sms_templateEdit one of the user's SMS templates and show the updated preview.
Potential side effectsspur_send_test_emailSend an email template, filled with sample data (or one owner's data), to the user's own Spur account email from their email sender, to check it in a real inbox.
Potential side effectsspur_list_postcard_templatesPostcard templates available to the user: their own (editable), Spur defaults, and Spur's built-in gallery.
Inferred read-onlyspur_get_postcard_templateFetch a postcard template's HTML for reading or editing.
Inferred read-onlyspur_preview_postcard_templateShow any postcard template (yours, a Spur default or a gallery design) rendered with sample data, without changing anything.
Inferred read-onlyspur_update_postcard_templateEdit one of the user's postcard templates and show the updated preview.
Potential side effectsspur_add_postcard_qr_codePut a tracked QR code on the back of one of the user's postcard templates and show the preview.
Inferred read-onlyspur_remove_postcard_qr_codeRemove the tracked QR code from one of the user's postcard templates (both sides) and show the preview.
Potential side effectsspur_delete_postcard_templatePermanently delete one of the user's postcard templates.
Potential side effectsspur_list_qr_codesThe user's tracked QR codes: destination URL, colors, and which of their postcard templates print each one.
Inferred read-onlyspur_create_qr_codeCreate a tracked QR code that sends scans to destination_url.
Potential side effectsspur_get_qr_code_activityScan activity for a QR code: totals, which mailed recipients (owners) scanned their postcard, and recent scans of the code itself.
Inferred read-onlyspur_list_imagesThe user's saved images (logos, headshots, property photos) with their public URLs, newest first.
Inferred read-onlyspur_save_imageDownload an image from a public https URL (the user's website, a shared photo link) and save it to the user's Spur image library, so it stays available for printing and sending.
Inferred read-onlyspur_upload_imageShow an upload box where the user picks or drops an image from their device (logo, headshot, property photo); it's saved to their Spur image library.
Potential side effectsspur_save_uploaded_imageUsed by the upload widget to save the file the user picked.
Potential side effectsspur_list_letter_templatesLetter templates available to the user, with their letter type (Top First Page or Insert Blank Page): their own (editable), Spur defaults, and Spur's built-in gallery.
Potential side effectsspur_preview_letter_templateShow any letter template (yours, a Spur default or a gallery design) rendered with sample data, without changing anything.
Inferred read-onlyspur_update_letter_templateEdit one of the user's letter templates and show the updated preview.
Potential side effectsspur_delete_letter_templatePermanently delete one of the user's letter templates.
Potential side effectsspur_get_billing_summaryPlan, wallet balance, and this period's usage and remaining allowance per feature (searches, enrichment, SMS, postcards, letters, AI).
Potential side effectsspur_list_campaignsThe user's campaigns (bulk email, SMS, direct mail, outreach) with status and recipient progress.
Potential side effectsspur_get_direct_mail_analyticsLetters and postcards sent, delivered, in transit and returned, plus USPS tracking totals and spend.
Inferred read-onlyspur_show_billing_optionsShows the user's wallet balance, one-click top-up amounts, auto-recharge status and every Spur plan with prices, in a widget with Pay/Upgrade buttons.
Potential side effectsspur_top_up_walletCreates a Stripe checkout link to add funds to the user's Spur wallet (pays for postcards, letters, SMS, enrichment and other usage beyond the plan).
Potential side effectsspur_change_planMoves the user to another Spur plan (ids from spur_show_billing_options; usually agent, team or brokerage).
Inferred read-onlyspur_check_paymentAfter the user pays a Stripe checkout link from spur_top_up_wallet or spur_change_plan, confirms the payment went through and returns the new wallet balance and plan.
Potential side effectsspur_manage_billingLink to the user's Stripe billing portal: update the card on file, download invoices, change or cancel the subscription.
Potential side effectsspur_list_search_automationsScheduled property searches with their schedule, filters, and next/last run times.
Inferred read-onlyspur_run_search_automationRun a search automation immediately instead of waiting for its schedule.
Inferred read-onlyspur_get_automation_logsRecent runs of a search automation: when, how many found/saved/enriched, and errors.
Inferred read-onlysearchSearch the user's saved Spur properties, owners and postcard templates by keyword (address, city, owner name, phone, email, template name).
Potential side effectsfetchFetch the full text of a record returned by search (ids look like property:…, owner:… or template:…).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.spur-mcp-server]
url = "https://mcp.usespur.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"spur-mcp-server": {
"type": "http",
"url": "https://mcp.usespur.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: spur-mcp-server
Remote MCP URL: https://mcp.usespur.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"spur-mcp-server": {
"url": "https://mcp.usespur.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"spur-mcp-server": {
"type": "http",
"url": "https://mcp.usespur.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "spur-mcp-server",
"transport": "streamable-http",
"url": "https://mcp.usespur.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.