Skip to the page

Recipes

Cursor recipes

Give Cursor’s agent DogBot’s tools while you build, so it can text you when a job finishes.

Three recipes for Cursor. Each names its trigger and the DogBot step, lists the fields to map and says how to test it with your own number before anyone else gets a text.

How Cursor connects

  • MCP: DogBot’s MCP server gives the assistant tools to send texts, read conversations and check your Mac.
  • API: Your own code calls DogBot’s REST API and listens to its signed webhooks.

Text me when the tests finish

PartWhat it is
TriggerYou ask Cursor’s agent
ActionThe assistant calls DogBot’s MCP tools
Connects throughMCP

Steps

  1. Add DogBot’s MCP server to Cursor with an API key as its bearer token.
  2. Ask the agent: “Run the test suite, then text me the result.”
  3. When the run ends, the agent calls send_text to your own number once you approve it.

Test it

Ask the assistant to text your own number first: “Text me at +1 555 555 0123 to say the setup works.” It shows the message DogBot returned, and the text arrives on your phone from your own number.

Find out why a text is waiting

PartWhat it is
TriggerYou ask Cursor’s agent
ActionThe assistant calls DogBot’s MCP tools
Connects throughMCP

Steps

  1. Ask: “Why hasn’t the text to +15555550123 gone out?”
  2. The agent finds it with list_messages and reads its hold with get_message.
  3. It answers in words, such as “It’s waiting for texting hours to open where the person lives,” and checks get_device_status when the hold says your Mac is offline.

Test it

Ask the assistant to text your own number first: “Text me at +1 555 555 0123 to say the setup works.” It shows the message DogBot returned, and the text arrives on your phone from your own number.

Add texting to your app

PartWhat it is
TriggerYou ask Cursor’s agent to write the code
ActionPOST /v1/messages
Connects throughAPI

Steps

  1. Ask the agent to install dogbot from npm and send a text with POST /v1/messages.
  2. Have it pass an Idempotency-Key so a retried request never sends twice.
  3. Have it add a route that checks DogBot’s webhook signature and handles message.received.

Map the fields

DogBot fieldMap it to
toThe person’s mobile number from Cursor. US numbers can leave off the +1.
textHi {{first_name}}, your appointment on {{date}} is confirmed. Reply here if you need to change it.
{{first_name}} in the textCursor’s first name field.
{{date}} in the textCursor’s date field.
metadatasource set to cursor, and record_id set to the record’s id, so the status and reply webhooks for this text can find the record again.
serviceAuto, the default: iMessage when the person uses it, otherwise SMS through your iPhone.
POST/v1/messagesSend a text →
curl -X POST "https://getdogbot.com/api/v1/messages" \
  -H "Authorization: Bearer $DOGBOT_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: cursor-1042" \
  -d '{
    "to": "+15555550123",
    "text": "Hi Maria, your appointment on (date) is confirmed. Reply here if you need to change it.",
    "metadata": {
      "source": "cursor",
      "record_id": "1042"
    }
  }'

Test it

Run the request with your own number in to. A text arrives on your phone from your own number.

Before you turn it on

  • Text only people who asked to hear from you. Anyone who replies STOP goes on your stop list, and DogBot cancels texts to them. Stop words
  • A text that can’t go yet waits with a hold rather than failing: texting hours, your Mac away, a daily limit. Holds
  • Cursor with DogBot on the integrations page says what else the two do together.