Squad Pings You — notification via Teams/MCP

Squad Pings You — Notification Architecture

Problem

When a squad member needs human input and the human isn't in the terminal session, there's no way to reach them. The squad should be able to ping the human on their phone — Teams, iMessage, Discord, whatever — when they hit a wall.

Vision

"It needs to feel like I'm not in the team room, they are, and they need me so they pinged me." — Brady

Solution (Designed)

Zero infrastructure in Squad core. Users bring their own MCP notification server.
A built-in skill (human-notification) teaches agents when and how to ping.
Teams is the primary path — Microsoft's official Teams MCP server, per-repo channels.
iMessage secondary (Mac-only), Discord/webhook as alternatives.

Deliverables (completed)

Design proposal: team-docs/proposals/034-notification-architecture.md
Notification skill: .ai-team/skills/human-notification/SKILL.md
Consumer docs: docs/features/notifications.md
Sample MCP config for Teams webhook setup
End-to-end test: agent triggers notification → message arrives in Teams
Update README with notification feature mention
Update guide.md with notification setup reference

Presume Teams

Per Brady's directive — Teams is the default/primary notification channel for docs and examples.

✅ v0.4.0 Verdict: Ship It

Status: 80% complete — design and core deliverables are done. This is finishing work.

What's Already Shipped

✅ Design proposal (team-docs/proposals/034-notification-architecture.md) — architecture validated
✅ Notification skill (.ai-team/skills/human-notification/SKILL.md) — agents know when and how to ping
✅ Consumer docs (docs/features/notifications.md) — user-facing documentation complete

Remaining Work Items

WI-1: Sample MCP Config for Teams Webhook

Owner: Fenster (Configuration Specialist)
Effort: 30 minutes
Acceptance Criteria:

Sample .mcp.json snippet showing Teams webhook MCP server configuration
Include comments explaining webhook URL setup
Location: docs/examples/mcp-teams-config.json or inline in docs/features/notifications.md

WI-2: End-to-End Test Scenario

Owner: Hockney (Test Architect)
Effort: 1 hour
Acceptance Criteria:

Test script that exercises the human-notification skill
Validates agent → MCP → Teams message flow
Location: est/integration/notification-e2e.test.js or test documentation

WI-3: README Update

Owner: McManus (Documentation Lead)
Effort: 15 minutes
Acceptance Criteria:

Add "Agent Notifications" to features list in README.md
One-sentence description with link to docs/features/notifications.md

WI-4: guide.md Update

Owner: McManus (Documentation Lead)
Effort: 15 minutes
Acceptance Criteria:

Add notification setup reference to docs/guide.md
Link to notification docs and MCP config example

Dependencies & Risks

Dependencies:

WI-1 (config example) should complete before WI-2 (test) for reference
WI-3 and WI-4 can run in parallel after WI-1

Risks:

⚠️ Low risk — no core Squad changes needed, zero infrastructure footprint
Teams webhook testing requires a real Teams channel (external dependency)
Fallback: document manual testing procedure if automated E2E is blocked

Architecture Notes

This is the right design:

Zero infrastructure — users bring their own MCP server, Squad stays lean
MCP-native — leverages existing notification servers (Teams, iMessage, Discord)
Skill-based — agents learn the pattern, no hardcoded notification logic

This feature makes Squad feel like a real team that can reach you when you're not in the room.

Timeline: 2-3 hours total work. Target: complete within this sprint.

— 🏗️ Keaton (Lead) · Posted by Squad

docs: MCP setup guide, notifications update, plugin marketplace guide (…

Delivered in PR #38 (docs). Updated docs/features/notifications.md with sample MCP configs for Teams, iMessage, Discord, and webhook. Added notifications section to docs/guide.md and README.md v0.4.0 section.

docs: add v0.8.25 release blog post (#27)

test: add SDK feature parity batch 2 tests (github#347/github#341)

test: SDK feature parity batch 2 — 64 tests for #27, #28, #36, #49, #50…

docs: Add Teams & Outlook bidirectional integration research for Squa…

chore: Append Issue github#27 Teams/Outlook research findings to Elro…

Navigation Menu

Repository navigation

Squad Pings You — notification via Teams/MCP #27

Squad Pings You — Notification Architecture

Problem

Vision

Solution (Designed)

Deliverables (completed)

Presume Teams

✅ v0.4.0 Verdict: Ship It

What's Already Shipped

Remaining Work Items

WI-1: Sample MCP Config for Teams Webhook

WI-2: End-to-End Test Scenario

WI-3: README Update

WI-4: guide.md Update

Dependencies & Risks

Architecture Notes

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Squad Pings You — notification via Teams/MCP #27

Description

Squad Pings You — Notification Architecture

Problem

Vision

Solution (Designed)

Deliverables (completed)

Presume Teams

Activity

bradygaster commented on Feb 13, 2026

✅ v0.4.0 Verdict: Ship It

What's Already Shipped

Remaining Work Items

WI-1: Sample MCP Config for Teams Webhook

WI-2: End-to-End Test Scenario

WI-3: README Update

WI-4: guide.md Update

Dependencies & Risks

Architecture Notes

bradygaster commented on Feb 13, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions