zaungast
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZAUNGAST_DB_DIR | No | Read a static copy of the database directly (testing / offline analysis); skips discovery and live-refresh. | |
| TEAMS_LEVELDB_DIR | No | Path to the Teams …\IndexedDB\https_teams.microsoft.com_0.indexeddb.leveldb directory. Set only if auto-discovery fails or you have multiple profiles. | |
| ZAUNGAST_INCREMENTAL | No | Refresh mode: copy-reuse (default, faster) or reparse (simpler). |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_conversationsA | Your Teams sidebar: the newest N conversations (default), or filter by kind/participant/title/time. Note: this reads the LOCAL Teams cache — history is the synced slice on this device, not the full server archive. |
| read_messagesA | Read one conversation's messages in STORY ORDER (oldest→newest). Target by handle (c:xxxx) or title/participant substring. Page back with the returned older: cursor, or center on a message with around:. Note: this reads the LOCAL Teams cache — history is the synced slice on this device, not the full server archive. |
| searchA | Full-text search across all messages with filters. Empty query = filtered browse. from/in accept display-name / title substrings or handles. mentions_me finds messages that @mention you. Note: this reads the LOCAL Teams cache — history is the synced slice on this device, not the full server archive. |
| top_topicsA | Distinctive/trending topics over a window (vs your baseline), overall or scoped to a person/conversation. Returns each topic with an exemplar message. Note: this reads the LOCAL Teams cache — history is the synced slice on this device, not the full server archive. |
| find_personA | Resolve a name/nickname fragment to a person's canonical name and stable p:handle, with message count and last-contact time. Use when a name is ambiguous or unrecognized, or when you need contact stats or a p:handle. For ordinary filtering, just pass a name substring directly to search/read_messages 'from'/'participant' — don't call this first. Omit query to scan the roster (most-talked-to first). |
| describe_schemaA | Inspect the raw Teams IndexedDB stores and PROPOSE a field mapping. Use when tools report the schema is unrecognized (after a Teams update), or to inspect the DB structure. Proposes only — applies nothing; a human verifies the proposal and saves it as a new schema version. |
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/mbe24/zaungast'
If you have feedback or need assistance with the MCP directory API, please join our Discord server