# Teams Webhook Notifier MCP

> Microsoft Teams Webhook Notifier MCP sends structured messages and alerts directly into your designated Microsoft Teams channels. It provides a secure, zero-permission bridge for your AI agent to communicate critical updates—like deployment statuses or engineering reports—without needing complex corporate API access.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Tags:** webhook, notifications, alerts, adaptive-cards, zero-trust, real-time-messaging

## Description

This MCP gives your AI client the ability to drop important notifications straight into specific Teams channels. Think of it as giving your automation process a megaphone that only reaches one room.

Because this tool uses a simple Incoming Webhook URL, you skip the headache of managing enterprise-level permissions or rotating complex API tokens. Your agent doesn't need read access—it just needs permission to speak. This means you can send rich alerts, like those formatted with Adaptive Cards, complete with actionable buttons and data tables, without compromising your organization’s security posture.

The Vinkius catalog makes this simple connection available across any compatible AI client. You get the ability to reliably alert teams about everything from successful deployments to production bugs using pure, contained messaging. It's one of the safest and most straightforward ways to keep critical information visible where it needs to be.

## Tools

### send_teams_message
Sends a notification or message to a Microsoft Teams channel, optionally including rich UI details via JSON.

## Prompt Examples

**Prompt:** 
```
Notify Teams that the deployment is complete.
```

**Response:** 
```
I've sent the message 'The deployment is complete.' to the Teams channel.
```

**Prompt:** 
```
Send a rich alert to Teams using a MessageCard format to report a bug.
```

**Response:** 
```
The rich MessageCard alert detailing the bug has been successfully posted to Teams.
```

## Capabilities

### Post Rich Alerts
Send messages that include structured data, buttons, and tables instead of plain text.

### Broadcast Status Updates
Notify a specific Teams channel about events like deployments or service status changes.

### Trigger Engineering Reports
Automatically post detailed technical reports and incident summaries to the team chat.

## Use Cases

### Deployment Complete Alert
The CI/CD pipeline finishes its build and asks the agent to notify Teams. The agent calls `send_teams_message` with a structured card confirming the version number, commit hash, and providing an immediate link to review the logs.

### Incident Bug Report
A monitoring service detects an anomaly. The automation triggers the agent, which formats the full stack trace and impact area into a rich MessageCard using `send_teams_message`, ensuring the on-call team gets all necessary data immediately.

### Feature Flag Rollout Status
When a new feature is flipped live, the agent sends a status update to the #releases channel. This message uses `send_teams_message` to include an expiration date and the responsible team contact.

### Daily Standup Summary
At 9 AM, the agent aggregates summaries from multiple systems. It then posts a clean, structured daily summary message into the dedicated standup chat using `send_teams_message`.

## Benefits

- Zero Security Risk: You don't need heavy Graph API tokens or complex permissions. This webhook method keeps the connection surgically contained, only allowing messaging out and nothing else.
- Rich Content Delivery: Don't settle for plain text updates. Your agent uses `send_teams_message` to generate fully interactive Adaptive Cards with buttons and tables.
- Deployment Agnostic: Whether you’re using your agent in a code IDE like Cursor or an autonomous workflow engine like CrewAI, the message delivery remains simple and reliable.
- Instant Visibility: Critical alerts hit the team chat immediately. Instead of checking logs or dashboards, everyone sees the status update pop up right where they work.
- Maximum Containment: Because it’s a webhook, your agent cannot read corporate emails or snoop on other channels. It only sends messages to what you define.

## How It Works

The bottom line is that you use a simple URL to let your agent speak directly into one specific Teams chat without needing massive security credentials.

1. First, you set up a single Incoming Webhook URL within your target Teams channel. This URL is how the MCP connects.
2. Next, your AI agent calls this MCP and invokes the `send_teams_message` tool, providing either plain text or detailed JSON for rich cards.
3. Finally, the message bypasses complex corporate permissions and appears in the designated Teams channel instantly.

## Frequently Asked Questions

**Can I use Microsoft Teams Webhook Notifier MCP for general chat?**
No, this MCP only sends messages to the specific channel defined by your incoming webhook URL. It is not designed for general, ad-hoc chatting across multiple locations.

**Does send_teams_message require elevated permissions?**
Nope. Because it uses a simple webhook, it bypasses the need for complex corporate API tokens or high-level Graph access, making it very low risk.

**What is the limit on what I can send using this MCP?**
You can send plain text messages, but the real power comes from the optional `cardJson` parameter in `send_teams_message`, which lets you create rich Adaptive Cards.

**Can my agent read data with Microsoft Teams Webhook Notifier MCP?**
No. This is a one-way street. The MCP only allows your AI client to send messages out; it has zero ability to read or access any other internal corporate data.

**Does this work with all types of Teams channels?**
It works for any channel where you can generate a standard Incoming Webhook URL. The setup is specific to the destination chat, not the entire tenant.