com.usespur/spur · v1.0.0 · communication
Spur is healthy: it completed an MCP handshake in 947 ms and exposes 78 tools.
Real estate leads, skip tracing, direct mail, SMS & email outreach, and marketing automations
Endpoint: https://mcp.usespur.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 78 |
| Latency | 947 ms |
| Last checked (UTC) | 2026-10-24T23:40:14.021Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-24T23:40:14.021Z | Healthy | 947 |
spur_search_properties | Search 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 credits when the search makes more than 3 ZHomes calls (e.g. several event types, |
spur_parse_search_query | Show 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 filters you can adjust. The returned arguments can be passed straight to spur_se |
spur_get_property | Show 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_properties | Save 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 duplicated. |
spur_list_saved_properties | List properties the user has saved in Spur, optionally filtered by city, state, list, or enrichment status. Shows cards and a map. |
spur_get_property_stats | Totals for the user's saved properties: counts by status, enrichment progress and similar portfolio-level numbers. |
spur_find_owners | Find 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_owner | Full owner record: contact details, mailing address, enrichment status and their property portfolio in Spur. |
spur_enrich | Run 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 owners Costs enrichment credits per record (check spur_get_billing_summary). Ask |
spur_list_property_lists | All 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_list | Create a property list, optionally seeding it with saved property ids. |
spur_add_properties_to_list | Add saved properties to an existing property list. |
spur_draft_message | Draft 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 {{owner_first_name}} and {{property_address}} to keep it reusable (see resource spur |
spur_list_workflows | The user's multi-step outreach workflows (email/SMS/mail sequences) with status and enrollment counts. |
spur_get_workflow | One 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_workflow | Create 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/SMS from spur_list_message_templates (design new ones with spur_create_email_te |
spur_set_workflow_step_template | Set 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, enrolled owners get the new template from their next send. |
spur_set_workflow_active | Activate 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_workflow | Enroll 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_sms | Text an owner from the user's Spur number. Show the user the exact message and recipient and get approval before calling with confirm=true. Costs 1 SMS credit. |
spur_list_sms_conversations | SMS 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_conversation | The full SMS thread with one owner, oldest first. |
spur_get_outreach_report | Outreach performance (sent, delivered, opened, replied, by channel) for all workflows or one, over an optional date range. |
spur_list_message_templates | The user's saved email and SMS templates. These are what outreach workflow send_email / send_sms steps use. |
spur_get_message_template | Fetch 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_template | Show 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_draft | Preview 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. Email HTML guidance (see spur://email-design-guide): full HTML document, table |
spur_create_email_template | Save 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. - Redesign: base_template_id copies one of the user's email templates. - From scra |
spur_update_email_template | Edit 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-text version is regenerated unless it was hand-written or you pass text_body. Wo |
spur_create_sms_template | Save 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 text, ideally one segment (160 GSM characters, or 70 if it uses emoji or other no |
spur_update_sms_template | Edit 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 guidance: plain text, ideally one segment (160 GSM characters, or 70 if it uses emoji |
spur_delete_message_template | Delete 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_email | Send 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_templates | Postcard 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 from blank with start_from_blank. |
spur_get_postcard_template | Fetch 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_template | Show any postcard template (yours, a Spur default or a gallery design) rendered with sample data, without changing anything. |
spur_create_postcard_template | Create 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 an existing template: base_template_id (yours, a Spur default or a gallery id) |
spur_update_postcard_template | Edit 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 can't be edited: copy them first with spur_create_postcard_template base_templat |
spur_add_postcard_qr_code | Put 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_activity). Placement: position="auto" fills the back's QR slot (an element with class |
spur_remove_postcard_qr_code | Remove 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. |
spur_delete_postcard_template | Permanently delete one of the user's postcard templates. Spur defaults can't be deleted. Confirm with the user first. |
spur_list_return_addresses | Return addresses saved for direct mail. The default one is used when a campaign doesn't specify one. |
spur_preview_postcard_campaign | Required step before mailing postcards. Renders the postcard with the first recipient's real data, checks which owners have mailing addresses, estimates the cost from the user's plan, and returns a confirmation_token. Show the preview, then ask the user to approve. Only after they approve, call spu |
spur_send_postcards | Mail the postcards approved in spur_preview_postcard_campaign. Irreversible and charges the user's account. Requires the preview's confirmation_token and the user's explicit approval (confirm=true). |
spur_list_qr_codes | The user's tracked QR codes: destination URL, colors, and which of their postcard templates print each one. Put one on a postcard with spur_add_postcard_qr_code; see scans with spur_get_qr_code_activity. |
spur_create_qr_code | Create a tracked QR code that sends scans to destination_url. Then add it to a postcard back with spur_add_postcard_qr_code; each mailed postcard gets its own code under it so scans are tracked per recipient. |
spur_update_qr_code | Rename a QR code, change where scans go, or change its colors. A new destination also applies to postcards already mailed with this code. Templates pick up new colors at send time. |
spur_delete_qr_code | Permanently delete a QR code. Refused while one of the user's postcard templates still prints it: remove it from those first with spur_remove_postcard_qr_code. Postcards already mailed keep redirecting. Confirm with the user first. |
spur_get_qr_code_activity | Scan activity for a QR code: totals, which mailed recipients (owners) scanned their postcard, and recent scans of the code itself. Use it to find warm leads from a postcard campaign. |
spur_list_images | The user's saved images (logos, headshots, property photos) with their public URLs, newest first. Use it as <img src="…"> (or a CSS background-image) in postcard, letter or email HTML. To add one, use spur_upload_image (from the user's device) or spur_save_image (from a URL). |
spur_save_image | Download 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. Returns the saved image's URL. JPG, PNG, WebP, GIF or SVG, up to 20 MB. For a file on the user's device, use spur_upload_i |
spur_upload_image | Show 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. Use this whenever the user wants to use their own image, including one they attached to the chat: attachments don't reach Spur, so ask them to drop it |
spur_save_uploaded_image | Used by the upload widget to save the file the user picked. Not for the assistant. |
spur_delete_image | Permanently delete one of the user's saved images. Refused while one of their postcard, letter or email templates still uses it, since those would show a broken image. Confirm with the user first. |
spur_list_letter_templates | Letter 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. Copy one with spur_create_letter_template base_template_id to redesign it, or start from blank with start_from_blank. |
spur_get_letter_template | Fetch a letter template's HTML for reading or editing. For small text changes prefer spur_update_letter_template with replacements instead of resending the whole HTML. |
spur_preview_letter_template | Show any letter template (yours, a Spur default or a gallery design) rendered with sample data, without changing anything. |
spur_create_letter_template | Create a letter template and show a preview. Pick the letter type first (top_first_page or insert_blank_page); it decides where the address prints and how much of the page the design can use. Three ways to start: - From blank: start_from_blank=true gives an empty one-page letter laid out for the let |
spur_update_letter_template | Edit one of the user's letter templates and show the updated preview. For text tweaks pass replacements (exact find → replace); to redesign, pass full html. letter_type switches between top_first_page and insert_blank_page. Spur default and gallery templates can't be edited: copy them first with spu |
spur_delete_letter_template | Permanently delete one of the user's letter templates. Spur defaults can't be deleted. Confirm with the user first. |
spur_preview_letter_campaign | Required step before mailing letters. Renders the letter with the first recipient's real data in its letter type's layout, checks which owners have mailing addresses, estimates the cost from the user's plan (Insert Blank Page letters include the extra address page), and returns a confirmation_token. |
spur_send_letters | Mail the letters approved in spur_preview_letter_campaign. Irreversible and charges the user's account. Requires the preview's confirmation_token and the user's explicit approval (confirm=true). |
spur_get_billing_summary | Plan, wallet balance, and this period's usage and remaining allowance per feature (searches, enrichment, SMS, postcards, letters, AI). Check this before large sends. |
spur_list_campaigns | The user's campaigns (bulk email, SMS, direct mail, outreach) with status and recipient progress. |
spur_get_campaign_stats | Delivery and run statistics for one campaign. |
spur_get_direct_mail_analytics | Letters and postcards sent, delivered, in transit and returned, plus USPS tracking totals and spend. |
spur_show_billing_options | Shows 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. Use whenever the user wants to add funds, buy credits, upgrade, change or compare plans, or a send failed for billing reasons. |
spur_top_up_wallet | Creates 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). No money moves until the user pays on Stripe, so no confirmation is needed. If the user didn't name an amount, suggest $25, $50 or $100, or enough to |
spur_change_plan | Moves the user to another Spur plan (ids from spur_show_billing_options; usually agent, team or brokerage). - No paid subscription yet: returns a Stripe checkout link. No confirmation needed. - Already subscribed: switches the plan immediately and charges or credits the prorated difference to the sa |
spur_check_payment | After 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. Safe to call repeatedly. |
spur_manage_billing | Link to the user's Stripe billing portal: update the card on file, download invoices, change or cancel the subscription. |
spur_set_auto_recharge | Turns wallet auto-recharge on or off. When on, Spur charges the saved card amount_usd whenever the balance drops below threshold_usd, so sends never fail for lack of funds. Needs a saved card (the first spur_top_up_wallet payment saves one). Turning it on needs the user's approval of the amount and |
spur_list_search_automations | Scheduled property searches with their schedule, filters, and next/last run times. |
spur_create_search_automation | Schedule a recurring property search. Every run uses 1 search credit, or 2 when it makes more than 3 ZHomes calls (several event types, tax/sale-history events, furnished-only or description-based filters). New matches can be saved to a list and enriched automatically (auto_enrich spends skip-trace |
spur_run_search_automation | Run a search automation immediately instead of waiting for its schedule. Uses 1 search credit (2 if the run makes more than 3 ZHomes calls), and enrichment credits if auto_enrich is on. |
spur_get_automation_logs | Recent runs of a search automation: when, how many found/saved/enriched, and errors. |
search | Search the user's saved Spur properties, owners and postcard templates by keyword (address, city, owner name, phone, email, template name). Returns ids for the fetch tool. For live listings use spur_search_properties. |
fetch | Fetch the full text of a record returned by search (ids look like property:…, owner:… or template:…). |