Spur

Connect it to your AI

Claude Code

claude mcp add --transport http spur https://mcp.usespur.com/mcp

Claude, ChatGPT, Cursor and other apps

Add it as a custom connector with this URL (Streamable HTTP):

https://mcp.usespur.com/mcp

Cursor, VS Code and other apps (mcp.json)

{
  "mcpServers": {
    "spur": {
      "url": "https://mcp.usespur.com/mcp"
    }
  }
}

Tools it offers

60 tools, as the server itself reported during our check on Oct 31, 2026.

• spur_search_propertiesSearch live listings (Zillow data) in Spur with plain English and/or structured filters, including event filters. Results show as cards and a map. Uses 1 property-search credit per call from the user's Spur plan, or 2 cr
• spur_parse_search_queryShow how Spur interprets a plain-English property search (filters and events) without running it. Free: uses no search credit. Use it to confirm intent before spending a credit, or to turn a vague request into explicit f
• spur_get_propertyShow one property as a detailed card: a saved Spur property by property_id, or a live listing by zpid. Includes owner links and enrichment status for saved properties.
• spur_save_propertiesSave live listings into the user's Spur properties (and optionally a property list). Pass listing objects from spur_search_properties structuredContent.cards[].listing. Already-saved listings are refreshed, not duplicate
• spur_list_saved_propertiesList properties the user has saved in Spur, optionally filtered by city, state, list, or enrichment status. Shows cards and a map.
• spur_get_property_statsTotals for the user's saved properties: counts by status, enrichment progress and similar portfolio-level numbers.
• spur_find_ownersFind property owners in the user's Spur account by name, phone, email or mailing address text. Use spur_get_owner for full details and portfolio.
• spur_get_ownerFull owner record: contact details, mailing address, enrichment status and their property portfolio in Spur.
• spur_enrichRun skip tracing to find owners and their phone numbers, emails and mailing addresses. - property_ids: find the owner of saved properties (creates/links owner records) - owner_ids: refresh contact details for existing ow
• spur_list_property_listsAll of the user's property lists with ids and sizes. Use the id with spur_list_saved_properties, spur_add_properties_to_list or outreach tools.
• spur_create_property_listCreate a property list, optionally seeding it with saved property ids.
• spur_add_properties_to_listAdd saved properties to an existing property list.
• spur_draft_messageDraft an email, SMS or direct-mail message with Spur's AI. Returns text only; nothing is sent. Pass owner_id/property_id to personalize with real owner and property data. Uses 1 AI credit. Use {{merge_fields}} like {{own
• spur_list_workflowsThe user's multi-step outreach workflows (email/SMS/mail sequences) with status and enrollment counts.
• spur_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.
• spur_create_workflowCreate a multi-step outreach sequence from saved templates. It's saved as an inactive draft: nothing sends until it's activated (spur_set_workflow_active) and owners are enrolled. Send steps take a saved template: email/
• spur_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). Get step_ids from spur_get_workflow. If the workflow is active, en
• spur_set_workflow_activeActivate a workflow (enrolled owners start receiving its emails, texts and mail on schedule, which uses credits) or pause it. Activating requires every send step to have a template and the user's explicit approval.
• spur_enroll_owners_in_workflowEnroll owners in an outreach workflow. The workflow will start emailing/texting/mailing them on its schedule, which uses credits. Confirm the workflow name and owner count with the user first.
• spur_send_smsText an owner from the user's default approved number (or Spur's workspace number if they have none; see spur_get_texting_setup). Show the user the exact message and recipient and get approval before calling with confirm
• spur_list_sms_conversationsSMS conversations with owners, newest first, with unread counts and the last message. Good for triaging replies (hot leads, not interested, wrong number).
• spur_get_sms_conversationThe full SMS thread with one owner, oldest first.
• spur_get_outreach_reportOutreach performance (sent, delivered, opened, replied, by channel) for all workflows or one, over an optional date range.
• spur_list_message_templatesThe user's saved email and SMS templates. These are what outreach workflow send_email / send_sms steps use.
• spur_get_message_templateFetch an email template's subject, HTML and plain text, or an SMS template's text, for reading or editing. For small changes prefer the update tool's replacements over resending everything.
• spur_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. Changes nothing.
• spur_preview_message_draftPreview email HTML or SMS text before saving it: renders it with sample or real owner data and runs the design checks. Nothing is saved; iterate here, then save with spur_create_email_template / spur_create_sms_template.
• spur_create_email_templateSave a new email template and show its inbox preview. Ways to start: - From blank: start_from_blank=true gives a tested 600px responsive layout with greeting, signature and a compliant footer; pass html to replace it. -
• spur_update_email_templateEdit one of the user's email templates and show the updated inbox preview. For tweaks pass replacements (exact find → replace in "html", "subject" or "text"); to redesign pass full html. When the HTML changes, the plain-
• spur_create_sms_templateSave a new SMS template and show its phone preview with segment count and checks. The saved template can then be used by outreach workflows (spur_create_workflow / spur_set_workflow_step_template). SMS guidance: plain te
• spur_update_sms_templateEdit one of the user's SMS templates and show the updated preview. Pass full text / fallback_body, or replacements (exact find → replace in "text" or "fallback"). Pass fallback_body="" to remove the fallback. SMS guidanc
• spur_delete_message_templateDelete one of the user's email or SMS templates. Workflow steps that use it will fail until they get another template, so check spur_list_workflows and confirm with the user first.
• spur_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. Never goes to owners. Confirm with the user first.
• spur_list_postcard_templatesPostcard templates available to the user: their own (editable), Spur defaults, and Spur's built-in gallery. Copy a default or gallery design with spur_create_postcard_template base_template_id to redesign it, or start fr
• spur_get_postcard_templateFetch a postcard template's HTML for reading or editing. For small text changes prefer spur_update_postcard_template with replacements instead of resending whole HTML.
• spur_preview_postcard_templateShow any postcard template (yours, a Spur default or a gallery design) rendered with sample data, without changing anything.
• spur_create_postcard_templateCreate a postcard template and show a preview. Three ways to start: - From blank: start_from_blank=true gives an empty, correctly sized canvas for the size (any side you pass HTML for replaces the blank side). - Redesign
• spur_update_postcard_templateEdit one of the user's postcard templates and show the updated preview. For text tweaks pass replacements (exact find → replace on a side); to redesign, pass full front_html/back_html. Spur default and gallery templates
• spur_add_postcard_qr_codePut a tracked QR code on the back of one of the user's postcard templates and show the preview. Each mailed postcard gets its own code under the chosen QR code, so scans are tracked per recipient (spur_get_qr_code_activi
• spur_remove_postcard_qr_codeRemove the tracked QR code from one of the user's postcard templates (both sides) and show the preview. A QR slot from the design stays, empty.

Questions