MCP server

The Stet MCP server, @stethq/mcp, lets AI agents drive Stet over the Model Context Protocol: compose broadcasts, target audiences, send or schedule, and read delivery and engagement results. It is a thin adapter — every tool maps to a REST route in the API reference.

Requirements

An API key (bk_…) from Settings → API keys. Pick the write scope for full functionality — a read key can list and measure but can't compose or send. API access requires the Growth plan or higher; below that every request returns a 403 with a plan-upgrade-required problem document.

Install and connect

Nothing to install — npx runs the server on demand:

claude mcp add stet \
  --env STET_API_KEY=bk_xxxxxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx \
  --env STET_API_URL=https://app.stethq.com \
  -- npx -y @stethq/mcp

Or add it to your MCP config by hand:

{
  "mcpServers": {
    "stet": {
      "command": "npx",
      "args": ["-y", "@stethq/mcp"],
      "env": {
        "STET_API_KEY": "bk_xxxxxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "STET_API_URL": "https://app.stethq.com"
      }
    }
  }
}

Both STET_API_KEY and STET_API_URL are required. STET_API_URL is the base URL of your Stet deployment, for example https://app.stethq.com.

Tools

The full tool reference lives in the @stethq/mcp README — deliberately, so the npm page and these docs can't drift apart. Tools group into four families: compose (draft content and blocks), target (channels, audiences, sending profiles), send (validate, preview, send now or schedule), and measure (deliveries, reactions, replies).