Can an agent remove team members?

The remove tools exist in the inventory, and the document marks them as “Side effect delete not allowed”, so the server refuses those calls. Membership changes that should happen are best done by a person in Teams itself.

Does the server cover meetings and calls?

Yes. It creates online meetings for the signed-in user or on behalf of a specified user, and starts calls with target participants and media configuration.

What is Warden preflight?

Warden is DataGrout’s neuro-symbolic firewall. It inspects each tool call before execution in Off, Log only, Advisory or Enforce mode, blocking requests that look like prompt injection or unsafe data access.

Native MCP Server

Microsoft Teams MCP Server

Q: How many tools does the Teams MCP Server include?

178 tools covering teams, channels, channel messages and tabs, chats, meetings and calls, presence and work location, shifts and schedules, telephony, channel email and Graph search. The full inventory is listed in your DataGrout workspace.

Give your AI agents native, governed access to Microsoft Teams. 178 purpose-built tools cover teams and channels, channel messages and tabs, chats, meetings and calls, presence and work location, shifts and schedules, telephony and Graph search, under one policy layer.

Get started free

No code. One Hub endpoint for every agent.

Native Teams tools: 178
Tenant-scoped connection: OAuth2
Policy-controlled: Read + Write
Preflight on every call: Warden

What is the DataGrout Microsoft Teams MCP Server?

The DataGrout Microsoft Teams MCP Server is a native Model Context Protocol server that exposes Teams as callable tools for AI agents. Agents can add team members, create and archive channels, post and reply to channel messages, work with chats and their members, create online meetings and calls, set presence and work location, build shifts and schedules, assign phone numbers and run Microsoft Graph Search across Microsoft 365, all through one governed endpoint that enforces side-effect policy and runs Warden preflight on every call.

178 tools across channels, chats, meetings and schedules

Tenant-scoped connection for the organisation

Read and write allowed, scoped by your policy

178 Microsoft Teams tools, grouped by the work they do

Teams is a workspace and a phone system in one. The groups below follow that shape; the full inventory is in your signed-in workspace.

Teams and channels

Set up the space before anyone is invited into it.

Add a member to a team
Create standard, private or shared channels
Archive a channel, including through the group-based team endpoint
Provision or remove a channel’s email address

Channel messages and tabs

Where the work is discussed, and where its context lives.

Post a message in a channel
Reply to a specific channel message
Pin a message in a chat
Add a tab to a channel

Chats

One-to-one and group conversations, including per-user state.

Create a chat, or get the existing one-to-one chat
Add a member to a chat
Post a message in a chat
Hide a chat or mark it read or unread for a user

Meetings and calls

Create the meeting, or place the call.

Create an online meeting for the signed-in user
Create an online meeting on behalf of a specified user
Start a call with target participants and media configuration
Return the meeting or call details the next step needs

Presence and work location

The signal colleagues read before they message someone.

Set a user’s preferred presence, or clear it
Set presence with availability, activity and a session
Set a manual work location by place ID
Set or clear the automatic work location

Shifts, telephony and search

Scheduling and the org-level plumbing around Teams.

Create shifts, open shifts and scheduling groups
Offer a shift and share a team schedule
Assign or update a telephone number for a user or resource account
Run a Microsoft Graph Search query across Microsoft 365 resources

Connect Microsoft Teams in four steps

Everything happens in the DataGrout Hub — no code, no per-agent configuration.

1
Open your Hub Server
In DataGrout, open the Hub Server that will carry your integrations and click Add Integration.
2
Find Microsoft Teams
Search for Microsoft Teams, then select the native MCP Server integration.
3
Credentials, tenant and sandbox
The integration has Credentials and Sandbox sections. Connect the Microsoft account and identify the tenant the server may reach.
4
Select tools and set policy
Expose the channel, chat and meeting tools the agent needs, then set side-effect and Warden policy.

Authentication

OAuth2
Connect the Microsoft account in the Credentials section, then choose which teams, channels and chats the agents may work with. The account’s own Teams permissions still apply.
Tenant ID
A Teams connection is scoped to one tenant. Several tools take a tenant ID and a user ID together, so the connection identifies the organisation whose teams, chats and meetings the server may reach.
Sandbox
A Sandbox section sits beside Credentials in the integration, so the connection can be prepared before the Hub’s agents work against live teams and chats.

What agents get back

Teams responses carry the identifiers an agent needs to chain the next call, plus the fields that explain the object it touched.

Team, channel, chat and message identifiers
Meeting and call details, including join information
Presence, work location and schedule records
Receipt and execution summary per call

Governance on every Microsoft Teams call

The server ships with the same layered policy engine as every DataGrout integration. Security teams set the posture once; every agent inherits it.

Side-effect controls

Read and write are available. Side effects are governed by your policy, set per integration and inherited from the Hub Server above it.

Policy and interaction controls

Policy Controls carry a mode dropdown and a minimum verdict dropdown. The integration also has its own Interaction section, and overriding the parent policy or parent interaction settings is disabled by default.

Warden preflight

Chat and channel content is written by everyone in the tenant. Warden screens every call in Off, Log only, Advisory or Enforce mode before it executes.

Policy inheritance

Integration policy inherits from the Hub Server and can only get stricter, Warden posture included. A child integration never weakens its parent.

Observability built in

Every execution can return a receipt, a pre-run credit estimate, a Cognitive Trust Certificate and a full execution summary — so an agent's work on your Microsoft Teams data is always explainable.

Receipt per execution

Credit cost estimate

Trust certificate (CTC)

Execution summary

How Warden works →Hub policy inheritance →The MCP Gateway →

What teams run on it

Four patterns that show up again and again once a Microsoft Teams connection is in place.

Channel updates

An agent posts a status update to the right channel, replies in the thread that asked for it, and adds a tab for the document being discussed.

Meeting setup

Create an online meeting for a colleague, with the join details returned so they can be shared in the channel where the meeting was requested.

Onboarding a team

Create the channels a new project needs, add the members, and set up the scheduling group its rota will use.

Workspace reviews

Read teams, channels and chats, compare membership and channel email provisioning with what was intended, and report what stands out.

Microsoft Teams MCP Server FAQ

Through Microsoft OAuth2 in the Credentials section, scoped to a tenant. The Sandbox section sits beside it, and every agent on that Hub inherits the connection.