Microsoft 365 Teams via Graph: list chats, read/send messages, list teams/channels, presence.
Microsoft 365 Teams MCP server exists for a simple reason — assistants are far more useful when they can act on Microsoft 365 Teams directly instead of describing what you should do. Microsoft 365 Teams via Graph: list chats, read/send messages, list teams/channels, presence.
Source-available MCP servers by Mindstone. Works with any MCP host — Claude Desktop, Cursor, Rebel, and others.
Installation goes through your MCP client rather than a global install: point it at @mindstone/mcp-server-zendesk on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Microsoft 365 Teams is connected, these are the calls the assistant has available:
Release — age cool-down.** The repo-level .npmrc sets min-release-age=7 (days), so CI refuses to install dependency versions published in the last week. ThisProvenance — attested releases.** Releases are published by CI (.github/workflows/release.yml) under the @mindstone/ npm scope via Trusted Publishing OIDC — noUntrusted — content envelopes.** External content from email, helpdesk, and ticketing systems (email-imap, freshdesk, zendesk) is wrapped in <untrusted-contentSecure-by — default writes.** Production-impacting writes (QuickBooks invoices/bills/customers/vendors) require an explicit QB_ALLOW_PROD_WRITES=1 opt-in envConnector — DescriptionYou will need 2 environment variables: MCP_WORKSPACE_PATH, MCP_OAUTH_BIND_HOST. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Microsoft 365 Teams's toolset — Release, Provenance, Untrusted and 2 more — is a fair guide to whether it matches your workflow. It is maintained by mindstone; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Release | age cool-down.** The repo-level .npmrc sets min-release-age=7 (days), so CI refuses to install dependency versions published in the last week. This blocks the "same-day malicious re-publish" path that ships post-npm audi |
| Provenance | attested releases.** Releases are published by CI (.github/workflows/release.yml) under the @mindstone/ npm scope via Trusted Publishing OIDC — no long-lived npm token exists anywhere — with --provenance Sigstore attesta |
| Untrusted | content envelopes.** External content from email, helpdesk, and ticketing systems (email-imap, freshdesk, zendesk) is wrapped in <untrusted-content source="..."> envelopes with close-tag breakout escaping, so an LLM host |
| Secure-by | default writes.** Production-impacting writes (QuickBooks invoices/bills/customers/vendors) require an explicit QB_ALLOW_PROD_WRITES=1 opt-in env var; outreach prospect-enrolment and mixmax sequence-recipient tools carry |
| Connector | Description |
{
"mcpServers": {
"microsoft-teams": {
"command": "npx",
"args": ["-y", "@mindstone/mcp-server-zendesk"],
"env": {
"MCP_WORKSPACE_PATH": "your-value",
"MCP_OAUTH_BIND_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MCP_WORKSPACE_PATH | Filesystem location the server is allowed to use. | Optional |
| MCP_OAUTH_BIND_HOST | Endpoint or connection string the server talks to. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.