mcp-slack·integration·active

Slack MCP

Real-time notifications when SARA finds Critical issues, LEO breaches an SLO, or ARIA's trend detector flags a regression. Routed to the right channel by component.

LEO SARA ARIAtrigger · mcp⌘ MCP · Slack

Slack MCP

Real-time notifications when SARA finds a Critical issue, LEO breaches an SLO, or ARIA'sTrend Detector flags a regression. Routed to the right channel by component.

What flows out

·Critical security findings (channel: #security-alerts or per-team config)

·SLO breaches from LEO (channel: #sre or per-service config)

·Regression alerts from ARIA (channel: per-team)

·Sprint report summaries (channel: per-team, end of sprint)

·Direct messages for individual reviewers when a remediation PR is assigned

What flows in

·Slash command responses (e.g. /aria status, /sara findings)

·Thread replies to alert messages (used to acknowledge / claim ownership)

·Reactions (used to dismiss noise — engineers react with :eyes: to acknowledge an alert)

Channel routing

→Channel routing is config-driven per component, never hardcoded. The default routes are:

·Auth service alerts → #auth-team

·Payments service alerts → #payments

·Frontend alerts → #frontend

·Cross-cutting (no clear owner) → #engineering

Routing falls back to a default channel if no per-service config exists.

Threading

For an ongoing situation (e.g. a SARA finding being remediated), all related notifications post to the same thread:

·Initial finding posts to the channel

·Remediation PR opened → reply in thread

·PR merged → reply in thread

·Verification run passes → reply in thread, parent message updated to ✅

This keeps channels readable. Channels with one-off messages per event become unreadable; channels with threaded conversations remain scannable.

Authentication

Slack app (OAuth 2.0). Scopes:

·chat:write — post messages

·files:write — upload report attachments

·channels:read — list channels for routing config

·reactions:read — observe reactions for ack flow

Rate limiting

Slack's per-app rate limit is 1 msg/sec per channel by default. The connector batches non-urgent messages into a single thread when alert volume spikes (e.g. a flurry of low-confidence findings).

Privacy

→The connector never DMs anyone who hasn't installed it. Direct messages are only sent to engineers explicitly named in a CODEOWNER or assignee field.

Server

mcp://slack.com/mcp

Vendor

Slack.

MCP server endpoint

mcp://slack.com/mcp

vendor · Slack

Related · integration

Sprint Context Loader

sprint-context-loader

Pulls sprint metadata — name, dates, team, release tag, prior trend data — directly from connected issue trackers via MCP.

Jira MCP

mcp-jira

Bidirectional Jira connector. TARA pulls stories from sprints; ARIA pushes findings, recommendations, and quality reports back as issues, comments, or sprint reviews.

TestRail MCP

mcp-testrail

Pulls existing test cases and execution history; pushes EVAN-generated tests and run results back as cases, runs, and milestone reports.

Azure DevOps MCP

mcp-ado

Pulls work items + repos; pushes test plans, suites, and runs. Handles ADO test points and outcome states with full bi-directional sync.

GitHub MCP

mcp-github

Reads PRs, issues, code search; opens PRs containing EVAN-generated automation, SARA remediation patches, and ARIA-recommended changes.

Confluence MCP

mcp-confluence

Reads PRDs and ACs from Confluence pages as TARA input. Publishes ARIA's quality reports back as Confluence pages with embedded charts.