chatwatch
Related Servers
Alternatives to chatwatch
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to read from and write to Microsoft Teams via a real browser-based bridge, with support for multi-tenant profiles, chat listing, message reading and searching, team/channel listing, and sending messages.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to list spaces, read and search Google Chat conversations, and send messages or thread replies by driving the Chat web app in a signed-in Chrome profile, with no Google Chat API, OAuth app or Cloud project required.716 npmMIT
- AlicenseAqualityCmaintenanceEnables Microsoft Teams chat automation, message extraction, and unread notification monitoring by automating the Teams web client with Puppeteer, requiring no API keys or Azure setup.512 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Microsoft Teams and Microsoft Graph, covering chats and channel messaging, message search, user and team member lookups, and file upload or attachment downloads. Supports OAuth device-code authentication, rich Markdown formatting, and LLM-friendly conversion of Teams HTML into Markdown.12 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to drive your own signed-in ChatGPT web account — asking questions, continuing chats, attaching files, toggling thinking or web search, creating images, transcribing recordings of any length, reading replies aloud, and managing conversations, memories and projects. It runs against a local Chrome tab on chatgpt.com and reports live progress and step-named errors back to the client.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read conversations, send messages, and manage members in Microsoft Teams via the Teams Chat Service REST API.121 npm9MIT
TDQS
Scored across 6 tools
Most tools target clearly different operations: listing chats, reading history, waiting for new events, sending, fetching attachments, and listing drafts. The closest pair is teams_read_messages vs teams_wait_for_messages, but the descriptions make the distinction (historical snapshot vs polling with after_seq/seq cursors) explicit enough that an agent can choose correctly.
Every tool uses the same teams_ prefix followed by a verb_noun snake_case pattern (list_chats, read_messages, send_message, get_attachments, list_drafts). No mixing of camelCase or inconsistent verb styles.
Six tools is well-scoped for a Teams chat bridge: one per lifecycle step (discover chats, read, poll, send, fetch attachments, review drafts) with no redundant entries. Nothing feels padded or missing at the count level.
Core read/poll/send/attachment/draft-listing flows are covered, but teams_list_chats exposes per-chat settings (watch, send mode, handler) with no tool to change them, and drafts can only be listed, never approved or discarded programmatically. Sending also opens/marks a chat read with no standalone mark-read/unread operation, forcing workarounds or human action on the chatwatch page.