# Spur (remote · mcp.usespur.com)

Real estate leads, skip tracing, direct mail, SMS & email outreach, and marketing automations

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `mcp.usespur.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-usespur-spur/mcp.md), [page](https://verifymcp.io/servers/com-usespur-spur/mcp)

## Channel facts

- Endpoint: `https://mcp.usespur.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 16491 tokens (~171/item across 96 items; 87 tools + 9 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 12 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 89 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Spur MCP server?

Spur is a hosted endpoint at https://mcp.usespur.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "com-usespur-spur": {
      "type": "http",
      "url": "https://mcp.usespur.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-usespur-spur]
url = "https://mcp.usespur.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-usespur-spur": {
      "type": "remote",
      "url": "https://mcp.usespur.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-usespur-spur --url 'https://mcp.usespur.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-usespur-spur:
    url: "https://mcp.usespur.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-usespur-spur": {
      "Transport": "http",
      "Url": "https://mcp.usespur.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-usespur-spur -t streamable-http -u 'https://mcp.usespur.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-usespur-spur": {
      "type": "http",
      "url": "https://mcp.usespur.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 86, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 81, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “spur_buy_phone_number”, which the server declares destructive
- [security] New tool “spur_pay_texting_fees”, which the server declares destructive
- [security] New tool “spur_release_phone_number”, which the server declares destructive
- [security] New tool “spur_submit_texting_registration”, which the server declares destructive
- [security] Tool “spur_send_sms” rewrote its description, which is the text the model reads
- [functional] New tool “spur_get_texting_setup”
- [functional] New tool “spur_resend_texting_verification”
- [functional] New tool “spur_save_texting_registration”
- [functional] New tool “spur_search_phone_numbers”
- [functional] New tool “spur_set_default_phone_number”

### 2026-10-26 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 80, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (87)

### `spur_search_properties` (~1632 tokens)

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, tax/sale-history events, or description-based filters). To check how a sentence will be interpreted before spending a credit, call spur_parse_search_query first.

Examples:
  \- "3 bed houses under $2,500/mo in Austin owned 10+ years" -> location="Austin, TX", listing_status="forRent", home_type="singleFamily", min_beds=3, max_price=2500, min_ownership_years=10
  \- "duplexes for sale in 78704 built before 1980 with absentee owners" -> location="78704", listing_status="forSale", home_type="multiFamily", max_year_built=1979, only_absentee=true
  \- "new pre-foreclosures or price drops of 10%+ in Dallas this week" -> location="Dallas, TX", events=["preforeclosure","price_drop"], event_within_days=7, event_min_change_pct=10
  \- "motivated sellers in Houston: stale, back on market, or fired their agent" -> location="Houston, TX", events=["stale_listing","back_on_market","agent_to_fsbo"]

Events (pass in `events`; a listing matches when ANY selected event fired, and is tagged with each):
\- Listing lifecycle: new_listing, coming_soon, coming_soon_active, price_drop, price_increase, pending, sold, back_on_market, delisted (automations only), open_house, rental_listed, rent_change, move_in_moved_up
\- Distress & motivation: preforeclosure, foreclosure, auction, bank_owned, distress_escalated, fsbo, agent_to_fsbo, stale_listing, new_construction
\- Valuation & tax: tax_assessment_posted, assessed_value_jump, tax_paid_dropped (weak), sale_recorded, zestimate_moved, equity_gap, price_below_assessed
Direct events (price_drop, pending, sold, preforeclosure, fsbo, new_listing, …) work on the first search. Change events (price_increase, back_on_market, distress_escalated, agent_to_fsbo, re…

Input parameters:

- `center_lat` (number): Radius search centre (with center_lng and radius_miles)
- `center_lng` (number): Radius search centre longitude (with center_lat and radius_miles)
- `days_posted` (integer): Only listings posted within this many days
- `event_min_change_pct` (number): Minimum % move for price / rent / Zestimate / assessment events
- `event_min_equity_gap_pct` (number): Minimum % Zestimate above last sale price for equity_gap (default 30)
- `event_stale_days` (integer): Days on market that counts as stale (default 90)
- `event_within_days` (integer): Lookback window for events, in days (default 7)
- `events` (array): Only listings where any of these events happened; see the tool description
- `has_3d_tour` (boolean): true = only listings with a 3D virtual tour
- `has_air_conditioning` (boolean): true = only listings with air conditioning
- `has_garage` (boolean): true = only listings with a garage
- `has_open_house` (boolean): true = only listings with an upcoming open house
- `has_pool` (boolean): true = only listings with a pool
- `has_view` (boolean): true = only listings with any view (use views on live search for a specific kind)
- `home_type` (string): Zillow home type code
- `is_price_reduced` (boolean): true = only listings whose asking price has been cut
- `is_single_story` (boolean): true = only single-story homes
- `is_waterfront` (boolean): true = only waterfront listings
- `keywords` (string): Comma-separated listing keywords, e.g. "pool, granite"
- `limit` (integer): Maximum results to show
- `listing_status` (string): Defaults to forRent when omitted and the query doesn't imply one
- `listing_type` (string): Seller / listing kind; for catching NEW entries into a distress stage prefer events
- `location` (string): City and state ("Dallas, TX") or ZIP code
- `max_age` (integer): At most this many years since built
- `max_baths` (number): Maximum bathrooms
- `max_beds` (integer): Maximum bedrooms
- `max_days_on_market` (integer): Listed at most this many days
- `max_lot_size` (integer): Square feet
- `max_ownership_years` (number): Owner has held the property at most this long
- `max_price` (number): Maximum price (monthly rent for rentals), USD
- `max_sqft` (integer): Maximum living area in square feet
- `max_year_built` (integer): Built in or before this year
- `max_zip` (integer): Highest ZIP code in a numeric ZIP range (with min_zip)
- `min_age` (integer): Years since built
- `min_baths` (number): Minimum bathrooms (half baths count as 0.5)
- `min_beds` (integer): Minimum bedrooms
- `min_days_on_market` (integer): Listed at least this many days (higher suggests a motivated seller)
- `min_equity` (number): Estimated equity in USD (Zestimate or price minus assessed value; rough)
- `min_lot_size` (integer): Square feet (1 acre = 43,560)
- `min_ownership_years` (number): Owner has held the property at least this long
- `min_price` (number): Minimum price (monthly rent for rentals), USD
- `min_sqft` (integer): Minimum living area in square feet
- `min_year_built` (integer): Built in or after this year
- `min_zip` (integer): Lowest ZIP code in a numeric ZIP range (with max_zip); prefer zip_list for specific ZIPs
- `neighborhoods` (array): Neighborhood / area names matched against address and description
- `only_absentee` (boolean): Absentee-owned (owner mails elsewhere)
- `only_pre_foreclosure` (boolean): Distressed / pre-foreclosure (heuristic, includes description keywords)
- `only_vacant` (boolean): Likely vacant (heuristic: description keywords + long days on market)
- `ownership_type` (string): business = LLC / corp / trust owners (heuristic)
- `query` (string): Free-text intent; Spur's AI turns it into filters and re-ranks by description
- `radius_miles` (number): Keep only listings within this many miles of center_lat / center_lng
- `views` (array): Only listings with any of these view types
- `zip_list` (array): Keep only these ZIPs; set location to the city that contains them

### `spur_parse_search_query` (~116 tokens)

Preview search filters

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_search_properties (keep the same location / status unless the user says otherwise). Exclusions ("no condos", "not foreclosures") are honoured by leaving those filters out.

Input parameters:

- `query` (string, required): The user's search in their own words

### `spur_get_property` (~71 tokens)

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.

Input parameters:

- `property_id` (string): Saved Spur property id
- `zpid` (string|number): Zillow property id from search results

### `spur_save_properties` (~89 tokens)

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.

Input parameters:

- `list_id` (string): Also add the saved properties to this property list (spur_list_property_lists)
- `listings` (array, required): Listing objects copied unchanged from spur_search_properties structuredContent.cards[].listing

### `spur_list_saved_properties` (~167 tokens)

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.

Input parameters:

- `city` (string): City name, e.g. "Austin"
- `enrichment_status` (string): Skip-trace status of the property's owner (spur_enrich)
- `limit` (integer): Maximum number of items to return
- `list_id` (string): Only properties in this property list
- `max_price` (number): Maximum price in USD (rent per month for rentals)
- `min_price` (number): Minimum price in USD (rent per month for rentals)
- `offset` (integer): Number of items to skip, for pagination
- `state` (string): Two-letter state, e.g. "TX"

### `spur_get_property_stats` (~30 tokens)

Property stats

Totals for the user's saved properties: counts by status, enrichment progress and similar portfolio-level numbers.

### `spur_find_owners` (~118 tokens)

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.

Input parameters:

- `enrichment_status` (string): Only owners with this skip-trace status
- `has_phone` (boolean): Only owners with at least one phone number
- `limit` (integer): Maximum number of items to return
- `offset` (integer): Number of items to skip, for pagination
- `query` (string): Text to match against name, email, phone or mailing address

### `spur_get_owner` (~46 tokens)

Get owner

Full owner record: contact details, mailing address, enrichment status and their property portfolio in Spur.

Input parameters:

- `owner_id` (string, required): Owner id (UUID from a Spur list/search tool)

### `spur_enrich` (~144 tokens)

Skip trace / 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 the user to approve the count first, then call with confirm=true.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `owner_ids` (array): Owner ids to skip-trace (from spur_find_owners)
- `property_ids` (array): Saved property ids whose owners to skip-trace

### `spur_list_property_lists` (~39 tokens)

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` (~66 tokens)

Create property list

Create a property list, optionally seeding it with saved property ids.

Input parameters:

- `description` (string): Optional note about what the list is for
- `name` (string, required): List name shown in Spur
- `property_ids` (array): Saved property ids to add right away

### `spur_add_properties_to_list` (~60 tokens)

Add properties to list

Add saved properties to an existing property list.

Input parameters:

- `list_id` (string, required): Property list id (UUID from a Spur list/search tool)
- `property_ids` (array, required): Saved property ids (from spur_list_saved_properties or spur_save_properties)

### `spur_draft_message` (~155 tokens)

Draft outreach 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://merge-variables).

Input parameters:

- `channel` (string, required): Which kind of message to draft
- `owner_id` (string): Owner to personalize for (from spur_find_owners)
- `prompt` (string, required): What to write, e.g. "friendly first touch asking if they would sell, mention we close in cash"
- `property_id` (string): Saved property the message is about

### `spur_list_workflows` (~29 tokens)

List outreach workflows

The user's multi-step outreach workflows (email/SMS/mail sequences) with status and enrollment counts.

### `spur_get_workflow` (~62 tokens)

Get outreach 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.

Input parameters:

- `workflow_id` (string, required): Workflow id (UUID from a Spur list/search tool)

### `spur_create_workflow` (~238 tokens)

Create outreach 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_template / spur_create_sms_template), direct mail from the user's saved postcard or letter templates. Wait steps space them out. Reply/open/click branches can be added afterwards in Spur → Outreach.

Example: "text, wait 2 days, email, wait 5 days, postcard" -> steps=[{type:"send_sms",template_id:…},{type:"wait",days:2},{type:"send_email",template_id:…},{type:"wait",days:5},{type:"send_direct_mail",template_id:…}]

Input parameters:

- `description` (string): Optional note about the workflow's goal
- `name` (string, required): Workflow name shown in Spur
- `steps` (array, required): Steps in run order: send_email / send_sms / send_direct_mail with a saved template_id, and wait steps (days, hours) between them

### `spur_set_workflow_step_template` (~121 tokens)

Use template in workflow step

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.

Input parameters:

- `step_id` (string, required): step_id from spur_get_workflow
- `template_id` (string, required): Template id (UUID from a Spur list/search tool)
- `workflow_id` (string, required): Workflow id (UUID from a Spur list/search tool)

### `spur_set_workflow_active` (~108 tokens)

Activate or pause workflow

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.

Input parameters:

- `active` (boolean, required): true = activate (start sending), false = pause
- `confirm` (boolean): Required (true) when activating, only after the user approved it
- `workflow_id` (string, required): Workflow id (UUID from a Spur list/search tool)

### `spur_enroll_owners_in_workflow` (~123 tokens)

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.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `owner_ids` (array, required): Owner ids to enroll (from spur_find_owners); owners without the needed contact details are skipped
- `workflow_id` (string, required): Workflow id (UUID from a Spur list/search tool)

### `spur_send_sms` (~137 tokens)

Send SMS

Text 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=true. Billed per 160-character segment (70 if it has emoji or special characters), so a 200-character text costs 2.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `message` (string, required): Exact SMS text the user approved
- `owner_id` (string, required): Owner id (UUID from a Spur list/search tool)

### `spur_list_sms_conversations` (~68 tokens)

SMS inbox

SMS conversations with owners, newest first, with unread counts and the last message. Good for triaging replies (hot leads, not interested, wrong number).

Input parameters:

- `limit` (integer): Maximum conversations to return
- `unread_only` (boolean): true = only conversations with unread replies

### `spur_get_sms_conversation` (~40 tokens)

SMS thread

The full SMS thread with one owner, oldest first.

Input parameters:

- `owner_id` (string, required): Owner id (UUID from a Spur list/search tool)

### `spur_get_outreach_report` (~86 tokens)

Outreach report

Outreach performance (sent, delivered, opened, replied, by channel) for all workflows or one, over an optional date range.

Input parameters:

- `date_from` (string): ISO date, e.g. 2026-10-01
- `date_to` (string): ISO date
- `workflow_id` (string): Report on one workflow only; omit for all workflows

### `spur_list_message_templates` (~48 tokens)

List email and SMS templates

The user's saved email and SMS templates. These are what outreach workflow send_email / send_sms steps use.

Input parameters:

- `channel` (string): Only email or only SMS templates; omit for both

### `spur_get_message_template` (~69 tokens)

Get email or SMS 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.

Input parameters:

- `template_id` (string, required): Email or SMS template id (UUID from a Spur list/search tool)

### `spur_preview_message_template` (~94 tokens)

Preview email or SMS 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.

Input parameters:

- `owner_id` (string): Preview with this owner's real data (spur_find_owners) instead of sample data
- `template_id` (string, required): Email or SMS template id (UUID from a Spur list/search tool)

### `spur_preview_message_draft` (~492 tokens)

Preview unsaved email or SMS

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-based layout 600px wide, inline styles on elements (a small <style> block in <head> is fine for resets/media queries), web-safe font stacks, no JavaScript, no forms, no external CSS. Images as absolute https URLs with alt text and width attributes. The user's own images (logo, headshot, property photos): spur_list_images gives their URLs; if they want to use an image they have, call spur_upload_image (or spur_save_image for a link) and use the saved URL. Use PNG or JPG in emails, not SVG. A hidden preheader <div style="display:none"> right after <body> sets the inbox snippet. Include an opt-out line ("Reply STOP" or an unsubscribe link) and the sender's postal address in the footer. Keep it under 50,000 characters. Use merge fields like {{owner_first_name}}, {{property_address}}, {{your_name}}, {{your_phone}}, {{company_name}} (see spur://merge-variables). The plain-text version is generated from the HTML unless you pass text_body.

SMS guidance: plain text, ideally one segment (160 GSM characters, or 70 if it uses emoji or other non-GSM characters; longer messages are billed per segment). Identify yourself, keep it conversational, and include opt-out wording ("Reply STOP to opt out") on first-touch messages. Links in texts from unverified numbers can be blocked, so give link-free fallback_body text when the body has a URL. Use merge fields like {{owner_first_name}}, {{property_address}}, {{your_name}} (see spur://merge-variables).

Input parameters:

- `channel` (string, required): Whether the draft is an email or an SMS
- `fallback_body` (string): SMS only: link-free text sent if links are blocked
- `html` (string): Email HTML
- `owner_id` (string): Preview with this owner's real data (spur_find_owners) instead of sample data
- `subject` (string): Email subject
- `text` (string): SMS text, or the email's plain-text version

### `spur_create_email_template` (~480 tokens)

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 scratch: pass html (or only text_body for a plain-text email).
The saved template can then be used by outreach workflows (spur_create_workflow / spur_set_workflow_step_template).

Email HTML guidance (see spur://email-design-guide): full HTML document, table-based layout 600px wide, inline styles on elements (a small <style> block in <head> is fine for resets/media queries), web-safe font stacks, no JavaScript, no forms, no external CSS. Images as absolute https URLs with alt text and width attributes. The user's own images (logo, headshot, property photos): spur_list_images gives their URLs; if they want to use an image they have, call spur_upload_image (or spur_save_image for a link) and use the saved URL. Use PNG or JPG in emails, not SVG. A hidden preheader <div style="display:none"> right after <body> sets the inbox snippet. Include an opt-out line ("Reply STOP" or an unsubscribe link) and the sender's postal address in the footer. Keep it under 50,000 characters. Use merge fields like {{owner_first_name}}, {{property_address}}, {{your_name}}, {{your_phone}}, {{company_name}} (see spur://merge-variables). The plain-text version is generated from the HTML unless you pass text_body.

Input parameters:

- `base_template_id` (string): Copy this email template as the starting point
- `description` (string): Internal note about the template; never sent to owners
- `html` (string): Full email HTML; merge fields like {{owner_first_name}} are filled per recipient
- `is_default` (boolean): Make this the user's default email template
- `name` (string, required): Template name shown in Spur
- `start_from_blank` (boolean): true = start from Spur's responsive, compliant blank email layout
- `subject` (string): Required unless copying a template
- `text_body` (string): Plain-text version; generated from the HTML when omitted

### `spur_update_email_template` (~499 tokens)

Edit 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. Workflows using this template send the new version from their next step.

Example: replacements=[{target:"html", find:"<p style=\"margin:0 0 16px;\"></p>", replace:"<p style=\"margin:0 0 16px;\">I'd like to make a cash offer on {{property_address}}.</p>"}]

Email HTML guidance (see spur://email-design-guide): full HTML document, table-based layout 600px wide, inline styles on elements (a small <style> block in <head> is fine for resets/media queries), web-safe font stacks, no JavaScript, no forms, no external CSS. Images as absolute https URLs with alt text and width attributes. The user's own images (logo, headshot, property photos): spur_list_images gives their URLs; if they want to use an image they have, call spur_upload_image (or spur_save_image for a link) and use the saved URL. Use PNG or JPG in emails, not SVG. A hidden preheader <div style="display:none"> right after <body> sets the inbox snippet. Include an opt-out line ("Reply STOP" or an unsubscribe link) and the sender's postal address in the footer. Keep it under 50,000 characters. Use merge fields like {{owner_first_name}}, {{property_address}}, {{your_name}}, {{your_phone}}, {{company_name}} (see spur://merge-variables). The plain-text version is generated from the HTML unless you pass text_body.

Input parameters:

- `description` (string): Internal note about the template; never sent to owners
- `html` (string): Full replacement HTML
- `is_default` (boolean): true = make this the user's default template for its channel
- `name` (string): New template name
- `replacements` (array): Small edits applied in order instead of resending the full content
- `subject` (string): New subject line
- `template_id` (string, required): Email or SMS template id (UUID from a Spur list/search tool)
- `text_body` (string): Full replacement plain-text version

### `spur_create_sms_template` (~247 tokens)

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 non-GSM characters; longer messages are billed per segment). Identify yourself, keep it conversational, and include opt-out wording ("Reply STOP to opt out") on first-touch messages. Links in texts from unverified numbers can be blocked, so give link-free fallback_body text when the body has a URL. Use merge fields like {{owner_first_name}}, {{property_address}}, {{your_name}} (see spur://merge-variables).

Input parameters:

- `description` (string): Internal note about the template; never sent to owners
- `fallback_body` (string): Link-free version sent if a link gets the text blocked
- `is_default` (boolean): true = make this the user's default template for its channel
- `name` (string, required): Template name shown in Spur
- `text` (string, required): SMS body; merge fields like {{owner_first_name}} are filled per recipient

### `spur_update_sms_template` (~281 tokens)

Edit 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 or other non-GSM characters; longer messages are billed per segment). Identify yourself, keep it conversational, and include opt-out wording ("Reply STOP to opt out") on first-touch messages. Links in texts from unverified numbers can be blocked, so give link-free fallback_body text when the body has a URL. Use merge fields like {{owner_first_name}}, {{property_address}}, {{your_name}} (see spur://merge-variables).

Input parameters:

- `description` (string): Internal note about the template; never sent to owners
- `fallback_body` (string): Link-free text sent instead when links are blocked; "" removes it
- `is_default` (boolean): true = make this the user's default template for its channel
- `name` (string): New template name
- `replacements` (array): Small edits applied in order instead of resending the full content
- `template_id` (string, required): Email or SMS template id (UUID from a Spur list/search tool)
- `text` (string): Full replacement SMS body

### `spur_delete_message_template` (~93 tokens)

Delete email or SMS 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.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `template_id` (string, required): Email or SMS template id (UUID from a Spur list/search tool)

### `spur_send_test_email` (~147 tokens)

Send test email to yourself

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.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `owner_id` (string): Preview with this owner's real data (spur_find_owners) instead of sample data
- `sender_id` (string): Email sender to send from; defaults to the user's default sender
- `template_id` (string, required): Email or SMS template id (UUID from a Spur list/search tool)

### `spur_list_postcard_templates` (~109 tokens)

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.

Input parameters:

- `category` (string): Only templates in this category, e.g. "Just Sold"
- `include_gallery` (boolean): Include Spur's built-in gallery designs
- `size` (string): Only templates designed for this size

### `spur_get_postcard_template` (~81 tokens)

Get postcard template HTML

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.

Input parameters:

- `side` (string): Which side's HTML to return
- `template_id` (string, required): Template id from spur_list_postcard_templates (a saved template's UUID or a Spur gallery id)

### `spur_preview_postcard_template` (~63 tokens)

Preview postcard template

Show any postcard template (yours, a Spur default or a gallery design) rendered with sample data, without changing anything.

Input parameters:

- `template_id` (string, required): Template id from spur_list_postcard_templates (a saved template's UUID or a Spur gallery id)

### `spur_create_postcard_template` (~727 tokens)

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) copies its HTML; override front_html/back_html/size as needed.
\- From scratch: pass both front_html and back_html.

HTML guidance (see spur://postcard-design-guide): full HTML documents, inline <style>, no scripts. Fixed pixel sizing on html, body and a root .postcard at 300 px/in including 0.125" bleed: 6x4 → 1875×1275, 6x9 → 2775×1875, 6x11 → 3375×1875. Keep text 0.25" inside the edge. USPS clear zone on the back, measured from the bleed edges (Spur prints over it and covers anything there): postage 1.25"×1.25" in the top-right corner; address block 3.5"×2", 0.5" from the right edge and 1.35" from the top; USPS barcode strip 4.75"×0.625" along the bottom-right edge. Keep all text, logos, photos and QR codes out of it; a background color or texture under it is fine. The safe message area is left of the address block and above the barcode strip. Images as absolute https URLs. The user's own images (logo, headshot, property photos): spur_list_images gives their URLs; if they want to use an image they have, call spur_upload_image (or spur_save_image for a link) and use the saved URL. Use merge fields such as {{owner_first_name}}, {{property_address}}, {{your_name}}, {{your_phone}}, {{company_name}} (see spur://merge-variables). QR code box by default: unless the user says they don't want a QR code, every back you design includes an empty square <div class="qr-box"> in the message area (≥ 0.75in, e.g. 225×225 px at 300 px/in) with a short call to action beside it ("Scan to see your home's value"). Never write QR markup or {{qrUrl}} yourself: after saving, call spur_add_postcard_qr_code and the tracked QR fills the box (pick the code with spur_list_qr_codes, or ask the user…

Input parameters:

- `back_html` (string): Full back-side HTML; keep the address block area clear
- `base_template_id` (string): Copy this template's HTML and size as the starting point
- `category` (string): Category label, e.g. "Just Sold" or "Market Update"
- `description` (string): Internal note about the template; never printed
- `front_html` (string): Full front-side HTML
- `name` (string, required): Template name shown in Spur
- `size` (string): Postcard size: "6x4" (standard 4×6), "6x9" or "6x11"
- `start_from_blank` (boolean): Start from an empty canvas sized for `size`

### `spur_update_postcard_template` (~709 tokens)

Edit 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_template_id.

Example: change the headline -> replacements=[{side:"front", find:"Just Sold!", replace:"Just Listed!"}]

HTML guidance (see spur://postcard-design-guide): full HTML documents, inline <style>, no scripts. Fixed pixel sizing on html, body and a root .postcard at 300 px/in including 0.125" bleed: 6x4 → 1875×1275, 6x9 → 2775×1875, 6x11 → 3375×1875. Keep text 0.25" inside the edge. USPS clear zone on the back, measured from the bleed edges (Spur prints over it and covers anything there): postage 1.25"×1.25" in the top-right corner; address block 3.5"×2", 0.5" from the right edge and 1.35" from the top; USPS barcode strip 4.75"×0.625" along the bottom-right edge. Keep all text, logos, photos and QR codes out of it; a background color or texture under it is fine. The safe message area is left of the address block and above the barcode strip. Images as absolute https URLs. The user's own images (logo, headshot, property photos): spur_list_images gives their URLs; if they want to use an image they have, call spur_upload_image (or spur_save_image for a link) and use the saved URL. Use merge fields such as {{owner_first_name}}, {{property_address}}, {{your_name}}, {{your_phone}}, {{company_name}} (see spur://merge-variables). QR code box by default: unless the user says they don't want a QR code, every back you design includes an empty square <div class="qr-box"> in the message area (≥ 0.75in, e.g. 225×225 px at 300 px/in) with a short call to action beside it ("Scan to see your home's value"). Never write QR markup or {{qrUrl}} yourself: after saving, call spur_add_postcard_qr_code and the tracked QR fills the box (pick the code with spur_list_qr_codes, or ask the user whe…

Input parameters:

- `back_html` (string): Full replacement back HTML
- `category` (string): Category label, e.g. "Just Sold" or "Market Update"
- `description` (string): Internal note about the template; never printed
- `front_html` (string): Full replacement front HTML
- `name` (string): New template name
- `replacements` (array): Small edits applied in order instead of resending the full content
- `size` (string): Postcard size: "6x4" (standard 4×6), "6x9" or "6x11"
- `template_id` (string, required): Template id (UUID from a Spur list/search tool)

### `spur_add_postcard_qr_code` (~353 tokens)

Add QR code to postcard

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 qr-box, qr-code-box, qr-placeholder or qr-callout-box, as Spur's gallery designs have) and otherwise goes in the bottom-right of the message area, left of the address block and above the USPS barcode. Corners (top_left, top_right, bottom_left, bottom_right) and x_inches/y_inches place it in the message area; spots in the USPS clear zone are refused. Replaces any QR already on the card. If it lands on the message text, call again with another corner or move the text.

Create a QR code first with spur_create_qr_code if spur_list_qr_codes has none that fits.

Input parameters:

- `position` (string): Where to place the code on the back; auto fills the design's qr-box
- `qr_code_id` (string, required): QR code id from spur_list_qr_codes or spur_create_qr_code
- `size_inches` (number): Edge length when placed in the message area (not used for a slot). 0.75in or more scans reliably
- `template_id` (string, required): Postcard template id (UUID from a Spur list/search tool)
- `x_inches` (number): Left edge, inches from the bleed's left edge (with y_inches; overrides position)
- `y_inches` (number): Top edge, inches from the bleed's top edge (with x_inches)

### `spur_remove_postcard_qr_code` (~64 tokens)

Remove QR code from postcard

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.

Input parameters:

- `template_id` (string, required): Postcard template id (UUID from a Spur list/search tool)

### `spur_delete_postcard_template` (~77 tokens)

Delete postcard template

Permanently delete one of the user's postcard templates. Spur defaults can't be deleted. Confirm with the user first.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `template_id` (string, required): Template id (UUID from a Spur list/search tool)

### `spur_list_return_addresses` (~29 tokens)

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` (~171 tokens)

Preview postcard mailing

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 spur_send_postcards with the token (the widget's Send button does the same). The token expires in 30 minutes and only covers this exact template, recipient set, return address and size.

Input parameters:

- `owner_ids` (array, required): Owners to mail (spur_find_owners)
- `return_address_id` (string): Defaults to the user's default return address
- `size` (string): Defaults to the template's size
- `template_id` (string, required): Postcard template id (UUID from a Spur list/search tool)

### `spur_send_postcards` (~87 tokens)

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).

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `confirmation_token` (string, required): confirmation_token from spur_preview_postcard_campaign

### `spur_list_qr_codes` (~56 tokens)

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` (~163 tokens)

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.

Input parameters:

- `background_color` (string): Hex color, e.g. #111827. Keep strong contrast with the background so phones can scan it
- `destination_url` (string, required): Where a scan sends people, e.g. https://acme.example/offer (https:// is added if missing)
- `foreground_color` (string): Hex color, e.g. #111827. Keep strong contrast with the background so phones can scan it
- `name` (string, required): Label shown in Spur, e.g. 'Spring cash offer'

### `spur_update_qr_code` (~168 tokens)

Edit 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.

Input parameters:

- `background_color` (string): Hex color, e.g. #111827. Keep strong contrast with the background so phones can scan it
- `destination_url` (string): Where a scan sends people, e.g. https://acme.example/offer (https:// is added if missing)
- `foreground_color` (string): Hex color, e.g. #111827. Keep strong contrast with the background so phones can scan it
- `name` (string): New name for the QR code
- `qr_code_id` (string, required): QR code id from spur_list_qr_codes

### `spur_delete_qr_code` (~103 tokens)

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.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `qr_code_id` (string, required): QR code id from spur_list_qr_codes

### `spur_get_qr_code_activity` (~81 tokens)

QR code scans

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.

Input parameters:

- `limit` (integer): Maximum recipients and scans to list
- `qr_code_id` (string, required): QR code id from spur_list_qr_codes

### `spur_list_images` (~88 tokens)

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).

Input parameters:

- `limit` (integer): Maximum images to return

### `spur_save_image` (~127 tokens)

Save image from URL

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_image instead. Only save images the user provided or asked for.

Input parameters:

- `filename` (string): Name to save it under, e.g. 'acme-logo'
- `url` (string, required): Public https URL of the image

### `spur_upload_image` (~125 tokens)

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 into the box. After uploading, the user can click "Use this image", or call spur_list_images to get the URL.

Input parameters:

- `purpose` (string): What the image is for, shown to the user, e.g. 'Logo for the postcard back'

### `spur_save_uploaded_image` (~54 tokens)

Save uploaded image

Used by the upload widget to save the file the user picked. Not for the assistant.

Input parameters:

- `data_base64` (string, required): File contents, base64-encoded
- `filename` (string, required): Original file name

### `spur_delete_image` (~89 tokens)

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.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `image_id` (string, required): image_id from spur_list_images

### `spur_list_letter_templates` (~109 tokens)

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.

Input parameters:

- `category` (string): Only templates in this category
- `include_gallery` (boolean): Include Spur's built-in gallery designs
- `letter_type` (string): Only templates of this letter type

### `spur_get_letter_template` (~66 tokens)

Get letter template HTML

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.

Input parameters:

- `template_id` (string, required): Template id from spur_list_letter_templates (a saved template's UUID or a Spur gallery id)

### `spur_preview_letter_template` (~61 tokens)

Preview letter template

Show any letter template (yours, a Spur default or a gallery design) rendered with sample data, without changing anything.

Input parameters:

- `template_id` (string, required): Template id from spur_list_letter_templates (a saved template's UUID or a Spur gallery id)

### `spur_create_letter_template` (~479 tokens)

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 letter type.
\- Redesign an existing template: base_template_id (yours, a Spur default or a gallery id) copies its HTML and letter type; override html or letter_type as needed.
\- From scratch: pass html.

HTML guidance (see spur://letter-design-guide): one US Letter page (8.5"×11"), full HTML document with inline <style>, "@page { size: 8.5in 11in; margin: 0; }", no scripts. One root <div class="letter"> 8.5in wide; px/in units only (no vh/vw); no box-shadow, transforms or manual page breaks. top_first_page: leave the first 3.15in blank (an empty <div class="address-zone" style="height:3.15in">), body ≈ 3–4 short paragraphs. insert_blank_page: no address zone; letterhead up to 1.8in, body up to ~400 words. Images as absolute https URLs. The user's own images (logo, headshot, property photos): spur_list_images gives their URLs; if they want to use an image they have, call spur_upload_image (or spur_save_image for a link) and use the saved URL. Use merge fields such as {{owner_first_name}}, {{property_address}}, {{your_name}}, {{your_phone}}, {{company_name}} (see spur://merge-variables).

Input parameters:

- `base_template_id` (string): Copy this template's HTML and letter type as the starting point
- `category` (string): Category label, e.g. "Seller Outreach"
- `description` (string): Internal note about the template; never printed
- `html` (string): Full letter HTML
- `letter_type` (string): Defaults to the base template's type, else top_first_page
- `name` (string, required): Template name shown in Spur
- `start_from_blank` (boolean): Start from an empty page laid out for letter_type

### `spur_update_letter_template` (~479 tokens)

Edit 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 spur_create_letter_template base_template_id.

HTML guidance (see spur://letter-design-guide): one US Letter page (8.5"×11"), full HTML document with inline <style>, "@page { size: 8.5in 11in; margin: 0; }", no scripts. One root <div class="letter"> 8.5in wide; px/in units only (no vh/vw); no box-shadow, transforms or manual page breaks. top_first_page: leave the first 3.15in blank (an empty <div class="address-zone" style="height:3.15in">), body ≈ 3–4 short paragraphs. insert_blank_page: no address zone; letterhead up to 1.8in, body up to ~400 words. Images as absolute https URLs. The user's own images (logo, headshot, property photos): spur_list_images gives their URLs; if they want to use an image they have, call spur_upload_image (or spur_save_image for a link) and use the saved URL. Use merge fields such as {{owner_first_name}}, {{property_address}}, {{your_name}}, {{your_phone}}, {{company_name}} (see spur://merge-variables).

Input parameters:

- `category` (string): Category label, e.g. "Seller Outreach"
- `description` (string): Internal note about the template; never printed
- `html` (string): Full replacement HTML
- `letter_type` (string): "top_first_page": the address prints in the top 3.15in of page 1 (shows through a #10 window envelope), so keep that band empty. "insert_blank_page": Spur adds a separate address page in front, so th…
- `name` (string): New template name
- `replacements` (array): Small edits applied in order instead of resending the full content
- `template_id` (string, required): Template id (UUID from a Spur list/search tool)

### `spur_delete_letter_template` (~76 tokens)

Delete letter template

Permanently delete one of the user's letter templates. Spur defaults can't be deleted. Confirm with the user first.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `template_id` (string, required): Template id (UUID from a Spur list/search tool)

### `spur_preview_letter_campaign` (~207 tokens)

Preview letter mailing

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.

Show the preview, then ask the user to approve. Only after they approve, call spur_send_letters with the token (the widget's Send button does the same). The token expires in 30 minutes and only covers this exact template, letter type, print options, recipient set and return address.

Input parameters:

- `color` (boolean): Print in color (false for black and white)
- `double_sided` (boolean): Print on both sides of each sheet
- `owner_ids` (array, required): Owners to mail (spur_find_owners)
- `return_address_id` (string): Defaults to the user's default return address
- `template_id` (string, required): Letter template id (UUID from a Spur list/search tool)

### `spur_send_letters` (~84 tokens)

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).

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `confirmation_token` (string, required): confirmation_token from spur_preview_letter_campaign

### `spur_get_billing_summary` (~46 tokens)

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` (~67 tokens)

List campaigns

The user's campaigns (bulk email, SMS, direct mail, outreach) with status and recipient progress.

Input parameters:

- `limit` (integer): Maximum campaigns to return
- `offset` (integer): Campaigns to skip, for paging
- `status` (string): Only campaigns with this status

### `spur_get_campaign_stats` (~36 tokens)

Campaign stats

Delivery and run statistics for one campaign.

Input parameters:

- `campaign_id` (string, required): Campaign id (UUID from a Spur list/search tool)

### `spur_get_direct_mail_analytics` (~31 tokens)

Direct mail analytics

Letters and postcards sent, delivered, in transit and returned, plus USPS tracking totals and spend.

### `spur_show_billing_options` (~70 tokens)

Top up or upgrade

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` (~103 tokens)

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 cover the send they're planning.

Input parameters:

- `amount_usd` (number, required): Amount to add in US dollars (minimum $5)

### `spur_change_plan` (~180 tokens)

Upgrade or 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 saved card. Call once without confirm to get the exact change, ask the user to approve it, then call again with confirm=true.
\- Moving to the free Solo plan returns a billing-portal link where the user cancels the paid subscription.

Input parameters:

- `billing_interval` (string): annual is cheaper per month
- `confirm` (boolean): Only for users who already have a paid subscription: true ONLY after they approved the switch and the prorated charge in the conversation.
- `plan_id` (string, required): Target plan id, e.g. agent, team, brokerage

### `spur_check_payment` (~65 tokens)

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.

Input parameters:

- `session_id` (string, required): session_id returned with the checkout link (starts with cs_)

### `spur_manage_billing` (~33 tokens)

Billing portal

Link to the user's Stripe billing portal: update the card on file, download invoices, change or cancel the subscription.

### `spur_set_auto_recharge` (~175 tokens)

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 threshold (confirm=true); turning it off doesn't.

Input parameters:

- `amount_usd` (number): Amount added per recharge (required when enabling, minimum $5)
- `confirm` (boolean): Required to enable: true ONLY after the user approved automatic charges of this amount at this threshold.
- `enabled` (boolean, required): true = turn auto-recharge on, false = off
- `threshold_usd` (number): Recharge when the balance drops below this (required when enabling; lower than amount_usd)

### `spur_list_search_automations` (~28 tokens)

List search automations

Scheduled property searches with their schedule, filters, and next/last run times.

### `spur_create_search_automation` (~1608 tokens)

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 credits on every run, so confirm with the user).

Examples:
  \- "every Monday 8am Central, Dallas rentals under $2k" -> frequency="weekly", day_of_week=1, run_time="08:00", timezone="America/Chicago", location="Dallas, TX", max_amount=2000
  \- "last Friday of each month" -> frequency="monthly", day_of_week=5, week_of_month=-1
  \- "every morning, new pre-foreclosures and price drops in Houston, save to my Distress list" -> frequency="daily", run_time="07:00", location="Houston, TX", events=["preforeclosure","price_drop"], list_id=…

Accepts the same advanced and event filters as spur_search_properties (min_amount / max_amount instead of min_price / max_price). Run the search once with spur_search_properties first so the user can check the results before scheduling.

In automations each event fires once, on the run that first sees it, so the same property isn't saved twice; change events start reporting from the second run. "delisted" is only available here.

Events (pass in `events`; a listing matches when ANY selected event fired, and is tagged with each):
\- Listing lifecycle: new_listing, coming_soon, coming_soon_active, price_drop, price_increase, pending, sold, back_on_market, delisted (automations only), open_house, rental_listed, rent_change, move_in_moved_up
\- Distress & motivation: preforeclosure, foreclosure, auction, bank_owned, distress_escalated, fsbo, agent_to_fsbo, stale_listing, new_construction
\- Valuation & tax: tax_assessment_posted, assessed_value_jump, tax_paid_dropped (weak), sale_recorded, zestimate_moved, equity_gap, price_below_assessed
Direct events (price_drop, pending, sold, preforeclosure, fsbo, new_listing, …) work on the first search. Change…

Input parameters:

- `ai_query` (string): Qualitative intent; each run re-ranks listings by description against it
- `auto_enrich` (boolean): Skip-trace new matches on every run (spends enrichment credits)
- `auto_save` (boolean): Save new matches to the user's properties
- `center_lat` (number): Radius search centre (with center_lng and radius_miles)
- `center_lng` (number): Radius search centre longitude (with center_lat and radius_miles)
- `day_of_week` (integer): 0=Sunday … 6=Saturday; for weekly, biweekly, monthly
- `days_posted` (integer): Only listings posted within this many days
- `enabled` (boolean): false = save it paused
- `event_min_change_pct` (number): Minimum % move for price / rent / Zestimate / assessment events
- `event_min_equity_gap_pct` (number): Minimum % Zestimate above last sale price for equity_gap (default 30)
- `event_stale_days` (integer): Days on market that counts as stale (default 90)
- `event_within_days` (integer): Lookback window for events, in days (default 7)
- `events` (array): Only listings where any of these events happened; see the tool description
- `frequency` (string, required): How often the search runs
- `has_garage` (boolean): true = only listings with a garage
- `has_pool` (boolean): true = only listings with a pool
- `has_view` (boolean): true = only listings with any view (use views on live search for a specific kind)
- `home_type` (string): Zillow home type code
- `is_price_reduced` (boolean): true = only listings whose asking price has been cut
- `is_waterfront` (boolean): true = only waterfront listings
- `keywords` (string): Comma-separated listing keywords, e.g. "pool, granite"
- `list_id` (string): Save new matches into this property list
- `listing_status` (string): Which listings to search
- `listing_type` (string): Seller / listing kind; for catching NEW entries into a distress stage prefer events
- `location` (string, required): City/state or ZIP, e.g. "Dallas, TX"
- `max_age` (integer): At most this many years since built
- `max_amount` (number): Maximum price in USD (rent per month for forRent)
- `max_baths` (number): Maximum bathrooms
- `max_beds` (integer): Maximum bedrooms
- `max_days_on_market` (integer): Listed at most this many days
- `max_lot_size` (integer): Square feet
- `max_ownership_years` (number): Owner has held the property at most this long
- `max_sqft` (integer): Maximum living area in square feet
- `max_year_built` (integer): Built in or before this year
- `max_zip` (integer): Highest ZIP code in a numeric ZIP range (with min_zip)
- `min_age` (integer): Years since built
- `min_amount` (number): Minimum price in USD (rent per month for forRent)
- `min_baths` (number): Minimum bathrooms (half baths count as 0.5)
- `min_beds` (integer): Minimum bedrooms
- `min_days_on_market` (integer): Listed at least this many days (higher suggests a motivated seller)
- `min_equity` (number): Estimated equity in USD (Zestimate or price minus assessed value; rough)
- `min_lot_size` (integer): Square feet (1 acre = 43,560)
- `min_ownership_years` (number): Owner has held the property at least this long
- `min_sqft` (integer): Minimum living area in square feet
- `min_year_built` (integer): Built in or after this year
- `min_zip` (integer): Lowest ZIP code in a numeric ZIP range (with max_zip); prefer zip_list for specific ZIPs
- `name` (string, required): Automation name shown in Spur
- `neighborhoods` (array): Neighborhood / area names matched against address and description
- `only_absentee` (boolean): Absentee-owned (owner mails elsewhere)
- `only_pre_foreclosure` (boolean): Distressed / pre-foreclosure (heuristic, includes description keywords)
- `only_vacant` (boolean): Likely vacant (heuristic: description keywords + long days on market)
- `ownership_type` (string): business = LLC / corp / trust owners (heuristic)
- `radius_miles` (number): Keep only listings within this many miles of center_lat / center_lng
- `run_time` (string, required): 24h local time "HH:MM"
- `timezone` (string): IANA time zone, e.g. "America/Chicago"
- `week_of_month`: Monthly only; -1 = last
- `zip_list` (array): Keep only these ZIPs; set location to the city that contains them

### `spur_run_search_automation` (~70 tokens)

Run search automation now

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.

Input parameters:

- `automation_id` (string, required): Automation id (UUID from a Spur list/search tool)

### `spur_get_automation_logs` (~60 tokens)

Automation run history

Recent runs of a search automation: when, how many found/saved/enriched, and errors.

Input parameters:

- `automation_id` (string, required): Automation id (UUID from a Spur list/search tool)
- `limit` (integer): Maximum runs to return

### `spur_get_texting_setup` (~87 tokens)

Texting setup status

The user's texting setup: phone numbers bought in Spur (and which can send), carrier (A2P 10DLC) registration status, carrier notes, what's still missing, and the next step. Call this before helping with numbers or registration.

Input parameters:

- `refresh` (boolean): true = ask the carriers for the latest status first (use when the user is waiting on approval)

### `spur_search_phone_numbers` (~109 tokens)

Find phone numbers

Search local US numbers the user can buy, by area code, state, city or digits. Show the options and let the user pick before spur_buy_phone_number. Prefer an area code in the user's market.

Input parameters:

- `area_code` (string): e.g. 512
- `city` (string)
- `contains` (string): Digits the number should contain, e.g. 777
- `limit` (integer)
- `state` (string): e.g. TX

### `spur_buy_phone_number` (~159 tokens)

Buy phone number

Buy a local number for the user's account (it's theirs immediately and replies land in their SMS inbox). It can't send texts until their carrier registration is approved. Plans include some numbers; beyond that each costs $5/mo from the Spur wallet, first month charged now (spur_get_texting_setup shows the user's price). Tell the user the price and get explicit approval for this exact number first.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `locality` (string): City from the search result, for display
- `phone_number` (string, required): phone_number from spur_search_phone_numbers
- `region` (string): State from the search result, for display

### `spur_set_default_phone_number` (~41 tokens)

Set default number

Make one of the user's bought numbers the default sender for their texts.

Input parameters:

- `number_id` (string, required): number_id from spur_get_texting_setup

### `spur_release_phone_number` (~86 tokens)

Release phone number

Permanently give up one of the user's bought numbers. They may never get it back, and contacts texting it will no longer reach them. Confirm with the user first.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `number_id` (string, required): number_id from spur_get_texting_setup

### `spur_save_texting_registration` (~203 tokens)

Save texting registration

Create or update the user's carrier (A2P 10DLC) registration draft. Pass only the fields to change; nested objects merge. Pick registration_type from two questions: has an EIN? (no → sole_proprietor) and more than ~2,000 texts/day? (yes → standard, else low_volume_standard). Business details must match IRS records exactly. Only record consent methods the user actually uses: carriers reject texting purchased or skip-traced lists without consent. write_campaign_text=true then reads their website and drafts the campaign description, opt-in flow and sample messages (needs message_types and consent_channels). Show that text to the user to review.

Input parameters:

- `address` (object)
- `business_info` (object)
- `contact` (object)
- `messaging` (object)
- `registration_type` (string)
- `write_campaign_text` (boolean): true = also draft the campaign text from their website and answers

### `spur_submit_texting_registration` (~231 tokens)

Submit texting registration

Send the user's registration to the carriers (also resubmits a rejected one after fixes). Charges the Spur wallet: $29 one-time for low volume / sole proprietor or $79 for standard (includes the first month, then $3 or $15/mo), or $15 to resubmit after a carrier rejection; spur_get_texting_setup shows the exact amount due now. Tell the user the amount. Walk the user through the full details first, and only call after they explicitly approve and personally confirm both statements: they only text people who agreed to receive their messages and honor STOP, and they won't send prohibited content (cannabis, firearms, high-risk loans or debt collection, gambling, sexual content, hate speech).

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
- `user_confirms_consent` (boolean, required): The user confirmed they only text people who agreed to receive their messages and honor STOP requests
- `user_confirms_no_prohibited_content` (boolean, required): The user confirmed they won't send prohibited content

### `spur_pay_texting_fees` (~83 tokens)

Pay overdue texting fees

Retry overdue monthly number and registration fees from the Spur wallet right away (normally retried daily). Use after the user adds funds. Restores paused numbers once paid. Charges the wallet: confirm the amount with the user first.

Input parameters:

- `confirm` (boolean, required): Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.

### `spur_resend_texting_verification` (~41 tokens)

Resend verification text

Sole proprietors only: re-send the carrier's verification text (the user replies YES) when the previous one expired after 24 hours.

### `search` (~72 tokens)

Search Spur

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.

Input parameters:

- `query` (string, required): Keywords: address, city, owner name, phone, email or template name

### `fetch` (~53 tokens)

Fetch Spur record

Fetch the full text of a record returned by search (ids look like property:…, owner:… or template:…).

Input parameters:

- `id` (string, required): Record id exactly as returned by search, e.g. property:<uuid>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-usespur-spur/mcp#diagnostics

## Score history

- 2026-11-06: 86
- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 84
- 2026-10-31: 83
- 2026-10-30: 83
- 2026-10-29: 82
- 2026-10-28: 82
- 2026-10-27: 81
- 2026-10-26: 81
- 2026-10-25: 80
- 2026-10-24: 80

## Common questions

### What is the Spur MCP server?

Spur is an MCP server listed in the public MCP registry as com.usespur/spur. Real estate leads, skip tracing, direct mail, SMS & email outreach, and marketing automations. This page covers its hosted endpoint (https://mcp.usespur.com/mcp).

### Is the Spur MCP server safe to use?

Spur scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Spur MCP server expose?

Spur exposes 87 tools: spur_search_properties, spur_parse_search_query, spur_get_property, spur_save_properties, spur_list_saved_properties, and 82 more. Their descriptions and schemas cost roughly 15,017 tokens of context every time the server is loaded.

### Does the Spur MCP server require authentication?

Yes. Spur asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Spur MCP server still maintained?

Spur is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Spur MCP server?

VerifyMCP ran 14 checks on Spur, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.usespur.com/mcp
- Website: https://usespur.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-usespur-spur/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-usespur-spur/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-usespur-spur/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-usespur-spur/mcp