Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Read Microsoft Teams teams, channels, chats and messages, and post/reply/send, safe by default.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
TEAMS_CLIENT_ID, TEAMS_TENANT_ID, TEAMS_CLIENT_SECRET, TEAMS_TOKEN, TEAMS_MODE, TEAMS_ALLOW_SENDValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"teams": {
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-teams"
],
"env": {
"TEAMS_CLIENT_ID": "your-value",
"TEAMS_TENANT_ID": "your-value",
"TEAMS_CLIENT_SECRET": "your-value",
"TEAMS_TOKEN": "your-value",
"TEAMS_MODE": "your-value",
"TEAMS_ALLOW_SEND": "your-value"
}
}
}
}Run this in your terminal
claude mcp add teams --env TEAMS_CLIENT_ID=your-value --env TEAMS_TENANT_ID=your-value --env TEAMS_CLIENT_SECRET=your-value --env TEAMS_TOKEN=your-value --env TEAMS_MODE=your-value --env TEAMS_ALLOW_SEND=your-value -- npx -y @dockndevai/mcp-teamsFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"teams": {
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-teams"
],
"env": {
"TEAMS_CLIENT_ID": "your-value",
"TEAMS_TENANT_ID": "your-value",
"TEAMS_CLIENT_SECRET": "your-value",
"TEAMS_TOKEN": "your-value",
"TEAMS_MODE": "your-value",
"TEAMS_ALLOW_SEND": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"teams": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-teams"
],
"env": {
"TEAMS_CLIENT_ID": "your-value",
"TEAMS_TENANT_ID": "your-value",
"TEAMS_CLIENT_SECRET": "your-value",
"TEAMS_TOKEN": "your-value",
"TEAMS_MODE": "your-value",
"TEAMS_ALLOW_SEND": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
TEAMS_CLIENT_ID envTEAMS_TENANT_ID envTEAMS_MODE envTEAMS_ALLOW_SEND envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account dockndevai, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: TEAMS_CLIENT_SECRET, TEAMS_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 39 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A safe-by-default Model Context Protocol server for Microsoft Teams, over Microsoft Graph. It lets an agent read and operate Teams — list joined teams, channels and members, read channel messages and threaded replies, read 1:1/group chats and their messages, and (in higher modes) post to channels, reply in threads, send chat messages, and soft-delete a message.
Browser sign-in: on first run it opens your browser to the Microsoft sign-in page, then caches the token and refreshes it silently — the server never sees your password.
Part of the dockndevai MCP server suite — one governance model across all of them.
The server starts read-only (see Safe by default); higher-capability tools are only registered when you raise the mode.
| Tool | For | Needs mode |
|---|---|---|
whoami | confirm which account is in use | read-only |
list_teams | teams the user has joined | read-only |
list_channels | channels in a team | read-only |
list_team_members | members of a team | read-only |
list_channel_messages | recent messages in a channel | read-only |
get_channel_message | one channel message + body | read-only |
list_message_replies | a channel message's thread | read-only |
list_chats | the user's 1:1 / group chats | read-only |
list_chat_messages | messages in a chat | read-only |
send_channel_message | post to a channel | read-write + TEAMS_ALLOW_SEND |
reply_channel_message | reply in a channel thread | read-write + TEAMS_ALLOW_SEND |
send_chat_message | send a chat message | read-write + TEAMS_ALLOW_SEND |
delete_channel_message | soft-delete your own message | admin + TEAMS_ALLOW_DELETE |
npx -y @dockndevai/mcp-teams
You need an Entra (Azure AD) app registration. For the default browser sign-in, register a public client and add the redirect URI http://localhost (platform: *Mobile and desktop applications*), then use its Application (client) ID as TEAMS_CLIENT_ID. Grant delegated Team.ReadBasic.All, Channel.ReadBasic.All, ChannelMessage.Read.All (and ChannelMessage.Send / Chat.ReadWrite to post). No client secret is needed for interactive use.
{
"mcpServers": { "teams": { "command": "npx", "args": ["-y", "@dockndevai/mcp-teams"], "env": { "TEAMS_CLIENT_ID": "00000000-0000-0000-0000-000000000000", "TEAMS_TENANT_ID": "common", "TEAMS_MODE": "read-only" } } } }
On first use the server opens your browser to sign in and caches the token at ~/.mcp-teams/token.json (0600); later runs refresh silently.
See docs/CLIENTS.md for Claude Code / Cursor / Codex / VS Code / Windsurf snippets, and .env.example for every supported variable.
Auth mode is chosen automatically (override with TEAMS_AUTH):
TEAMS_CLIENT_ID set. Authorization-code + PKCE with a loopback redirect: the browser opens, you approve once, and the access + refresh token are cached on disk. Most Teams messaging APIs are delegated-only, so this is the primary mode. The server never handles your password.TEAMS_CLIENT_SECRET present; the server fetches an app token itself. Note that several Teams message APIs are not available to app-only tokens without protected-API approval from Microsoft.TEAMS_TOKEN set to a pre-obtained Graph bearer token. You manage its lifetime.The access model is enforced by src/security.ts — defence in depth on top of the Graph token's own scopes/roles:
read-only (default) → read-write → admin. A tool is registered only if the mode allows its capability. Read-only exposes the 9 read tools; posting needs read-write; deletes need admin.read-write it also requires this flag.admin mode. Deletes are soft-deletes (recoverable), and only your own messages.TEAMS_ALLOW_SEND / TEAMS_ALLOW_DELETE gates.See SECURITY.md.
npm install
npm run build
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | TEAMS_TOKEN=x node dist/index.js npm test
MIT