msteams-local-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MSTEAMS_LEVELDB | No | Path to the Microsoft Teams LevelDB directory. If not set, auto-discovery per OS is used. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List the Teams accounts (tenant/user contexts) in the local cache. Each: |
| list_conversationsB | List chats/channels (id, title, type), optionally filtered by |
| read_conversationC | Return up to |
| search_messagesB | Case-insensitive substring search across cached messages. Optional |
| recent_messagesA | Messages received in the last Ideal for 'what did I get while I was away'. Filter by |
| mentionsA | @-mentions of you (someone @mentioned you), newest first, with content.
|
| unread_messagesA | Unread items needing attention = your UNREAD @-mentions. ⚠️ The local Teams cache has NO general read marker (per-message read state is
not stored on disk), so true 'all unread' can't be derived. Unread @-mentions
are the reliable signal. For 'everything that arrived while I was away', use
|
| overviewA | Who messaged you: recent activity grouped by conversation, newest first. Per conversation: title, message count, distinct senders, last message + time. Great first call to get the lay of the land before drilling in. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/KamorionLabs/msteams-local-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server