Headless API & MCP

REST and MCP for servers and LLM agents. No widget.

No widget. Call the REST API at https://api-v2.dropcowboy.com from your server with an API key, or connect an AI agent to MCP at https://mcp.dropcowboy.com/mcp. Start with the API reference or connect AI tools.

When to use this vs REST

This block is REST and MCP. Use it from servers and AI agents. There is nothing to embed.

Do not rebuild

• A client for our API. The MCP server already exposes the tools to Cursor and Claude.

Drop-in

API keys stay on the server. Catalog discovery on MCP needs no key. Data-plane tools need the team signed in or an API key.

# SMS from your backend. phone_line_id is a line with an approved texting campaign.
curl -X POST https://api-v2.dropcowboy.com/sms \
  -H "x-key: $KEY" -H "x-secret: $SECRET" \
  -H "Content-Type: application/json" \
  -d '{"to":"+15125550148","phone_line_id":"e2b6f9a3-5c1d-4e8b-a4f7-9c3e1b5d7a28","body":"Hi from Drop Cowboy"}'

# MCP (Cursor / Claude): https://mcp.dropcowboy.com/mcp
# Anonymous tools: list_building_blocks, get_building_block
# Signed-in tools: contacts, campaigns, messaging, ...

JS API / HTML tag

No browser widget and no HTML tag. MCP clients connect to https://mcp.dropcowboy.com/mcp. Looking up Building Blocks needs no key; data tools need the team signed in or an API key.

Auth and scopes

API key and secret on your server. Looking up blocks needs no key.

Limits

• API keys stay on the server. Never ship them to a browser.
• Each key only has the scopes you grant it.

Related REST

Routes are on https://api-v2.dropcowboy.com.

• POST /sms - send a text (sms:send)
• https://mcp.dropcowboy.com/mcp - MCP server

Full reference: Texts API.