MCP Teams Server

Created By
InditexTecha year ago
An MCP (Model Context Protocol) server implementation for Microsoft Teams integration, providing capabilities to read messages, create messages, reply to messages, mention members.
Overview

What is MCP Teams Server?

MCP Teams Server is an implementation of the Model Context Protocol (MCP) designed for integration with Microsoft Teams, enabling functionalities such as reading, creating, and replying to messages, as well as mentioning team members.

How to use MCP Teams Server?

To use MCP Teams Server, clone the repository, set up the required environment variables, and start the server using the provided commands. Ensure you have a Microsoft Teams account and the necessary configurations in place.

Key features of MCP Teams Server?

  • Start threads in channels with titles and contents, mentioning users.
  • Update existing threads with message replies, mentioning users.
  • Read thread replies and list channel team members.
  • Read channel messages.

Use cases of MCP Teams Server?

  1. Automating message management in Microsoft Teams.
  2. Enhancing team collaboration through automated replies and mentions.
  3. Integrating external applications with Microsoft Teams for seamless communication.

FAQ from MCP Teams Server?

  • What is the Model Context Protocol?

The Model Context Protocol is a framework that allows applications to communicate contextually within platforms like Microsoft Teams.

  • Do I need a Microsoft Teams account to use this server?

Yes, a Microsoft Teams account is required for integration and functionality.

  • Is there a Docker image available for MCP Teams Server?

Yes, a Docker image can be built and run for easier deployment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
InditexTech
Star
233
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago