Microsoft 365 Teams
mcpkey · packageio.github.mindstone/mcp-server-microsoft-teams · v0.3.1
Microsoft 365 Teams via Graph: list chats, read/send messages, list teams/channels, presence.
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
#!/usr/bin/env bash # microsoft-teams (io.github.mindstone/mcp-server-microsoft-teams), recipe baremetal (generated). # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-microsoft-teams.service. set -euo pipefail export HOST=127.0.0.1 PORT=8101 exec npx -y supergateway@4 --stdio 'npx -y @mindstone/[email protected]' --outputTransport streamableHttp --stateful --host 127.0.0.1 --port 8101 --streamableHttpPath /mcp --healthEndpoint /healthz [Unit] Description=MCP server microsoft-teams (toolset my-agent), generated by Hub After=network-online.target Wants=network-online.target [Service] Type=simple User=mcp Group=mcp EnvironmentFile=/etc/mcp/my-agent.env Environment=HOME=/var/lib/mcp/microsoft-teams WorkingDirectory=/var/lib/mcp/microsoft-teams ExecStart=/opt/mcp/my-agent/bin/microsoft-teams.sh Restart=on-failure RestartSec=5 NoNewPrivileges=true ProtectSystem=strict ProtectHome=true PrivateTmp=true ReadWritePaths=/var/lib/mcp/microsoft-teams [Install] WantedBy=multi-user.target
generated from the record, not tested yet
docker run --rm -p 127.0.0.1:8101:8000 -e MS_CLIENT_ID -e MS_CONFIG_DIR -e MS_ACCOUNT_EMAIL -e MS_MCP_PACKAGE_ID -e MICROSOFT_REQUEST_TIMEOUT_MS node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y @mindstone/[email protected]'"'"' --outputTransport streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz'
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T11:40:21+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
microsoft-teams:
image: node:22-alpine
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y @mindstone/[email protected]' --outputTransport
streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint
/healthz
ports:
- 127.0.0.1:8101:8000
volumes:
- npm-cache:/root/.npm
healthcheck:
test:
- CMD-SHELL
- wget -qO- http://127.0.0.1:8000/healthz || exit 1
interval: 30s
timeout: 5s
retries: 5
start_period: 2m
restart: unless-stopped
environment:
MS_CLIENT_ID: ${MS_CLIENT_ID}
MS_CONFIG_DIR: ${MS_CONFIG_DIR}
MS_ACCOUNT_EMAIL: ${MS_ACCOUNT_EMAIL}
MS_MCP_PACKAGE_ID: ${MS_MCP_PACKAGE_ID}
MICROSOFT_REQUEST_TIMEOUT_MS: ${MICROSOFT_REQUEST_TIMEOUT_MS}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T11:40:21+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: microsoft-teams
namespace: mcp
labels: &id001
app: microsoft-teams
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: microsoft-teams
image: node:22-alpine
ports:
- containerPort: 8000
name: http
env:
- name: MS_CLIENT_ID
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MS_CLIENT_ID
- name: MS_CONFIG_DIR
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MS_CONFIG_DIR
- name: MS_ACCOUNT_EMAIL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MS_ACCOUNT_EMAIL
- name: MS_MCP_PACKAGE_ID
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MS_MCP_PACKAGE_ID
- name: MICROSOFT_REQUEST_TIMEOUT_MS
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MICROSOFT_REQUEST_TIMEOUT_MS
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y @mindstone/[email protected]' --outputTransport
streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint
/healthz
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
---
apiVersion: v1
kind: Service
metadata:
name: microsoft-teams
namespace: mcp
spec:
selector:
app: microsoft-teams
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T11:40:21+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
microsoft-teams:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: microsoft-teams
image: node:22-alpine
ports:
- containerPort: 8000
name: http
env:
- name: MS_CLIENT_ID
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MS_CLIENT_ID
- name: MS_CONFIG_DIR
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MS_CONFIG_DIR
- name: MS_ACCOUNT_EMAIL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MS_ACCOUNT_EMAIL
- name: MS_MCP_PACKAGE_ID
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MS_MCP_PACKAGE_ID
- name: MICROSOFT_REQUEST_TIMEOUT_MS
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MICROSOFT_REQUEST_TIMEOUT_MS
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y @mindstone/[email protected]' --outputTransport
streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint
/healthz
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
The form opens with CHANGE_ME for each value you supply: MS_CLIENT_ID, MS_CONFIG_DIR, MS_ACCOUNT_EMAIL, MS_MCP_PACKAGE_ID, MICROSOFT_REQUEST_TIMEOUT_MS. Fill them in before you deploy.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- azure
-
A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.
connect to it
copy what your client needsnpx -y @mindstone/[email protected] # env: MS_CLIENT_ID, MS_CONFIG_DIR, MS_ACCOUNT_EMAIL, MS_MCP_PACKAGE_ID, MICROSOFT_REQUEST_TIMEOUT_MS
{
"mcpServers": {
"microsoft-teams": {
"command": "npx",
"args": [
"-y",
"@mindstone/[email protected]"
],
"env": {
"MS_CLIENT_ID": "${MS_CLIENT_ID}",
"MS_CONFIG_DIR": "${MS_CONFIG_DIR}",
"MS_ACCOUNT_EMAIL": "${MS_ACCOUNT_EMAIL}",
"MS_MCP_PACKAGE_ID": "${MS_MCP_PACKAGE_ID}",
"MICROSOFT_REQUEST_TIMEOUT_MS": "${MICROSOFT_REQUEST_TIMEOUT_MS}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add microsoft-teams -e "MS_CLIENT_ID=${MS_CLIENT_ID}" -e "MS_CONFIG_DIR=${MS_CONFIG_DIR}" -e "MS_ACCOUNT_EMAIL=${MS_ACCOUNT_EMAIL}" -e "MS_MCP_PACKAGE_ID=${MS_MCP_PACKAGE_ID}" -e "MICROSOFT_REQUEST_TIMEOUT_MS=${MICROSOFT_REQUEST_TIMEOUT_MS}" -- npx -y @mindstone/[email protected]
{
"mcpServers": {
"microsoft-teams": {
"command": "npx",
"args": [
"-y",
"@mindstone/[email protected]"
],
"env": {
"MS_CLIENT_ID": "${MS_CLIENT_ID}",
"MS_CONFIG_DIR": "${MS_CONFIG_DIR}",
"MS_ACCOUNT_EMAIL": "${MS_ACCOUNT_EMAIL}",
"MS_MCP_PACKAGE_ID": "${MS_MCP_PACKAGE_ID}",
"MICROSOFT_REQUEST_TIMEOUT_MS": "${MICROSOFT_REQUEST_TIMEOUT_MS}"
}
}
}
}
{
"servers": {
"microsoft-teams": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mindstone/[email protected]"
],
"env": {
"MS_CLIENT_ID": "${MS_CLIENT_ID}",
"MS_CONFIG_DIR": "${MS_CONFIG_DIR}",
"MS_ACCOUNT_EMAIL": "${MS_ACCOUNT_EMAIL}",
"MS_MCP_PACKAGE_ID": "${MS_MCP_PACKAGE_ID}",
"MICROSOFT_REQUEST_TIMEOUT_MS": "${MICROSOFT_REQUEST_TIMEOUT_MS}"
}
}
}
}
name: my-agent target: local servers: - hub: io.github.mindstone/mcp-server-microsoft-teams
- not probed yet: tools unpinned, ingest lists them
tools
Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.