Does this MCP require Microsoft Graph API permissions?

No. This MCP uses incoming webhooks, so it doesn't need broad permissions like ChannelMessage.Send across your entire tenant.

Can my AI agent read my Teams messages?

No. The connection is one-way. The agent can only send messages to the specific channel where you provided the webhook URL.

Can I send more than just plain text?

Yes. You can use the cardJson parameter to send rich Adaptive Cards or MessageCards with buttons and tables.

How do I set this up in my AI client?

Vinkius hosts the MCP. You simply connect your client to the Vinkius catalog and provide your webhook URL.

Is this secure for enterprise use?

Yes. It follows a zero-trust model because it is limited to a single webhook, preventing the agent from accessing other corporate data.

Can the agent read messages from Teams with this?

No. Teams Incoming Webhooks are strictly unidirectional (Push only). The agent can only send messages to the authorized channel. It cannot read the channel history, see replies, or access other channels or SharePoint files. This ensures absolute Zero-Trust containment.

How do I create an MS Teams Webhook URL?

In Microsoft Teams, navigate to the channel, click '...', select 'Connectors', search for 'Incoming Webhook', and add it. Name your webhook and copy the generated URL.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Microsoft Teams Webhook Notifier to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Give your AI agent a direct line to your Teams channels.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 1 capability

We ship only the actions that matter.

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through MS Teams Webhook.

01
Send teams message
This capability sends a notification or message to a Microsoft Teams channel using a webhook. You can send plain text or include a rich UI element through the cardJson parameter.

Real work

What teams actually run

Deployment Notifications

Your agent sends a message to the dev channel as soon as a CI/CD pipeline finishes.

Incident Alerting

The agent posts a rich Adaptive Card when it detects a system error or service outage.

Automated Reporting

Your agent pushes structured telemetry data or daily summaries into a management channel.

Bug Reporting

The agent sends detailed bug reports with structured data to the engineering team.

Automate a task

Put MS Teams Webhook to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

MS Teams Webhook works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put MS Teams Webhook to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

900ms average. Fast in production.

MS Teams Webhook is checked daily against the live service.

Daily averagePeak 1464ms

Oct 5Today

Fastest day: 681ms
Slowest day: 1464ms
14-day trend: Improving-20%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 1 capability arrives ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of MS Teams Webhook, so you can see the experience inside your AI.

It does not authenticate your account with MS Teams Webhook. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

MS Teams Webhook Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_Pr8BUJFY1CYpfeUuj1rFw4RZo9IJ3IhbXBT2nkIw/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — MS Teams Webhook capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "microsoft-teams-webhook-notifier-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_Pr8BUJFY1CYpfeUuj1rFw4RZo9IJ3IhbXBT2nkIw/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up MS Teams Webhook in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work MS Teams Webhook owners hand off.

This MCP is built for technical teams who need to bridge the gap between automated agents and human communication channels.

01
DevOps Engineers
They hand off deployment statuses and infrastructure alerts to the agent.
02
SREs
They use the agent to push real-time system telemetry and incident reports to Teams.
03
Software Developers
They let the agent report build failures or bug alerts directly to their workspace.

FAQ

Questions MS Teams Webhook owners ask.

01
Does this MCP require Microsoft Graph API permissions?
No. This MCP uses incoming webhooks, so it doesn't need broad permissions like ChannelMessage.Send across your entire tenant.
02
Can my AI agent read my Teams messages?
No. The connection is one-way. The agent can only send messages to the specific channel where you provided the webhook URL.
03
Can I send more than just plain text?
Yes. You can use the cardJson parameter to send rich Adaptive Cards or MessageCards with buttons and tables.
04
How do I set this up in my AI client?
Vinkius hosts the MCP. You simply connect your client to the Vinkius catalog and provide your webhook URL.
05
Is this secure for enterprise use?
Yes. It follows a zero-trust model because it is limited to a single webhook, preventing the agent from accessing other corporate data.
06
Can the agent read messages from Teams with this?
No. Teams Incoming Webhooks are strictly unidirectional (Push only). The agent can only send messages to the authorized channel. It cannot read the channel history, see replies, or access other channels or SharePoint files. This ensures absolute Zero-Trust containment.
07
How do I create an MS Teams Webhook URL?
In Microsoft Teams, navigate to the channel, click '...', select 'Connectors', search for 'Incoming Webhook', and add it. Name your webhook and copy the generated URL.