Are these separate MCP tools?

No. Workflow profiles are structural primitives that ship in the OSS package — slack_workflow_save and slack_workflows. The AI brain (slack_smart_search, slack_catch_me_up, slack_triage) consumes them and returns structured JSON per the workflow_kind. Profile primitives live in OSS; the AI brain is hosted-only because it needs Vectorize + Workers AI.

Why structured JSON outputs instead of free-text summaries?

Operators chain workflow outputs into other tools — Notion, Linear, project trackers, status dashboards. Free-text summaries don't compose. Structured JSON does. exec_brief always returns {summary, decisions, risks, asks, action_items} so downstream automation can rely on the shape.

When do I need Pro vs Team?

Pro at $9/mo unlocks the scheduled morning catch-up DM (rolling out Q2 2026) and unlimited AI tool calls — the daily habit lever. Team at $49/mo flat adds shared workflow profiles across 5 workspaces, audit log, 24h support, and scheduled catch-up to a team channel. Pro is solo. Team is squad.

Workflows

Five workflow profiles. Structured JSON outputs.

Workflow profiles are the structural primitive that nobody else has. Define support_inbox, incident_room, exec_brief, product_launch_watch, or custom — the AI brain returns structured JSON per the workflow_kind. The brain is hosted-only; the profile primitives ship in OSS.

`support_inbox`

Returns: {open_threads, ack_lag, owner_gaps, escalations, next_actions}

Plan fit: Pro fit for solo support operators. Team fit when 2-10 people share the inbox and need synced profiles plus audit log.
Prompt starter: Run slack_catch_me_up against my support_inbox profile and return the structured JSON for this morning's standup.
Structured keys: open_threads, ack_lag, owner_gaps, escalations, next_actions

`incident_room`

Returns: {incident_summary, timeline, open_risks, owner_gaps, next_actions}

Plan fit: Team fit for 2-10 person on-call rotations. Ops fit when SLA, custom retention, or SOC2 evidence become hard requirements.
Prompt starter: Run slack_catch_me_up against my incident_room profile and return the structured JSON for the next responder.
Structured keys: incident_summary, timeline, open_risks, owner_gaps, next_actions

`exec_brief`

Returns: {summary, decisions, risks, asks, action_items}

Plan fit: Pro fit for solo founders / executives. The scheduled morning catch-up DM (rolling out Q2 2026) at 8am workspace time makes $9 a daily habit.
Prompt starter: Run slack_catch_me_up against my exec_brief profile for the last 24 hours and return the structured JSON.
Structured keys: summary, decisions, risks, asks, action_items

`product_launch_watch`

Returns: {launch_signals, feedback_themes, blockers, metrics, next_actions}

Plan fit: Team fit for product ops squads. Free tier validates the pattern. Pro fit for solo PM operators running daily.
Prompt starter: Run slack_catch_me_up against my product_launch_watch profile for the current release and return the structured JSON.
Structured keys: launch_signals, feedback_themes, blockers, metrics, next_actions

`custom`

Returns: {summary, highlights, open_questions, next_actions}

Plan fit: Any plan. Use when the four named profiles don't match your workflow shape — define your own channels + priority people + cadence.
Prompt starter: Run slack_catch_me_up against my custom profile and return the structured JSON for this morning.
Structured keys: summary, highlights, open_questions, next_actions

How profiles work

A workflow profile binds a workflow_kind (one of the 5 above) to:

channels: the Slack channels the AI reads
priority_people: users whose messages get extra weight
retention_mode: ephemeral or persistent
summary_cadence: on_demand, daily_8am, weekly_monday

The OSS package ships slack_workflow_save and slack_workflows — define profiles locally, hosted syncs and runs the AI brain against them.

Concrete recipe starters

Morning founder brief: exec_brief profile + scheduled morning catch-up DM (rolling out Q2 2026) at 8am workspace time. Pro $9/mo.
Support inbox standup: support_inbox profile + slack_catch_me_up at start of every shift. Free tier validates; Pro for daily.
Incident handoff: incident_room profile + slack_catch_me_up before next responder takes over. Team $49/mo flat.
Release watch: product_launch_watch profile + slack_catch_me_up at end of every day during the launch window. Team for shared visibility.

Templates ship in OSS

The OSS package includes 6 prebuilt workflow templates: oncall-handoff, support-triage, exec-monday, sprint-tracker, customer-feedback, incident-room. Apply them with:

npx -y @jtalk22/slack-mcp --apply-template oncall-handoff

Time-to-first-value drops from 10 minutes to 30 seconds.

Next step

Free tier ships all 5 workflow profile types and monthly AI credits — try the pattern before upgrading.

Start free Start Pro $9/mo Start Team $49/mo View plans

Buyer FAQ

Are these separate MCP tools? No. Workflow profiles are structural primitives that ship in the OSS package — slack_workflow_save and slack_workflows. The AI brain (slack_smart_search, slack_catch_me_up, slack_triage) consumes them and returns structured JSON per the workflow_kind. Profile primitives live in OSS; the AI brain is hosted-only because it needs Vectorize + Workers AI.
Why structured JSON outputs instead of free-text summaries? Operators chain workflow outputs into other tools — Notion, Linear, project trackers, status dashboards. Free-text summaries don't compose. Structured JSON does. exec_brief always returns {summary, decisions, risks, asks, action_items} so downstream automation can rely on the shape.
When do I need Pro vs Team? Pro at $9/mo unlocks the scheduled morning catch-up DM (rolling out Q2 2026) and unlimited AI tool calls — the daily habit lever. Team at $49/mo flat adds shared workflow profiles across 5 workspaces, audit log, 24h support, and scheduled catch-up to a team channel. Pro is solo. Team is squad.

Official vs managed Ops engagement