Improvements to the Teams MCP server example#597
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Teams MCP server example to support multiple concurrent “ask” flows per user, adds a Microsoft Graph-backed find_user tool, and refreshes documentation to match the new tool set and request/response flow.
Changes:
- Replace “next message answers the ask” with Adaptive Card-based replies correlated by
requestId, plus waiter-basedwait_for_reply/wait_for_approval. - Add Microsoft Graph user search (
find_user) via a new lightweight app-only Graph client. - Update README and example code to reflect new tool names and AAD object-id semantics.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| examples/mcp-server/src/state.ts | Adds waiter maps to support event-driven reply/approval waits. |
| examples/mcp-server/src/mcpTools.ts | Reworks ask/approval tools (snake_case names), adds wait_* tools, adds find_user. |
| examples/mcp-server/src/graphClient.ts | New app-only Graph client for user search. |
| examples/mcp-server/src/app.ts | Routes replies via card.action.ask_reply and approvals via card.action.approval_response. |
| examples/mcp-server/README.md | Documents new tools, AAD object-id usage, and Graph permissions. |
| examples/mcp-server/package.json | Adds Graph dependencies for the new find_user tool. |
| examples/ai-mcp/src/handlers.ts | Marks adaptive-card emissions as AI-generated content. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
heyitsaamir
reviewed
May 27, 2026
corinagum
reviewed
May 28, 2026
corinagum
reviewed
May 28, 2026
corinagum
reviewed
May 28, 2026
corinagum
reviewed
May 28, 2026
corinagum
reviewed
May 28, 2026
corinagum
reviewed
May 28, 2026
heyitsaamir
reviewed
May 28, 2026
corinagum
approved these changes
Jun 3, 2026
corinagum
added a commit
that referenced
this pull request
Jun 15, 2026
## Release 2.0.13 Merges main into release for stable publish. ### Notable changes since 2.0.12 - fix(client): use explicit Graph scopes for Teams Desktop NAA compatibility (#616) - ci: switch publish pipeline to 1ES Official template for CodeQL/SDL (#607) - ci: add weekly SDL pipeline for CodeQL/CredScan compliance (#608) - Refresh teams.apps README (#604) - Reject unauthenticated when no credentials (#506) - fix(api): conditionally set citation encodingFormat based on text presence (#579) - Improvements to the Teams MCP server example (#597) - Bump MSAL Node to v5 (#603) - Merge root message entities in Activity (#590) - TeamsSDK: Correct imports and return types in misc. packages (#589) - Cache federated identity MSAL clients (#613) ### Release steps 1. Merge this PR 2. Trigger the [release pipeline](https://dev.azure.com/DomoreexpGithub/Github_Pipelines/_build?definitionId=52&_a=summary) for `release` branch with **Public** publish type 3. Bump version on main to `2.0.14-preview.{height}` 4. Create git tag and GitHub Release page
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request makes significant improvements to the Teams MCP server example, focusing on enabling multiple simultaneous "ask" requests per user, adding a user search tool via Microsoft Graph, and updating the documentation and code to reflect these enhancements.
Key changes include:
1. Enhanced Ask/Reply Flow
card.action.ask_replyhandler. This enables tracking replies to individual asks and allows multiple pending questions per user.2. User Search via Microsoft Graph
find_usertool that searches for users by name, email, or UPN using Microsoft Graph, and returns up to 5 Azure AD object IDs. This is implemented in a newgraphClient.tsfile and documented in the README.3. Documentation and Developer Experience
userIdas the AAD object id.4. Package and Dependency Updates
package.json. (examples/mcp-server/package.json)These changes collectively make the MCP server example more robust, flexible, and easier to use in real-world scenarios.
AI-MCP Example