Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MSTEAMS_LEVELDBNoPath to the Microsoft Teams LevelDB directory. If not set, auto-discovery per OS is used.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_accountsA

List the Teams accounts (tenant/user contexts) in the local cache.

Each: key (use as the account filter elsewhere), tenant_id, user_id and a best-effort label inferred from org names in messages.

list_conversationsB

List chats/channels (id, title, type), optionally filtered by account.

read_conversationC

Return up to limit most recent messages of a conversation (newest last).

search_messagesB

Case-insensitive substring search across cached messages.

Optional days restricts to messages received in the last N days.

recent_messagesA

Messages received in the last days days, newest first — in ONE call.

Ideal for 'what did I get while I was away'. Filter by account (see list_accounts) to scope to one tenant/org.

mentionsA

@-mentions of you (someone @mentioned you), newest first, with content.

unread_only keeps only not-yet-read mentions; days restricts recency; account scopes to one tenant (see list_accounts). This is the only reliable read/unread signal in the local store.

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 recent_messages(days=...) instead (you read nothing while away → recent ≈ unread).

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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