Merge Unified's Microsoft Teams integration Merge Agent Handler's Microsoft Teams MCP server

Connect your AI Agents to Microsoft Teams in minutes

Merge lets you securely connect your agents to Microsoft Teams and thousands of tools instantly

Start building for free

Read docs

Microsoft Teams

Learn more about Merge Agent Handler

Available tools

reply_to_message

Reply to a specific message in a Teams channel to create threaded conversations.

get_message_replies

Retrieve all replies to a specific message to follow threaded conversations. Useful for understanding discussion context and reading complete conversation threads.

check_channel_type

Check if a channel is private or standard. Returns channel permissions and member management availability.

list_private_channels

List only the private channels in a team.

list_channels

List all channels in a Microsoft Team.

create_channel

Create a new channel within a Team for focused discussions.

get_channel_info

Get detailed information about a Teams channel including description, settings, and metadata. Useful for understanding channel purpose and permissions.

update_channel

Update channel settings such as name, description, or moderation settings.

delete_channel

Permanently delete a channel from a Team. Exercise caution - this removes all channel messages and files. Typically used for cleanup or reorganization.

list_team_files

List all files stored in a Team's SharePoint drive.

delete_team_file

Remove files from a Team's drive to clean up outdated content, free up storage, or remove sensitive information. Exercise caution as this permanently deletes files.

create_meeting

Create a new Teams meeting with attendees and schedule it in calendars. Includes automatic Teams integration for online meetings.

View all tools by creating a free account

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}

Copy Code

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }

Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}

Copy Code

FAQs on using Merge's Microsoft Teams MCP server

How can I use the Microsoft Teams MCP server?

Here are just a few potential use cases you can implement:

Notifications: Your agent can send real-time alerts to specific Teams channels when critical events occur, like high-priority tickets being created

Cross-platform collaboration: Your agent can post project updates to Teams channels by pulling data from tools like Jira or Asana

Meeting coordination: Your agent can schedule and create Teams meetings automatically when certain conditions are met, such as when an enterprise opportunity gets created

File sharing: Your agent can retrieve and share files from Teams channels with other systems, or upload reports and documents to relevant Teams folders

Scheduling: Your agent can check team members' availability statuses in Teams before scheduling meetings

Channel management: Your agent can create a new Teams channel automatically when an enterprise customer’s health scores drop below a predefined threshold

What are popular tools for Microsoft Teams’ MCP server?

Here are just a few popular tools across different areas:

Channels:

<code class="blog_inline-code">create_ channel</code>
<code class="blog_inline-code">update_channel</code>
<code class="blog_inline-code">get_channel_info</code>
<code class="blog_inline-code">check_channel_type</code>

Meetings:

<code class="blog_inline-code">get_free_busy_schedule</code>
<code class="blog_inline-code">list_meetings</code>
<code class="blog_inline-code">cancel_meting</code>

Team members:

<code class="blog_inline-code">get_team_member</code>
<code class="blog_inline-code">add_team_member</code>
<code class="blog_inline-code">list_team_member</code>
<code class="blog_inline-code">remove_team_member</code>

Can I set custom security rules for Microsoft Teams tool calls in Merge Agent Handler?

You can apply seemingly endless rules that align with your security policies and that of your customers. Here are just a few:

Credit card numbers: Block any messages that contain credit card numbers in the message content

Social security numbers: Prevent messages that contain social security numbers

Email addresses: Redact email addresses when the agent retrieves or searches channel messages. It should only see masked versions (e.g., j*@merge.dev)

Phone numbers: Automatically redact phone numbers from Teams message content when agents retrieve channel conversations or chat histories

API keys and tokens: Block agents from posting authentication credentials or access tokens in Teams channels or direct messages

Internal project codes: Mask sensitive project identifiers when agents read messages from specific Teams channels to prevent cross-team information leakage

What makes Merge Agent Handler’s Microsoft Teams MCP server better than alternative Teams MCP servers?

Merge provides security, reliability, and operational capabilities that Microsoft Teams MCP servers typically don’t offer. This includes:

Enterprise-grade authentication management

Merge performs credential validation, user-specific or shared authentication, and guided login flows through Merge Link. This eliminates the need for developers to write auth flows manually.

Security gateway and DLP protections

All tool inputs and responses are scanned for sensitive data. And administrators can block, redact, or mask data based on configurable rules, and get alerted when these rules are violated.

Connector Studio for customization

You can add, modify, or extend tools and connectors while preserving production-ready quality through Merge’s validation workflows.

Real-time observability and full audit logs

Merge provides searchable logs, audit trails, API request traces, and agent-level action monitoring, all of which are crucial for enterprise Teams deployments.

How can I add tools to Merge Agent Handler’s Microsoft Teams MCP server?

Here’s a brief breakdown of the steps you can take:

1. Open Connector Studio in the Agent Handler dashboard, and add the Microsoft Teams connector.

2. Add or modify tools within the Microsoft Teams connector. This includes defining API requests for Teams-specific actions, configuring input/output schemas for each tool, and providing optimized tool descriptions

3. Assign an authentication model (individual or shared). Individual authentication lets each user authenticate with their own Microsoft Teams credentials, while shared authentication enables organization-level access using shared credentials.

4. Add the Microsoft Teams connector to a Tool Pack, then regenerate the Tool Pack ID to include your Microsoft Teams tools.

5. Associate the Tool Pack with your agent using the MCP entry URL.

Explore other MCP servers built and managed by Merge

Airtable

Asana

Calendly

Confluence

Figma

GitHub

Gmail

Gong

Google Calendar

Google Drive

Greenhouse

HubSpot

Intercom

Jira

Jira Service Management

Linear

Notion

OneDrive

Outlook

Pipedrive

QuickBooks Online

SAP SuccessFactors

Salesforce

ServiceNow

SharePoint

Shopify

Slack

Stripe

Weather

Wikipedia

Zendesk

Zoom

Ready to try it out?

Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now