Stet MCP Server enables you to compose, target, preview, send/schedule, and measure Slack broadcasts from any MCP-capable agent.
Compose: Create drafts, set content in Markdown, add individual blocks (text, headers, images, etc.), reorder blocks, and control per-audience visibility.
Target: List channels and saved audiences, create one-time channel sets, get heuristic audience suggestions, and manage sending profiles (display name, avatar, footer, default audiences).
Validate & Preview: Check for channel overlap conflicts and preview the exact Slack Block Kit render per audience.
Send & Schedule: Send immediately, schedule for a future date/time, or cancel a scheduled/in-flight broadcast.
Measure: List broadcasts with status and preview, get per-channel delivery results (status, permalinks), emoji reaction totals (overall, by emoji, by channel), and in-thread replies with replier details.
Allows drafting, sending, and measuring Slack broadcasts via Stet.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Stet MCP Server draft a broadcast for the engineering team"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Local stdio MCP server for Stet. Draft, send, and measure Slack broadcasts from any MCP-capable agent.
Stet is a Slack-first broadcasting tool: compose a message once, target it per audience, preview the real Slack render, then send or schedule it across many channels with delivery tracking. This package exposes that whole workflow as MCP tools, so an agent can draft a broadcast, preview exactly what will land, send it, and read back who replied.
You need a Stet workspace to use this. Sign up at stethq.com.
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/mcpOr 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"
}
}
}
}Generate an API key at Dashboard → Settings → API keys. Keys are workspace-scoped; pick the write scope for full functionality (read-only keys can list and measure, but cannot compose or send).
Requires the Growth plan or higher. The REST/MCP surface is gated: below
Growth, every call returns 403 with a plan-upgrade-required problem
document. If you do not have a workspace yet, start at
stethq.com — mention that you want API/MCP access and we
will get you on a plan that includes it.
Related MCP server: Slack MCP Server
list_sending_profiles → pick who it comes from
list_channels → find the channels to hit
create_broadcast → returns a draft id
set_one_time_channels → target ad-hoc channels (or pass audience_ids up front)
set_broadcast_content → write the whole body as Markdown
preview_broadcast → one audience_id at a time (from list_audiences or
the set_one_time_channels response) — see the exact
Slack Block Kit that will land
send_broadcast_now → or schedule_broadcast
—— later ——
get_broadcast_sends → who got it, who failed, and why
get_broadcast_reactions → emoji engagement, by channel
get_broadcast_replies → what people actually said backTool | Description |
| Create a draft with a title, sending profile, and optional target audiences. Returns the new id. |
| Compose (or replace) the entire body from Markdown — one string, or per-audience segments. |
| Append a single content block (section, header, divider, image, context, actions, rich_text_list, fields). Prefer |
| Restrict a block to a subset of the target audiences. Empty array = visible to all. |
| Reorder blocks by supplying the full block-id list in the new order. |
Tool | Description |
| List Slack channels in the connected workspace. Free-text query plus structural filters. |
| List saved audiences (named sets of channels). |
| Create a saved audience from an explicit list of channel ids. |
| Target a draft at an ad-hoc channel set without creating a saved audience. Empty list deletes the group. |
| Heuristic audience suggestions based on channel-name patterns. |
| List sender identities configured in this workspace. |
| Create a sender identity: display name, avatar, footer, default audiences. |
Tool | Description |
| Check for channel-overlap conflicts (one channel in several audiences whose visible blocks differ). |
| Render the per-audience Slack Block Kit exactly as it will be delivered. |
| Send immediately. If the broadcast is already scheduled, returns 409 with the pending send time — retry with |
| Schedule for an ISO timestamp + timezone. |
| Cancel a scheduled or in-flight broadcast. Already-posted messages stay posted. |
Tool | Description |
| List broadcasts newest-first with status, counts, send time, and a content preview. Optional status filter. |
| A broadcast's content and lifecycle state: row, target audiences, blocks. |
| Per-channel delivery: status, error message, Slack permalink, reply/reaction counts, plus a delivered/failed/pending summary. |
| Emoji reaction totals — overall, by emoji, and by channel. |
| In-thread replies with the replier's display name and a permalink. Optional per-channel filter. |
Reactions and replies are only captured for messages Stet itself posted — they are matched to a send by channel + timestamp. Messages posted to Slack by other means have no engagement data here.
Engagement history is limited to your plan's retention window: 30 days on Growth and Scale, unlimited on Enterprise. Rows outside the window are hidden, not deleted, and reappear if you upgrade.
The schemas in src/tools.ts describe a REST API that lives in a separate,
private repository — there's no compiler tying the two together, so drift is
possible.
Be extra careful with output schemas. Validation on the output side is deliberately fail-soft: a wrong output schema still returns usable data to the caller and only logs a warning to stderr. A mistake here does not show up as a visible failure to anyone using the server.
This repo's unit tests run against a mock and can't catch that kind of drift —
the mock fabricates responses that match whatever the schema says, so it can't
tell you the schema itself is wrong. The only check that verifies these schemas
against the real API is a conformance suite that lives in the API repo
(npm run mcp:verify). Pair any release that touches src/tools.ts with a run
of it.
Variable | Required | Description |
| Yes | Workspace-scoped API key (Dashboard → Settings → API keys). |
| Yes | Base URL of your Stet deployment, e.g. |
MIT — see LICENSE.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Manage SRG+ hubs, channels, content, assets, users, and workspaces from any MCP-aware AI agent.
Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.
Phone, SMS & email for AI agents — one remote MCP endpoint, OAuth login, zero install.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/stethq/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
