Microsoft Teams API
Let your coding agent read Teams chats, send messages, and search people so support and ops tasks stay inside the IDE.
Overview
teams-api is an MCP server for the Build phase that connects your agent to Microsoft Teams to read chats, send messages, and search people.
What is this MCP server?
- Read chats, send messages, and search people in Microsoft Teams from MCP
- npm package teams-api-mcp via npx with stdio transport
- Authentication via TEAMS_EMAIL plus TEAMS_AUTO, TEAMS_LOGIN, or TEAMS_TOKEN
- Version 1.5.0 Microsoft Teams API MCP server
- AI-native Teams bridge for agent workflows, not a full Teams client replacement
- Server version 1.5.0
- npm identifier teams-api-mcp with npx runtime hint
- stdio transport with 4 documented environment variables for auth
Community signal: 3 GitHub stars.
What problem does it solve?
You live in your AI coding environment but customer and team context is trapped in Microsoft Teams threads you constantly context-switch to open.
Who is it for?
Solo founders and small teams on Microsoft 365 who want agent-driven Teams messaging and people search during product integrations.
Skip if: Slack-only shops, builders who cannot use corporate Teams auth, or users who need full meeting or calendar control beyond chat APIs.
What do I get? / Deliverables
Your agent can pull Teams context and send replies from MCP so integration and support workflows stay in one interface.
- MCP-configured Teams read and send capability inside your agent
- People search tool calls against your Teams directory
- Documented env-based auth for repeatable dev and ops setups
Recommended MCP Servers
Journey fit
Integration work happens while you are wiring the product and internal tooling to real collaboration systems customers and teams already use. Integrations subphase covers third-party APIs and messaging bridges that agents invoke during build and day-to-day operator workflows.
How it compares
MCP Teams messaging integration, not a standalone customer-support skill or CRM replacement.
Common Questions / FAQ
Who is teams-api for?
Builders and operators on Microsoft Teams who use Claude Code, Cursor, or other MCP clients and want chat read/send and people search in the agent.
When should I use teams-api?
Use it while building agent automations or internal tools that must act on live Teams conversations and contacts.
How do I add teams-api to my agent?
Add a stdio MCP entry that runs npx with teams-api-mcp, set TEAMS_EMAIL, and choose TEAMS_LOGIN, TEAMS_AUTO, or TEAMS_TOKEN per your platform.